Citation
No problems, there was nothing negative in my message!!
No worries, itâs just my first real PR so I wanted to make sure I did things right to not break everything ![]()
Citation
No problems, there was nothing negative in my message!!
No worries, itâs just my first real PR so I wanted to make sure I did things right to not break everything ![]()
@Romuald_Pochet For information, for calendar sharing, we are considering two types of calendars with @bertrandda:
So for you, you will need to make a request to retrieve all « shared » calendars in the scenes.
The discussion is available here:
For your information, I just merged the calendar sharing, so work on the scenes can resume ![]()
Hello everyone!
As this feature is quite requested, and as I just merged a PR that unlocks this behavior, I worked on a small functional specification so that we can at least agree on the desired functionality (thatâs the hardest part :p).
Functional specification for the scene trigger
I propose a trigger in the scenes that could be configured as follows:
Features:
Functional specification for the condition in the scenes
For the conditional part in the scenes, the idea is to be able to continue or interrupt a scene if an event in one/more given calendar meets a condition and is ongoing.
Example:
Proposal:
What do you think?
For information, I have started the developments, for now only on the scene trigger.
The backend part is almost finished, Iâm working on the frontend now.
@bertrandda I had to change a bit the GET /calendar request, in short I needed an option to retrieve only the shared calendars (and not my private ones), so I added 3 cases:
I thought about updating the frontend code.
It was necessary because now in the scenes only the shared calendars are accessible.
The PR on Github is here:
Do you also take into account holidays, etc.?
Or do you only manage certain filters on email titles?
Iâm not managing any of this!
The purpose of this feature is to give the user the ability to trigger scenes based on upcoming events / those that are about to end in their calendars, after that itâs up to the user to connect their own calendars.
The calendar content is personal to each user, I just provide the tools to create the scenes ![]()
If you want to connect a calendar with vacations, holidays, the day you go swimming, your kidsâ school, everything is possible!
Are we in agreement that there is no built-in calendar in Gladys, itâs just synchronization with a third-party service?
I would use it well for heating periods in a dedicated calendarâŠ
Oh, I see.
Thatâs not a bad idea, it saves you from having to get a library that calculates public holidays based on a given country.
Itâs another way of looking at things, like it prevents library errors.
Exactly, we consider that we are not here to code a complete calendar client (it would be a lot of work, and itâs not really our job)
The idea is that users keep their classic calendar client, continue to fill in events on their phone/computer as they already do, and then we just synchronize with it.
You can create a specific calendar anywhere for your heating periods and it will do the job ![]()
Exactly ![]()
For example, for public holidays, by default my calendar has a « public holidays » calendar I think, and Gladys synchronizes it. You just need to connect to this calendar, not put a filter on the name to catch all events, and there you go, you manage public holidays in Gladys.
Great job, this will be useful to many people.
Once again @AlexTrovato was right from the start
Add internal calendar sharing by bertrandda · Pull Request #1337 · GladysAssistant/Gladys · GitHub
Hello everyone!
Iâve made great progress today, and Iâve merged into master the first part of this development: triggering a scene based on an event that is happening or about to end.
Concretely, what is possible to do
These are just a few examples, but of course the possibilities are endless!
What does it look like?
What is powerful is that it is possible to retrieve in the actions the event that triggered the scene!
and this gives:
I can already see @lmilcent telling me: « but wait? are we going to be able to use the sensor values of the triggers in there?? » Maybe in the future yes!! ![]()
Video demonstration
I recorded a video that shows an example ![]()
How to test?
I made a Docker build on the :dev tag as usual.
The Docker image is as follows:
gladysassistant/gladys:dev
I welcome any feedback, if you have time to test this weekend that would be great ![]()
For the second part of the development, it will be later, I will keep you informed of the progress!
![]()
![]()
This is great, I love these messages: « hey look at the new super powerful feature I just made » ![]()
Thanks so much for the work!!
Well, for the heating example, first of all, it has to be supported by Gladys ![]()
I didnât dare to say it, but I think itâs a feature that is being developed in secret to surprise the community ![]()
I donât want to dash your hopes @spenceur but thatâs not the case ![]()
Heating is a big topic, and 90% of the work is defining what we want to do. Right now, weâre still at level 0, nothing has been done yet.
Youâre tough, Iâd say 5% already (see the feature request and the start of reflection) ![]()
Iâm trying to test the feature this weekend!
And did you add the âč flash for⊠âș or âč flash until âș function? ![]()
Turn on the light + wait 1sec + turn off the light, that should do it, right? ![]()
Couldnât we have a condition that if there is an event in calendar x, then an action is taken?
This would allow me to do this:
If there is an event on a public holiday in the holiday calendar, then we notify the head of linote that he can go back to bed