Already possible 
You select the « any name » option in the filters
Here is my feedback following my first scene creation experience.
Calendar Visibility
I want to create a scene, but my Google calendar is not visible by default even though I am the one who configured Gladys. I imagine I need to share my calendar, but this seems to apply to everyone by default.
Local Calendar
I realize that if I want to avoid Google, I will need to find an alternative compatible with external CalDAV. The best would have been to have a local calendar by default to depend as little as possible on the internet or third-party services. But here we are talking about the calendar service rather than the feature.
For now, I have created a « Gladys » agenda in my Google calendar.
Event Description
I tried to use the description of the appointment in my agenda, but this is not provided. I am sure we will have requests for this 
(Edit)
Test in a Scene
First attempt: I did not fill in the condition « and the event starts in ».
Result: 
Since my scene was saved, I thought it was good and that the parameter would be « at the time of the event » by default.
Thanks for your feedback @lmilcent, Iâll fix that!
Indeed, only calendars « shared » within the Gladys instance are displayed.
Private calendars are excluded from scenes for privacy reasons.
I added a message in the UI to make it clearer:
Also, on the calendars page, I added a message for new arrivals who donât have calendars configured:
Now itâs clearer!
Indeed, currently we donât retrieve the descriptions, but thatâs more at the level of the calendar feature itself. cc @bertrandda 
I removed the possibility of having these fields empty. By default, they are filled in, and only modifiable for another value.
Yes, excellent idea, I will see what can be done
Are calendars private even those belonging to the user who is creating the scene?
Because thatâs exactly what surprised me.
The agenda is mine, the scene is created from the same account, so I expected to be able to use it without sharing it with all Gladys users.
On the other hand, not having access to my wifeâs agenda (if she used Gladys ) makes sense because itâs another user.
I never checked, but do all Gladys users have access to scenes and their content?
- If so, I understand why not to share calendars in scenes by default.
Example of a security incident:
My wife created a scene with her agenda, which is not shared with me. But as a user, I can see the scene and modify it (hypothesis), so access her agenda indirectly (I just need to receive a message from Gladys for each new event).
Perfect, I think thatâs better!
Do you know if it is possible (without significant development effort) to have a local agenda, in which you can create events without using third-party services?
Exactly, and thatâs precisely for the case you mentioned.
Scenes are common to the entire instance; a scene is something « public » in Gladys, hence the need for the calendar to be public so it can be part of a scene.
Yes, exactly, a scene is not a private entity but shared among all members of the instance. Thatâs a choice!
However, only administrators can modify them.
I donât think thatâs what we want in Gladys! Itâs debatable, but for me, Gladys is not a calendar application.
The issue if we implement the ability to create local events is that weâll always be asked for more:
- What if I want to sync my local events with my remote calendar? My phone? (two-way sync)
- I want to change the color of my local calendar? (calendar editing view)
- I want to be able to locate my event? (map view for an event)
- I want to create recurring events (every Monday at 8 a.m.?)
Itâs hard to realize, but a calendar application is quite a huge task, especially given the high standards set by « basic » applications (Google Calendar, Apple Calendar on Mac, which is very simple but excellent).
For me, if we go in this direction, we will inevitably do worse than an external calendar, and we will be judged on a product that is not our specialty.
I think that Gladysâ goal is precisely not to reinvent the wheel but to connect with external applications that are already in our lives and work very well
Edit: this might be off-topic, maybe we can create a new topic 
In your case @lmilcent, why not self-host a CalDAV server (OwnCloud for example) if your goal is to have everything locally, I think thatâs the best option?
I validate what you explain about the access levels to the agendas, itâs clearer for me now!
For the local hosting part of the agenda, you are absolutely right about that. Proposing an ultra-basic agenda can be both very practical by explaining that it is intentionally basic, but itâs true that it can also be shooting yourself in the foot.
Where I relativize, is that the internet is only necessary for synchronization. Events are then imported locally, which allows to continue to function even in case of loss of internet.
To conclude on the self-hosting part, it is interesting but as you know it is work and time (no matter the service). So I often weigh the pros and cons, between spending time or taking a « secured » cloud like Gladys Plus which encrypts everything before sending to the cloud (what I call operating in Zero Knowledge mode).
Hello everyone!
I just merged part 2 of this development: condition on ongoing events in scenes.
The principle is to be able to continue or stop a scene only if an event is found / not found.
I made a build on the Docker dev tag which contains this condition:
gladysassistant/gladys:dev
Iâm open to any feedback
Once all this is tested, I will deploy a new version of Gladys!
Hello everyone! Iâm open to feedback on this second development before I release it
Thanks for the follow-up!
Here is my test in a scene:
- Scheduled trigger (to simulate a specific detection)
- Continue only if an event is found in my calendar, with any name
- Send a message
I wanted to send a message with the details of the event (name, location, etc.) but itâs not possible because there are no variables, unlike when I use the calendar as the scene trigger event.
And no way to call « get the last state » necessarily.
If itâs possible, it would seem more logical to create these variables by default in the scene when « continue only if » with the calendar is called. As the trigger part does.
Oh indeed, I didnât code the variables for this trigger, I thought it wasnât useful in this case⊠After all, youâre right, it can be useful.
Iâll do it today
From my side, I canât really do any testing since my schedules are not displaying correctly.
@bertrandda is on it, he is studying my logs carefully ^^
Itâs good for the variables, the PR:
Not yet merged, no dev build yet.
Iâll keep you posted when itâs live in dev!
The dev build has passed, available at:
gladysassistant/gladys:dev
Feedback is welcome!
Iâm currently writing the documentation in FR and EN for these 2 new features + the launch articles for Gladys Assistant v4.8 (Itâs a lot of work, with all the localized screenshots )
PR in progress here on the site:
Well, it took me almost the whole day, but Iâm done!
- Documentation for the scene trigger (EN + FR)
- Documentation for the condition in scenes (EN + FR)
- Gladys Assistant v4.8 launch article (EN + FR)
The PR is available here:
There is a link to the site deployed in preview on Cloudflare Page in the PR (not to be shared, itâs just a preview to see how it looks)
Iâm open to proofreading/feedback on the article and the documentation.
Iâm stopping for today, Iâll be back on Monday morning and I will probably launch Gladys Assistant v4.8 on Monday or Tuesday evening depending on the feedback
Iâm hesitating to do a live YouTube launch, because itâs a set of really nice features that bring a lot of possibilities to Gladys / scenes.
Great!
Yes, thatâs « normal », this page has never been translated (feature developed by an American who doesnât speak French).
I would be happy to receive a PR on this topic if someone wants to help, there has been a GitHub issue since November: In the french documentation of the "ScĂšnes", a part is in english : âChain Scenesâ · Issue #102 · GladysAssistant/v4-website · GitHub.
You need to:
- Translate the text (stored in
i18n/fr/docusaurus-plugin-content-docs) - Take a screenshot of the interface in French.
@lmilcent Youâll be interested in tonightâs live stream, I found a free online CalDAV calendar service for my demo (up to 2 devices). Of course, itâs in the cloud, but if you donât want to self-host, it can be a nice option.
In 2 minutes I had the CalDAV server credentials, and it works perfectly with Gladys
#teasing