I looked at the code: the action only retrieves events whose start time falls within the selected range, and during synchronization, Gladys does not record alarms/reminders for an event (they remain attached to the event). So if a “reminder” comes up, it means a real event exists in Gladys on that date, and I would like to understand where it comes from. Can you tell me:
Which calendar provider you are using (iCloud, Google, Nextcloud, .ics link…) ?
The range configured in the action (today, tomorrow, next X hours) ?
The exact text that the action produced, and the actual date of the event ?
Does this “reminder” also appear in Gladys’s Calendar page, on the reminder date ?
If possible, the .ics export of the event in question (you can hide personal info).
With this, we will know if it is a separate event created by your calendar app (in this case, you just need to uncheck this calendar in the action) or a synchronization issue on Gladys’s side.
Hello unfortunately, I had to do a clean reinstall of Gladys
Too many scenes, etc., and with all the updates since the beginning, some scenes were no longer relevant. BREFFF ^^
For the calendar, I was using the one on my NAS.
From what I remember, I had an event the next day all day with a reminder the day before.
And when I retrieved the calendar events, it retrieved the event for the next day, I thought it was related to the reminder.
Thanks @spenceur, actually your description is enough to understand the problem
It’s not the reminder. Gladys never stores reminders, they remain attached to the event. The problem comes from the all-day event itself, which was set one day too early.
Gladys records an all-day event at midnight Paris time, so at 23:00 UTC the day before (22:00 in summer). The “Retrieve calendar events” action was looking for it at midnight UTC. Result, with the “Today” range:
it returned the all-day events from tomorrow;
it forgot those from today.
The “Tomorrow” range had the same offset. Events with a start time are not affected.
I reproduced the bug and opened a GitHub issue: #3368
The fix will arrive in a future version. There will be nothing to do on your side, no resynchronization or scene modification.