Read the statement by Michael Teeuw here.
Default Calendar Not Loading Events After New MM Update
-
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. -
A workaround for users still having issues with the calendar. There was a problem with the
node-icalpackage for some events. This has just been fixed with a newnode-icalrelease (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.jsonandpackage-lock.jsonfiles, which would cause conflicts during the next MagicMirror update. Therefore, also run the following to restore them:
git restore package*.jsonYou will then have v0.26.0 installed - the
package.jsonfile say otherwise, but that doesn’t matter.Please give some feedback if that helps :-)
-
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
-
@doogy_rev can you show me the ~/MagicMirror/installers/upgrade.log
Maybe send it to me
Same userid at gmailIt is two part process, right?
-
Hi Sam,
Log sent to your gmail
Thanks
DoogyRev
-
@doogy_rev it looks like you tried it manually, git 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 it looks like you tried it manually, git 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?
-
@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 That worked, thanks very much.
-
@doogy_rev awesome… thanks for the feedback
-
My calendar also stopped showing events (from my Google calendar).
Running
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" forcefixed it for me. It worked like ‘Magic’ - pun intended.
Thank you!!
-
@Athlon ok, that means the manual upgrade failed. but pulled the new code
git pull && npm run install-mmmeans the git pull encountered a problem, and the npm run didn’t happen,m
but there is no log…can you send me the ~/MagicMirror/installers/upgrade.log so I can see what the problem might have been
same userid at gmail, thanks…
-
sent…
-
@Athlon replied
for others, this was a node version mismatch that cause the npm run install-mm to fail,
leaving the new source installed, but the dependencies NOT installed.so, something will fail… calendar for you
-
Reviving this… I’m having the same issues and got a little lost in the steps in the replies.
[2026-04-27 19:39:42.912] [ERROR] [calendar] Could not expand event "CHEM 122L": ical.expandRecurringEvent is not a function [2026-04-27 19:39:42.912] [INFO] [calendar] Broadcasting 0 events from https://calendar.google.com/calendar/ical/an.jusino%40gmail.com/private-74d08680c977c48e69171dadae3346d1/basic.ics. [2026-04-27 19:40:16.774] [LOG] [electron] Shutting down server...kittypi@KITTYpi:~/MagicMirror $ git pull && npm run install-mm Already up to date. > magicmirror@2.35.0 install-mm > npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev npm error code EBADENGINE npm error engine Unsupported engine npm error engine Not compatible with your version of node/npm: magicmirror@2.35.0 npm error notsup Not compatible with your version of node/npm: magicmirror@2.35.0 npm error notsup Required: {"node":">=22.21.1 <23 || >=24"} npm error notsup Actual: {"node":"v22.19.0","npm":"11.13.0"} npm error A complete log of this run can be found in: /home/kittypi/.npm/_logs/2026-04-27T23_48_16_062Z-debug-0.log -
@angeliKITTYx you are on node 22.19, and we need 22.21.1
If you use my scripted install or update then it will take care of that.
Because you did part of the install (git pull), the new version code is loaded
But not its dependencies, so MagicMirror won’t run correctlyYou could run my upgrade script with force instead of apply
As it won’t let you install/upgrade over the current level. -
@sdetweil thanks for the quick reply. I did the first line under the Update section and got the same results. All of the modules are working except CalEXT3 - it shows, but no events populate and I get all of those “not a function” errors.
I also tried running the second command in that section and got the same results. I’m probably missing a step somewhere…
kittypi@KITTYpi:~/MagicMirror $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" update log will be in /home/kittypi/MagicMirror/installers/upgrade.log doing test run = true, NO updates will be applied! Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v22.21.1 Installed Node version: v22.19.0 Node should be upgraded. Node.js upgrade defered, doing test run Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V10.9.4 Installed npm version: V11.13.0 No npm upgrade necessary. upgrading from version 2.35.0 to 2.35.0 bash: line 772: pm2: command not found fetching latest revisions Checking for modules with removed libraries updating dependencies for active modules with package.json files processing for module MMM-CalendarExt3 please wait ---------------------------------- skipped processing for MMM-CalendarExt3, doing test run processing complete for module MMM-CalendarExt3 processing for module MMM-Jokes please wait ---------------------------------- skipped processing for MMM-Jokes, doing test run processing complete for module MMM-Jokes processing for module MMM-Todoist2 please wait ---------------------------------- skipped processing for MMM-Todoist2, doing test run processing complete for module MMM-Todoist2 processing for module MMM-ISS-Live please wait ---------------------------------- skipped processing for MMM-ISS-Live, doing test run processing complete for module MMM-ISS-Live moving css contents to config kittypi@KITTYpi:~/MagicMirror $ -
@angeliKITTYx correct. It says doing test run , no changes will be made
The doc says this is a 2 part update process
Test, advise any issues , no changes
The second part, DoThe second line to copy ends with the word
apply
Which I want you to change to
force
-
@sdetweil
I fear I have made it even worse…kittypi@KITTYpi:~/MagicMirror $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" update log will be in /home/kittypi/MagicMirror/installers/upgrade.log doing test run = true, NO updates will be applied! Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v22.21.1 Installed Node version: v22.19.0 Node should be upgraded. Node.js upgrade defered, doing test run Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V10.9.4 Installed npm version: V11.13.0 No npm upgrade necessary. upgrading from version 2.35.0 to 2.35.0 bash: line 772: pm2: command not found fetching latest revisions Checking for modules with removed libraries updating dependencies for active modules with package.json files processing for module MMM-CalendarExt3 please wait ---------------------------------- skipped processing for MMM-CalendarExt3, doing test run processing complete for module MMM-CalendarExt3 processing for module MMM-Jokes please wait ---------------------------------- skipped processing for MMM-Jokes, doing test run processing complete for module MMM-Jokes processing for module MMM-Todoist2 please wait ---------------------------------- skipped processing for MMM-Todoist2, doing test run processing complete for module MMM-Todoist2 processing for module MMM-ISS-Live please wait ---------------------------------- skipped processing for MMM-ISS-Live, doing test run processing complete for module MMM-ISS-Live moving css contents to config kittypi@KITTYpi:~/MagicMirror $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force update log will be in /home/kittypi/MagicMirror/installers/upgrade.log doing test run = false Node currently installed. Checking version number. Minimum Node version: v22.21.1 Installed Node version: v22.19.0 installing correct version of node and npm, please wait sudo: n: command not found Check current Node installation ... Node currently installed. Checking version number. Minimum Node version: v22.21.1 Installed Node version: v22.19.0 Node should be upgraded. Installing Node.js ... using sudo n v22.21.1 force: line 446: sudo n v22.21.1 : command not found node version is Node.js installation Done! version=v22.19.0 Check current NPM installation ... NPM currently installed. Checking version number. Minimum npm version: V10.9.4 Installed npm version: V11.13.0 No npm upgrade necessary. want /var/swap=512MByte, checking existing: keeping it upgrading from version 2.35.0 to 2.35.0 force: line 772: pm2: command not found fetching latest revisions updating MagicMirror runtime, please wait npm error code EBADENGINE npm error engine Unsupported engine npm error engine Not compatible with your version of node/npm: magicmirror@2.35.0 npm error notsup Not compatible with your version of node/npm: magicmirror@2.35.0 npm error notsup Required: {"node":">=22.21.1 <23 || >=24"} npm error notsup Actual: {"node":"v22.19.0","npm":"11.13.0"} npm error A complete log of this run can be found in: /home/kittypi/.npm/_logs/2026-04-28T00_48_25_147Z-debug-0.log Checking for modules with removed libraries updating dependencies for active modules with package.json files processing for module MMM-CalendarExt3 please wait ---------------------------------- npm warn "install" is being parsed as a normal command line argument. npm warn Unknown cli config "--audit --no-fund --no-update-notifier". This will stop working in the next major version of npm. > mmm-calendarext3@1.12.4 postinstall > git submodule update --init --recursive Submodule path 'CX3_Shared': checked out 'c097e31c073007cf16e86f695bed1c807f581aef' up to date, audited 1 package in 1s found 0 vulnerabilities processing complete for module MMM-CalendarExt3 processing for module MMM-Jokes please wait ---------------------------------- npm warn "install" is being parsed as a normal command line argument. npm warn Unknown cli config "--audit --no-fund --no-update-notifier". This will stop working in the next major version of npm. up to date, audited 1 package in 1s found 0 vulnerabilities processing complete for module MMM-Jokes processing for module MMM-Todoist2 please wait ---------------------------------- npm warn "install" is being parsed as a normal command line argument. npm warn Unknown cli config "--audit --no-fund --no-update-notifier". This will stop working in the next major version of npm. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 added 50 packages, and audited 51 packages in 6s 4 packages are looking for funding run `npm fund` for details 6 vulnerabilities (4 moderate, 2 critical) Some issues need review, and may require choosing a different dependency. Run `npm audit` for details. processing complete for module MMM-Todoist2 processing for module MMM-ISS-Live please wait ---------------------------------- npm warn "install" is being parsed as a normal command line argument. npm warn Unknown cli config "--audit --no-fund --no-update-notifier". This will stop working in the next major version of npm. > mmm-iss-live@2.3.1 prepare > simple-git-hooks || true sh: 1: simple-git-hooks: not found up to date, audited 1 package in 967ms found 0 vulnerabilities processing complete for module MMM-ISS-Live moving css contents to config kittypi@KITTYpi:~/MagicMirror $ npm run start > magicmirror@2.35.0 start > node --run start:wayland /bin/sh: 1: ./node_modules/.bin/electron: not found -
@angeliKITTYx another fun time
Do
sudo npm install -g n sudo n 22.21.1 hash -r node -vIf it says 22.21.1
Then docd ~/MagicMirror npm run install-mmIf it says successful then
npm run start:x11
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login