Bug in action 'Retrieve events from a calendar'

There is currently a bug with the Retrieve calendar events action.
The action takes into account reminders for an event scheduled in X days.

Either the processing must add to the phrase « reminder for: xxxx » or it must be excluded

Hi @spenceur, thanks for the feedback!

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:

  1. Which calendar provider you are using (iCloud, Google, Nextcloud, .ics link…) ?
  2. The range configured in the action (today, tomorrow, next X hours) ?
  3. The exact text that the action produced, and the actual date of the event ?
  4. Does this “reminder” also appear in Gladys’s Calendar page, on the reminder date ?
  5. 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.

I tag @bertrandda who works on these topics.

Hello unfortunately, I had to do a clean reinstall of Gladys :slight_smile:
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.

Sorry for the lack of additional help

Thanks @spenceur, actually your description is enough to understand the problem :slightly_smiling_face:

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.

Thanks again for reporting it!

Hi everyone!

This topic is now in development.

A PR has been opened to fix the one-day offset of the “all-day” events in the “Get calendar events” action:

Feel free to follow the PR, test (optional, especially for small requests) and give your feedback here if needed.

Hello,

The one-day offset of the « full-day » events in the « Retrieve calendar events » action has been fixed in Gladys Assistant 5.3.3.

The details are in the announcement: