You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked my logs and found that one of my calendars was giving this exception (logs below). The event comes from Office 365, and I just need to confirm that the ical source is indeed invalid.
I've found that the event was created without a check in the "Use timezones" checkbox when creating events - I've tried recreating the series using that checkbox to see if anything changes. So far the ics feed is the same, but it could be delayed.
[2022-07-29 15:11:14 ERROR (MainThread) [custom_components.ical] Exception RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware in start_rules.rrule: Passe høns - Start: 2022-07-13 21:00:00 - RRule: vRecur({'FREQ': ['DAILY'], 'UNTIL': [datetime.datetime(2022, 7, 30, 19, 0, tzinfo=tzfile('/usr/share/zoneinfo/UTC'))], 'INTERVAL': [1]})[0m
No - the event is a while ago, so I haven't seen it (also haven't been looking very hard). But I'm actually most interested in knowing if the rule is a standards thing - because it might just be that the ical feed is invalid, and then the real issue is with, in my case, Microsoft.
I checked my logs and found that one of my calendars was giving this exception (logs below). The event comes from Office 365, and I just need to confirm that the ical source is indeed invalid.
I've found that the event was created without a check in the "Use timezones" checkbox when creating events - I've tried recreating the series using that checkbox to see if anything changes. So far the ics feed is the same, but it could be delayed.
The ical event:
The text was updated successfully, but these errors were encountered: