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?

hrt13

@sdetweil Hi, I am having the same problem since upgrading this morning (MM v2.35)

5 calendars, all from Google

Platform: Raspberry Pi3 B
OS: Debian GNU/Linux 11 (bullseye)

I haven’t tried regenerating the calendar links, should I?

sdetweil

@hrt13 shouldn’t need to

Are there any errors reported in the console log where you start MagicMirror?

If using pm2, then

pm2 logs —lines=xxx
Xxx is the number of latest lines to display, default 15
You might need 100

hrt13

@sdetweil Using pm2, I see a lot of “could not expand event” errors. Here’s one:

" [2026-04-02 12:29:21.274] [ERROR] [calendar] Could not expand event “Hockey vs. C”: ical.expandRecurringEvent is not a function"

Thanks

sdetweil

@hrt13 awesome to help could you find that event

curl -sL the_url_for_calendar >somefile.txt

Then edit somefile.txt and search for that title
Copy
Begin:vevent
…
End:vevent

And paste here. In code block
Edit Any info that might identify you, just dont delete any lines

hrt13

@sdetweil

I think this is it, it may be in the past (I’ll look for a more current one, I didn’t think I was getting events from the past), also, sorry about the ^M’s:

BEGIN:VEVENT
DTSTART:20150228T005000Z
DTEND:20150228T022000Z
DTSTAMP:20260402T201324Z
UID:somenumber@google.com
CREATED:20150130T132500Z
LAST-MODIFIED:20150130T132500Z
LOCATION:GIH - Logsdon
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Hockey vs. C
TRANSP:OPAQUE
END:VEVENT

sdetweil

@hrt13 is there one on a repeating schedule?

We shouldn’t expand one if it doesn’t have an rrule

hrt13

@sdetweil said:

There are some recent repeating events though I’m not sure any show in the logs. I’ll see if I can find some new events. Looking at the logs again, it seems it’s retrieving lots of past events which, of course, wouldn’t show on the calendar. The latest I’ve seen so far is an event from Jan 2026.

hrt13

@sdetweil this is definitely a repeating schedule

Log file error:
[2026-04-02 19:59:16.671] [ERROR] [calendar] Could not expand event “Tax Day”: ical.expandRecurringEvent is not a function

curl -sL output

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Holidays in United States
X-WR-TIMEZONE:UTC
X-WR-CALDESC:Holidays and Observances in United States
.
.
.
BEGIN:VEVENT
DTSTART;VALUE=DATE:20220418
DTEND;VALUE=DATE:20220419
DTSTAMP:20260403T003912Z
UID:20220418_clveaq2fmqp95elk3vma4ifhcs@google.com
CLASS:PUBLIC
CREATED:20240603T101345Z
DESCRIPTION:Observance\nTo hide observances\, go to Google Calendar Setting
 s > Holidays in United States
LAST-MODIFIED:20240603T101345Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Tax Day
TRANSP:TRANSPARENT
END:VEVENT
.
.
.
BEGIN:VEVENT
DTSTART;VALUE=DATE:20260415
DTEND;VALUE=DATE:20260416
DTSTAMP:20260403T003912Z
UID:20260415_fkehtfbgrr6j65q23flu2k5vu0@google.com
CLASS:PUBLIC
CREATED:20240603T101355Z
DESCRIPTION:Observance\nTo hide observances\, go to Google Calendar Setting
 s > Holidays in United States
LAST-MODIFIED:20240603T101355Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Tax Day
TRANSP:TRANSPARENT
END:VEVENT

sdetweil

@hrt13 hmm. A repeating event has one vevent, with an rrule line that describes how it repeats

KristjanESPERANTO

@hrt13 said:

[2026-04-02 19:59:16.671] [ERROR] [calendar] Could not expand event “Tax Day”: ical.expandRecurringEvent is not a function

Looks like you didn’t update the dependencies after you pulled the new MM version.

Please run node --run install-mm and check again.

hrt13

@KristjanESPERANTO said:

node --run install-mm

trying it now, it is taking a while. Will let you know.
I used mmpm to update, I guess it doesn’t update the dependencies.

KristjanESPERANTO

A workaround for users still having issues with the calendar. There was a problem with the node-ical package for some events. This has just been fixed with a new node-ical release (v0.26.0).

To use the new version, run this command in the MagicMirror directory:
npm install node-ical@latest.

Note that this will change your package.json and package-lock.json files, which would cause conflicts during the next MagicMirror update. Therefore, also run the following to restore them:
git restore package*.json

You will then have v0.26.0 installed - the package.json file say otherwise, but that doesn’t matter.

Please give some feedback if that helps :-)