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
-
-
@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 $ -
@angeliKITTYx ok, close that window and open another and
try the node --version again -
closed the terminal, opened a new terminal…
kittypi@KITTYpi:~ $ node --version v22.19.0 kittypi@KITTYpi:~ $ cd MagicMirror kittypi@KITTYpi:~/MagicMirror $ node --version v22.19.0 kittypi@KITTYpi:~/MagicMirror $ -
@angeliKITTYx weird
Dowhich nodeGo to that folder
sudo mv node onode hash -r which node node —version -
kittypi@KITTYpi:~/MagicMirror $ cd .. kittypi@KITTYpi:~ $ which node /usr/local/node/bin/node ... kittypi@KITTYpi:/ $ cd usr kittypi@KITTYpi:/usr $ cd local kittypi@KITTYpi:/usr/local $ cd node kittypi@KITTYpi:/usr/local/node $ cd bin kittypi@KITTYpi:/usr/local/node/bin $ cd node bash: cd: node: Not a directory kittypi@KITTYpi:/usr/local/node/bin $ sudo mv node onode hash -r which node node —version /usr/local/bin/node node:internal/modules/cjs/loader:1386 throw err; ^ Error: Cannot find module '/usr/local/node/bin/—version' at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15) at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19) at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22) at Function._load (node:internal/modules/cjs/loader:1192:37) at TracingChannel.traceSync (node:diagnostics_channel:328:14) at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5) at node:internal/main/run_main_module:36:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v22.21.1 kittypi@KITTYpi:/usr/local/node/bin $ -
@angeliKITTYx i hate this editor on my phone changing the characters
do
node --versionit should report 22.21.1
thencd ~/MagicMirror npm run install-mm -
@sdetweil
it’s booting now! hurray! however, now I’m getting the package lock error when i try to complete the calendarext3 update and none of my events are populating. I have a thread up on someone else’s trouble shooting but I’m out of time this morning. I be back at it this afternoon. thank you again for all your help. -
@angeliKITTYx awesome. Thanks for the feedback
package-lock? Erase that file then do the update
There is a known bug affecting modules that have functions in their config like ext3. We are discussing ways to distribute these fixes.
-
Did you get the npm run install-mm done after verifying node version was correct?
-
@sdetweil
yes I did the npm run install-mm successfully.i got it updated, but now it’s angry again
[2026-04-29 18:51:43.521] [ERROR] [calendar] Could not expand event "WD CNU": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.522] [ERROR] [calendar] Could not expand event "Ortho": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.522] [ERROR] [calendar] Could not expand event "WD CNU": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.523] [ERROR] [calendar] Could not expand event "HVAC DUCTING FIX": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.524] [ERROR] [calendar] Could not expand event "Injection appt time TBD": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.524] [ERROR] [calendar] Could not expand event "Env. Regulations": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.525] [ERROR] [calendar] Could not expand event "Z4 training": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.526] [ERROR] [calendar] Could not expand event "Jury Duty ": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.527] [ERROR] [calendar] Could not expand event "MATH 260: Linear Algebra ": ical.expandRecurringEvent is not a function [2026-04-29 18:51:43.527] [INFO] [calendar] Broadcasting 0 events from https://calendar.google.com/calendar/ical/axxxxx/basic.ics. [2026-04-29 18:52:09.449] [LOG] [electron] Shutting down server... [2026-04-29 18:52:09.452] [LOG] [node_helper] Stopping module helper: updatenotification [2026-04-29 18:52:09.462] [LOG] [node_helper] Stopping module helper: calendar [2026-04-29 18:52:09.464] [LOG] [node_helper] Stopping module helper: MMM-CalendarExt3 [2026-04-29 18:52:09.469] [LOG] [node_helper] Stopping module helper: MMM-Jokes [2026-04-29 18:52:09.470] [LOG] [node_helper] Stopping module helper: weather [2026-04-29 18:52:09.473] [LOG] [node_helper] Stopping module helper: MMM-Todoist2 [2026-04-29 18:52:09.478] [LOG] [app] Node_helpers stopped ... kittypi@KITTYpi:~/MagicMirror $ node --version v22.21.1 kittypi@KITTYpi:~/MagicMirror $ -
@angeliKITTYx looks like you didn’t do that in the MagicMirror folder
cd ~/MagicMirror npm run install-mm -
I did it originally in the MM folder, but I ran it again and still getting the same errors
I did catch this before the entire terminal filled up with “: ical.expandRecurringEvent is not a function”
[2026-04-29 19:59:54.445] [LOG] [server] Starting server on port 8080 ... [2026-04-29 19:59:54.499] [ERROR] [unknown] (node:58997) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead. (Use `electron --trace-deprecation ...` to show where the warning was created) [2026-04-29 19:59:54.855] [LOG] [app] Server started ... [2026-04-29 19:59:54.858] [LOG] [node_helper] Connecting so``` -
@angeliKITTYx that means the install-mm did not work
Please do again and show the output
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