Default Calendar Not Loading Events After New MM Update

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 :-)

doogy_rev

I have just updated to the latest version and have the same issue of the Calendar not loading.

I have tried the above suggestions but still not able to load gmail calendars

I did use the script to update MM and all dependancies

Any help appreciated

Thanks

DoogyRev

sdetweil

@doogy_rev can you show me the ~/MagicMirror/installers/upgrade.log

Maybe send it to me
Same userid at gmail

It is two part process, right?

doogy_rev

Hi Sam,

Log sent to your gmail

Thanks

DoogyRev

sdetweil

@doogy_rev it looks like you tried it manually, hit pull, and the latest code was already present

local version 2.35.0 already same as master 2.35.0

The upgrade by default will not upgrade over the existing version

To fix, rerun and change the parm from apply to force

doogy_rev

@sdetweil said:

@doogy_rev it looks like you tried it manually, hit pull, and the latest code was already present

local version 2.35.0 already same as master 2.35.0

The upgrade by default will not upgrade over the existing version

To fix, rerun and change the parm from apply to force

ok, so I know enough to be dangerous, what is the command I should be committing?

sdetweil

@doogy_rev if you copy paste the second upgrade command from my script GitHub repo, you will see the word

apply

At the end

Change that to

force

And hit enter

sdetweil