Using the agenda/calendar in scenes

[spenceur]

Be able to notify in a scene an event (Ex

In a scene the user can be notified of the day’s appointments)

Be able to perform automatic tasks based on an event (Ex

Warn about urgent appointments 10 minutes in advance.
Remind of a birthday etc)

Be able to retrieve information for event conditions. (Ex

Scene wake up:
If not a holiday or not a vacation or etc
Turn on the lights gradually and play music)

[Romuald_Pochet]

1. Use calendar events as a scene trigger
   Ex. run the scene when the event XXX starts / ends / starts with reminder

2. Allow testing in scenes if a calendar event is currently in progress.
   Ex. continue only if the event XXX is in progress

[pierre-gilles]

Thank you for the request, it’s perfect!

Cast your votes!

[spenceur]

This wouldn’t be a duplicate:

Utilisation de l'agenda/calendrier dans les scènes

Pouvoir notifier dans une scène un événement (Ex Dans une scène l’utilisateur peut être notifier des rdv de la journée) Pouvoir réaliser des taches automatique en fonction d’un événement (Ex Prévenir des rdv urgent 10 min a lavance. Prévenir d’un anniversaire etc ) Savoir récupérer des info pour des conditions d’événements. (Ex Scene wake up : Si jour non férié ou non vacance ou etc Allumer les lumière petit a petit et mettre de la musique )

[Romuald_Pochet]

Indeed, I searched for « calendar » and not « agenda »

[spenceur]

Could we then merge them perhaps, as well as those who voted for one or the other?

[VonOx]

I merged it, I think the votes are good too

[spenceur]

It seems okay We’re just missing your vote @VonOx

[Romuald_Pochet]

Hello,

Given that this is an essential feature for me and that I don’t master Gladys at all, I allowed myself to create a PR for this request (https://github.com/GladysAssistant/Gladys/pull/1338).

[VonOx]

@Romuald_Pochet you must have picked the wrong branch as the PR concerns your changes on the zwave or you haven’t created your branch from master

[Romuald_Pochet]

In fact, I left my master, which includes the Z-Wave modifications I’ll fix it as soon as possible

[spenceur]

Wouldn’t it be simpler to start from Gladys’s master instead of doing reverts?

[Romuald_Pochet]

It’s done.

Ps: sorry but I’m not yet used to using Git… But if it’s easier, I can start again from the master branch

[VonOx]

It’s mainly for the commit history.

[Romuald_Pochet]

Okay, I’m creating a clean branch. Well, I can’t start from Gladys master, shouldn’t I create a branch in my fork? Or my master also contains zwavejs, I think that’s the issue, I should have created a special branch for my demos…

[Romuald_Pochet]

Well, I’m starting from scratch: new fork, new branch, new PR

PS: now I’m going to try to create my PR for ZwaveJS

[pierre-gilles]

@Romuald_Pochet Thanks for your PR!

I see that you’ve gone with this for development:

Before even talking about the code, I think it would be good if we agree on what we want at the feature level, because in my opinion there are many ways to do this, and it’s not a simple feature:

• Typically, the « event starts » trigger is useful, but often what we want is « event starts in 5/15/30 minutes » (if you want to receive a reminder 15 minutes before leaving for an appointment, for example). Knowing that this is a very different paradigm, it will change the implementation a lot (since you have to program each trigger and not each event), so you need to think about it beforehand.
• As for event selection, how does it work? Is there a list and you select an event from the list? Do you take all events that contain this string? In my opinion, there is a real reflection to be had on this, it may be useful to have a trigger that is triggered on a specific event, or on a match of a specific text, in any case it must be clear in the UI.
• Who has the right to see which calendars? This is a very hot topic, we are talking about it here with @bertrandda: [Caldav] Configuration multicomptes - #13 par pierre-gilles. We need to agree before doing this dev.

Sorry if I’m asking a lot of questions, it’s a really cool feature and if we want to meet everyone’s needs, we need to ask the questions beforehand!

Thanks anyway for starting the development @Romuald_Pochet, it’s great work anyway

[spenceur]

I wonder if the feature you are presenting only meets your need @Romuald_Pochet?

For reference, the requests related to this feature:

Utilisation de l'agenda/calendrier dans les scènes

Pouvoir notifier dans une scène un événement (Ex Dans une scène l’utilisateur peut être notifier des rdv de la journée) Pouvoir réaliser des taches automatique en fonction d’un événement (Ex Prévenir des rdv urgent 10 min a lavance. Prévenir d’un anniversaire etc ) Savoir récupérer des info pour des conditions d’événements. (Ex Scene wake up : Si jour non férié ou non vacance ou etc Allumer les lumière petit a petit et mettre de la musique )

Utilisation de l'agenda/calendrier dans les scènes

Utiliser les événements du calendrier en tant que déclencheur d’une scène Ex. exécuter la scène lorsque l’événement XXX débute / se termine / débute avec reminder Permettre de tester dans les scènes si un événement du calendrier est actuellement en cours. Ex. continuer seulement si l’événement XXX est en cours

Did you see that we had merged the two requests @pierre-gilles?

Good luck

[Romuald_Pochet]

Hello,

Indeed, the feature is incomplete! I have just started the developments of what also goes into the heart of Gladys (and especially the UI part) Isn’t this a good way to work?

1. The reminder is managed via the reminder given by CalDav. But we would need to update the « calendar_event » data model to include the value; We could also specify the reminder when creating the scene and thus create the trigger when creating the scene. But in this case, we lose the triggering outside the scene, for example a notification on the UI or Telegram.
2. « Know how to retrieve info for event conditions »: to do
3. The current condition ‹ user › + ‹ calendar › + ‹ event ›, where ‹ event › is a regular expression (e.g. condition Papa/maman works for Papa, Maman Papa/maman, I admit it’s quite specific to my needs)
4. Rights are not managed and it seems quite complex to me.

Open discussion

[pierre-gilles]

@Romuald_Pochet

I’ve just started the developments of what will also enter the heart of Gladys (and especially the UI part) Isn’t this a good way to work?

No problem, there was nothing negative in my message!!

@Romuald_Pochet

The reminder is managed via the reminder given by CalDav. But we would need to update the « calendar_event » data model to include the value;

This is exactly what is being debated. In my opinion, it’s more of a thing we would like to manage in the scene rather than in the calendar, because typically we might want several scenes to be triggered by the same event, for example:

• 30 minutes before the appointment, send me a Telegram notification
• 15 minutes before, if I haven’t left the house, play a sound in the house
• 5 minutes before, make all the living room lights flash!

In my opinion, the programming should be specified in the trigger rather than in the calendar, and it’s actually simpler to understand in terms of UX, I think.

@Romuald_Pochet

The current condition ‹ user › + ‹ calendar › + ‹ event ›, where ‹ event › is a regular expression (e.g. condition Papa/maman works for Papa, Maman Papa/maman, I admit it’s quite specific to my need)

On this point, perhaps we should propose several cases:

• Selection of a specific event (is this useful?)
• Event whose title contains this text (and on this point, we need to be clear in the UI, the word « regex » is not obvious to everyone )

@Romuald_Pochet

Rights are not managed and it indeed seems quite complex.

I think the discussion with @bertrandda should continue with this development in mind so that we can make something that is coherent overall

@Romuald_Pochet

Open discussion

That’s the goal

In any case, congratulations on the first development, it’s great! My remarks are only positive, the goal is mainly to move forward!