Default Calendar Not Loading Events After New MM Update

inteeraymee

Please help!

I just updated my MM to the new version and right after doing that my calendar would not load any events. Prior to the update it was working fine. Is there anything in the config I need to tweak? Everything else seems to be working fine.

Thanks in advance!

sdetweil

@inteeraymee can you tell us more?

Where is your calendar sourced? Google, Apple, caldav,
How did you update to latest MagicMirror

How do you start MagicMirror? Pm2, or some other way

HeikoGr

@sdetweil @inteeraymee

I have the same issue after updating from MagicMirror 2.34.0 to 2.35.0.

In my case this is not a general calendar config problem and not an auth/fetch problem either. Some calendars still load fine, others fail right after the update, which pointed me to a parser regression.

What I found:

MagicMirror 2.34.0 used node-ical 0.22.1
MagicMirror 2.35.0 uses node-ical 0.25.6
The affected calendars are fetched successfully with HTTP 200
The failure happens during ICS parsing
These are the two of the log lines I get:

[ERROR] [calendar] https://<server>/remote.php/dav/calendars/xx1/?export - iCal parsing failed: Cannot parse: 1-01-15T12:00:00Z
[DEBUG] [calendar] Parsed iCal data from https://<server>/remote.php/dav/calendars/xx2/?export with 130 entries.

The important detail in the broken ICS files is this VTIMEZONE block:

BEGIN:VTIMEZONE
TZID:W. Europe Standard Time
BEGIN:DAYLIGHT
DTSTART:00010325T020000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:00011028T030000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
END:STANDARD
END:VTIMEZONE

I tested the exact same ICS file with both node-ical versions:

node-ical 0.22.1: parses successfully
node-ical 0.25.6: fails with Cannot parse: 1-01-15T12:00:00Z
I also verified that if I remove only that W. Europe Standard Time VTIMEZONE block from the failing ICS, the file parses again with node-ical 0.25.6.

So the problem seems to be a regression in node-ical 0.25.x when resolving VTIMEZONE definitions with year 0001 in DTSTART. The calendar fetch itself succeeds; the crash happens while parsing timezone metadata.

This may especially affect calendars coming from Outlook/Exchange/Nextcloud imports, because W. Europe Standard Time looks like a Microsoft-style timezone definition.

HeikoGr

i filed an issue: https://github.com/jens-maus/node-ical/issues/495

it could be an edge case on my side.
@inteeraymee by any chance: did you use emClient anytime in the past?

only workaround for my setup is to pin to v2.34.0 .
Updating the calendars might be the best solution for me…

sdetweil

@HeikoGr we originally never parsed the vtimezone sections

inteeraymee

@sdetweil I have about 5 that are sourced in Google and another 2 or so that are subscription-based (i.e. sports teams).

The way that I am starting MM is via ssh since my monitor is inside a frame up on a wall, making it a challenge to connect directly. The script I use is:

sudo -u rudin-fam
DISPLAY=:0
XAUTHORITY=/home/rudin-fam/.Xauthority
nohup chromium --kiosk http://localhost:8080
–noerrdialogs
–disable-infobars
–disable-session-crashed-bubble
–disable-restore-session-state
>/dev/null 2>&1 &

sdetweil

@inteeraymee that’s the display side, where is the server side?