A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
Default Calendar Not Loading Events After New MM Update
-
@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 -
kittypi@KITTYpi:~/MagicMirror $ sudo npm install -g n sudo n 22.21.1 hash -r node -v sudo: npm: command not found sudo: n: command not found v22.19.0 kittypi@KITTYpi:~/MagicMirror $ -
-
@sdetweil
still no luck :(
I’m logging off for the evening, but I’ll check back in tomorrow. Thank you for all the help you provide!kittypi@KITTYpi:~/MagicMirror $ sudo apt update sudo apt install nodejs Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: libbasicusageenvironment1 libgroupsock8 liblivemedia77 linux-headers-6.12.25+rpt-common-rpi linux-headers-6.12.25+rpt-rpi-2712 linux-headers-6.12.25+rpt-rpi-v8 linux-image-6.12.25+rpt-rpi-2712 linux-image-6.12.25+rpt-rpi-v8 linux-kbuild-6.12.25+rpt python3-v4l2 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-ares2 libnode108 libuv1 node-acorn node-busboy node-cjs-module-lexer node-undici node-xtend nodejs-doc Suggested packages: npm The following NEW packages will be installed: libc-ares2 libnode108 libuv1 node-acorn node-busboy node-cjs-module-lexer node-undici node-xtend nodejs nodejs-doc 0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded. Need to get 14.2 MB of archives. After this operation, 66.5 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://deb.debian.org/debian bookworm/main arm64 libc-ares2 arm64 1.18.1-3 [99.2 kB] Get:2 http://deb.debian.org/debian bookworm/main arm64 libuv1 arm64 1.44.2-1+deb12u1 [130 kB] Get:3 http://deb.debian.org/debian bookworm/main arm64 node-xtend all 4.0.2-3 [3,932 B] Get:4 http://deb.debian.org/debian bookworm/main arm64 nodejs arm64 18.20.4+dfsg-1~deb12u1 [319 kB] Get:5 http://deb.debian.org/debian bookworm/main arm64 node-acorn all 8.8.1+ds+~cs25.17.7-2 [128 kB] Get:6 http://deb.debian.org/debian bookworm/main arm64 node-cjs-module-lexer all 1.2.2+dfsg-5 [30.1 kB] Get:7 http://deb.debian.org/debian bookworm/main arm64 node-busboy all 1.6.0+~cs2.6.0-2 [16.9 kB] Get:8 http://deb.debian.org/debian bookworm/main arm64 node-undici all 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4 [285 kB] Get:9 http://deb.debian.org/debian bookworm/main arm64 libnode108 arm64 18.20.4+dfsg-1~deb12u1 [9,565 kB] Get:10 http://deb.debian.org/debian bookworm/main arm64 nodejs-doc all 18.20.4+dfsg-1~deb12u1 [3,579 kB] Fetched 14.2 MB in 4s (3,796 kB/s) Selecting previously unselected package libc-ares2:arm64. (Reading database ... 171415 files and directories currently installed.) Preparing to unpack .../0-libc-ares2_1.18.1-3_arm64.deb ... Unpacking libc-ares2:arm64 (1.18.1-3) ... Selecting previously unselected package libuv1:arm64. Preparing to unpack .../1-libuv1_1.44.2-1+deb12u1_arm64.deb ... Unpacking libuv1:arm64 (1.44.2-1+deb12u1) ... Selecting previously unselected package node-xtend. Preparing to unpack .../2-node-xtend_4.0.2-3_all.deb ... Unpacking node-xtend (4.0.2-3) ... Selecting previously unselected package nodejs. Preparing to unpack .../3-nodejs_18.20.4+dfsg-1~deb12u1_arm64.deb ... Unpacking nodejs (18.20.4+dfsg-1~deb12u1) ... Selecting previously unselected package node-acorn. Preparing to unpack .../4-node-acorn_8.8.1+ds+~cs25.17.7-2_all.deb ... Unpacking node-acorn (8.8.1+ds+~cs25.17.7-2) ... Selecting previously unselected package node-cjs-module-lexer. Preparing to unpack .../5-node-cjs-module-lexer_1.2.2+dfsg-5_all.deb ... Unpacking node-cjs-module-lexer (1.2.2+dfsg-5) ... Selecting previously unselected package node-busboy. Preparing to unpack .../6-node-busboy_1.6.0+~cs2.6.0-2_all.deb ... Unpacking node-busboy (1.6.0+~cs2.6.0-2) ... Selecting previously unselected package node-undici. Preparing to unpack .../7-node-undici_5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4_all.deb ... Unpacking node-undici (5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4) ... Selecting previously unselected package libnode108:arm64. Preparing to unpack .../8-libnode108_18.20.4+dfsg-1~deb12u1_arm64.deb ... Unpacking libnode108:arm64 (18.20.4+dfsg-1~deb12u1) ... Selecting previously unselected package nodejs-doc. Preparing to unpack .../9-nodejs-doc_18.20.4+dfsg-1~deb12u1_all.deb ... Unpacking nodejs-doc (18.20.4+dfsg-1~deb12u1) ... Setting up node-cjs-module-lexer (1.2.2+dfsg-5) ... Setting up libc-ares2:arm64 (1.18.1-3) ... Setting up libuv1:arm64 (1.44.2-1+deb12u1) ... Setting up nodejs-doc (18.20.4+dfsg-1~deb12u1) ... Setting up node-xtend (4.0.2-3) ... Setting up node-busboy (1.6.0+~cs2.6.0-2) ... Setting up node-undici (5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4) ... Setting up node-acorn (8.8.1+ds+~cs25.17.7-2) ... Setting up libnode108:arm64 (18.20.4+dfsg-1~deb12u1) ... Setting up nodejs (18.20.4+dfsg-1~deb12u1) ... update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode Processing triggers for man-db (2.11.2-2) ... Processing triggers for libc-bin (2.36-9+rpt2+deb12u13) ... kittypi@KITTYpi:~/MagicMirror $ node -v v22.19.0 kittypi@KITTYpi:~/MagicMirror $ sudo npm install -g n sudo n 22.21.1 hash -r node -v sudo: npm: command not found sudo: n: command not found v22.19.0 -
@angeliKITTYx so much fun. I hate when the tools only do half a job
sudo apt install npmThen
npm -vThen
sudo npm install -g n sudo n 22.21.1 hash -r node -v -
@sdetweil
it is just refusing to take 22.21.1... Setting up node-es-abstract (1.20.4+~cs26.27.47-1) ... Setting up node-webassemblyjs (1.11.4+dfsg+~cs10.11.17-2) ... Setting up node-util (0.12.5+~1.0.10-1) ... Setting up node-babel-plugin-lodash (3.3.4+~cs2.0.1-6) ... Setting up node-jest-debbundle (29.3.1~ds1+~cs70.48.25-2) ... Setting up node-assert (2.0.0+~cs3.9.8-2) ... Setting up webpack (5.75.0+dfsg+~cs17.16.14-1+deb12u1) ... Setting up node-parse-json (5.2.0+~cs5.1.7-1) ... Setting up node-read-pkg (5.2.0-2) ... Setting up node-istanbul (0.4.5+repack10+~cs97.25.57-3) ... Setting up node-tape (5.6.1+~cs8.20.19-1) ... Setting up node-css-loader (6.7.2+~cs14.0.11-1) ... Setting up node-tap (16.3.2+ds1+~cs50.8.16-1+deb12u1) ... Setting up node-deep-equal (2.1.0+~cs31.12.80-1) ... Setting up npm (9.2.0~ds1-1) ... Processing triggers for man-db (2.11.2-2) ... kittypi@KITTYpi:~/MagicMirror $ npm -v 11.13.0 kittypi@KITTYpi:~/MagicMirror $ sudo npm install -g n sudo n 22.21.1 hash -r node -v added 1 package in 2s installing : node-v22.21.1 mkdir : /usr/local/n/versions/node/22.21.1 fetch : https://nodejs.org/dist/v22.21.1/node-v22.21.1-linux-arm64.tar.xz copying : node/22.21.1 installed : v22.21.1 (with npm 10.9.4) Note: the node command changed location and the old location may be remembered in your current shell. old : /usr/bin/node new : /usr/local/bin/node If "node --version" shows the old version then start a new shell, or reset the location hash with: hash -r (for bash, zsh, ash, dash, and ksh) rehash (for csh and tcsh) v22.19.0 kittypi@KITTYpi:~/MagicMirror $ node --version v22.19.0 kittypi@KITTYpi:~/MagicMirror $ $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" bash: $: command not found -
The last command you have an extra leading $
kittypi@KITTYpi:~/MagicMirror $ $ bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" bash: $: command not foundWhen you copy/paste you only need to hit the little rectangle button at the en
But you dont need all that . The code is downloaded
Just do
cd ~/MagicMirror npm run install-mm -
how do i do percussive maintenance on code xD
kittypi@KITTYpi:~/MagicMirror $ cd ~/MagicMirror npm run install-mm > 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-28T20_16_16_675Z-debug-0.log kittypi@KITTYpi:~/MagicMirror $ -
@angeliKITTYx the end of your prior log post says 22.21.1 is installed
installing : node-v22.21.1 mkdir : /usr/local/n/versions/node/22.21.1 fetch : https://nodejs.org/dist/v22.21.1/node-v22.21.1-linux-arm64.tar.xz copying : node/22.21.1 installed : v22.21.1 (with npm 10.9.4) <-----are you in the same terminal window??
if so, you needhash -rto capture the path change
do
which nodeso we can see where it it located…
-
all the same terminal window. i don’t have anything else open. i know it says 22.21.1, but then node version says 19… very odd.
kittypi@KITTYpi:~/MagicMirror $ hash -r kittypi@KITTYpi:~/MagicMirror $ which node /usr/local/node/bin/node kittypi@KITTYpi:~/MagicMirror $ node --version v22.19.0 kittypi@KITTYpi:~/MagicMirror $
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