ical-sensor-homeassistant
ical-sensor-homeassistant copied to clipboard
`Exception RRULE UNTIL values must be specified in UTC when DTSTART is timezone-aware in start_rules.rrule`
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
The ical event:
BEGIN:VEVENT
RRULE:FREQ=DAILY;UNTIL=20220730T190000Z;INTERVAL=1
UID:040000008200E00074C5B7101A82E00800000000248F44D03D95D801000000000000000
0100000004E3A63849F5CC34D85174A1A7FDFB8A8
SUMMARY:Passe høns
DTSTART;TZID=(no TZ description):20220713T210000
DTEND;TZID=(no TZ description):20220713T211500
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20220729T131933Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
I have similar issue also. Any solution available?
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.
@LordMike i do have this issue a lot. Canyou explain the exact work aarround with the timezones?
Iirc I didn’t have a workaround. The issue disappeared when the event disappeared.