Hello,
I’m new to the area, I did my first Gladys install this week so I’m still figuring out some things. My install is up to date, I used the provided image for RPI.
To start, I have a problem with a very simple subject: the calendar.
I configured it on my account in Gladys, no problem (category « Other » since my caldav server is self-hosted).
I created a second User account, impossible to associate the same server with it. I make it Administrator, I can continue the configuration.
If I connect this 2nd account to caldav with a 2nd user, it works. However, it’s impossible for me to configure the same account as mine (annoying since we have a shared account that is used to share our calendars).
Thanks in advance if you have any tips, and congratulations on all the work already done!
Hello @pap welcome,
Indeed, this is not a case I had anticipated. There must be some conflicts in the database. I will try to reproduce and fix it as soon as possible.
For information, which service do you use to host your calendar?
Thank you for your response.
I use Radicale.
Welcome to the forum @pap and thank you for your feedback, it helps us improve! 
@bertrandda Let’s see if the solution is to synchronize the calendar twice (maybe), or to create cross-user calendars in Gladys?
Speaking of which, I recently made a proposal to avoid conflicts: Proposition: Ajouter un nombre aléatoire à 4 chiffres à tous les "selector" pour éviter les collisions
The ability to share calendars and dashboards among users would be great, indeed.
When reproducing, it’s true that certain uniqueness constraints on fields cause problems.
Yes, sharing calendars internally in Gladys is a good solution.
Later, I would still like to fix this uniqueness issue because imagine a family using the same Nextcloud instance (or iCloud, Google… I don’t think it’s possible with Radicale) if they configure the shares directly in the Nextcloud calendar, the external IDs will probably be the same during synchronizations.
In any case, this requires development in both cases. The internal sharing in Gladys should not be a problem, but fixing the uniqueness will be a headache. For the selectors, I agree with you Pierre-Gilles. But there is also the external ID and we fall back on the same problems mentioned here Gladys V4 - Affichage de capteurs dans l'interface - #11 par pierre-gilles when we want to remove the constraints. For example, I would like to remove the uniqueness constraint on t_calendar.external_id which in itself is not necessary between several users because when we retrieve a calendar we specify its user. At most, if we really want one, we can put it on the whole external_id + user_id.
I agree that this is a problem!
To remove the constraint on external_id, we need to consider that if we start making multi-user calendars, this may no longer be the case! (A calendar could be owned by everyone in the family)
I would rather add something to the external_id to make it even more unique (even if it means adding the user selector of the person who adds the calendar to the external id)
Yes, it will surely reduce error cases, but in the particular case of calendar sharing on the hosting side, I think it can happen. Anyway, we’ll see later, for now let’s make sharing possible, I started a PR Add internal calendar sharing by bertrandda · Pull Request #1337 · GladysAssistant/Gladys · GitHub
It’s done, the PR is ready if you want to test
hello,
how do you go about testing?
sorry, i’m not very familiar with github and such 
To functionally test a PR, it’s explained here by Pierre-Gilles Review des PR - J'ai besoin de vous!, however you won’t be able to do that directly on your RPI.
There has been a discussion started on the PR so changes will surely come.
OK, thanks for your reply.
I’ve posted my answer on the PR!
For information, we are debating the type of sharing:
- Either we share a calendar with the entire instance (shared calendar mode: yes/no)
- Or we offer to share a calendar only with certain people in the instance
Both options are possible, but option 2 is still more complex at many levels (what happens with scenes?)
See my 2 messages on Github
I’m reposting here what we discussed on Github.
For archiving, we’re going with « shared/private » instead of user-based sharing, which is not very useful/complex to implement for little gain 
See Github discussion: Add internal calendar sharing by bertrandda · Pull Request #1337 · GladysAssistant/Gladys · GitHub
For information, I just merged calendar sharing management into a Gladys instance 
You can thank @bertrandda for all the work done
In the UI, it looks like this:
The PR is available here: