@sdetweil

hey there,

false alarm… i think. After the pi update the problem was gone

Sam,

100% right! bad move on my part.
But yes i did run your script 2x, and used apply. Force is not mentioned on https://github.com/sdetweil/MagicMirror_scripts

So ran it again with force at the and…
This must be a new record, the fastest fix!
Not a single errog line in the log!

Tnx Sam

ps if u dont mind, i’ll be saving this command for later updates

Hey Guys

Still a noob at this, just love the mirror for daily use, info, etc

So i decided yo run the 1 july update.
(how i hate these updates, they rarely go well)

got some errors back, other people had them as well
npm error code EBADENGINE
npm error engine Unsupported engine
npm error engine Not compatible with your version of node/npm: magicmirror@2.32.0
npm error notsup Not compatible with your version of node/npm: magicmirror@2.32.0
npm error notsup Required: {“node”:“>=22.14.0”}
npm error notsup Actual: {“npm”:“10.8.2”,“node”:“v20.18.1”}

so i ran SdetWeil script to fix all
now MM starts… until 3 seconds later, electron crashes

0|mm | ### SYSTEM: manufacturer: ; model: ; virtual: false
0|mm | ### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: arm64; kernel: 6.12.34+rpt-rpi-v8
0|mm | ### VERSIONS: electron: 32.2.7; used node: 22.14.0; installed node: 22.14.0; npm: 10.9.2; pm2: 5.4.3
0|mm | ### OTHER: timeZone: Europe/Amsterdam; ELECTRON_ENABLE_GPU: undefined
0|mm | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT

SO what oh what could it be.

What are we gonne do? What log do you need?
Much appreciated.

So I ran the script, again, only now I applied FORCE at teh end
result:
ebian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Jan 13 16:27:51 2025 from 192.168.2.127
pi@pi-mirror:~ $ bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” force
update log will be in /home/pi/MagicMirror/installers/upgrade.log
doing test run = false
Node currently installed. Checking version number.
Minimum Node version: v20.18.1
Installed Node version: v20.18.1
Check current Node installation …
Node currently installed. Checking version number.
Minimum Node version: v20.18.1
Installed Node version: v20.18.1
No Node.js upgrade necessary.
Check current NPM installation …
NPM currently installed. Checking version number.
Minimum npm version: V10.8.2
Installed npm version: V10.8.2
No npm upgrade necessary.

want /var/swap=200MByte, checking existing: keeping it
saving custom.css
upgrading from version 2.30.0 to 2.30.0
fetching latest revisions
updating MagicMirror runtime, please wait

the screen did not change, so i pressed enter, and new info came up.

magicmirror@2.30.0 postinstall
npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully!
"

magicmirror@2.30.0 install-vendor
echo "Installing vendor files …
" && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing vendor files …

changed 3 packages in 11s

magicmirror@2.30.0 install-fonts
echo "Installing fonts …
" && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

Installing fonts …

changed 2 packages in 7s
MagicMirror² installation finished successfully!

then it started checking all my modules, no changes there

But all is well again and the mirror is running
So again Sam, tnx a milion!
2bad i keep running into these errors

A JavaScript error occurred in the main process
0|mm | Uncaught Exception:
0|mm | Error: Cannot find module ‘undici’

so after updateing the mirror and the pi this is my error
I have rebooted and have ran sdetweil fix-it-all script with apply.

But helas…

Mirror down mayday mayday

@sdetweil

hey there,

false alarm… i think. After the pi update the problem was gone

Hi there,

Tinkering can be fun, but is mostly frustrating.
Working on my mirror hoping to get a physical button to work, i ran into this error
/home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT

@sdetweil yes we have talked before, and yes I have tried the repair script using apply
which worked great last time

what changed after all was fine

• tinkerd with python script to check if the button was working
• disconnected the button to eliminate possible interference
• raspian updates were installed
• changed mm-carousel module version from barnabycolby to shbatm
• several pi reboots

let me know if you want more info
or when you have the solution

cheers!

@sdetweil

WOW that did alot… i think
but you sure now your stuf… problem fixed. I got my calender back
TNX!

here are the last lines of the log
----------------------------------
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 48 packages, and audited 49 packages in 8s

2 packages are looking for funding
run npm fund for details

2 moderate severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.

processing complete for module MMM-SystemStats

restoring custom.css
removing git alias
Upgrade ended - Sun Oct 20 17:53:11 CEST 2024

@sdetweil

Yes node -v
v20.9.0

Yes the install script was applied with apply
bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply

If you want i can try and zip and post the upgrade.log

Could not find anything helpfull on the web, of this forum so here goes.

MM was running fine until latest update. Weather stopped working.,
Fixed it by using the sample settings, they changed from openweather to openmeto. ok, no prob.

But now, dont ask, calender and newsfeed keep loading.
I tried;

• git pull in Magic mirror folder
• ran npm install node-fetch@2 in Magic mirror and calender module folder
• ran sdetweil repair script (
• updated Pi3, running bookwork

the log shows this
0|mm | [2024-10-18 14:59:19.435] [ERROR] Whoops! There was an uncaught exception…
0|mm | [2024-10-18 14:59:19.448] [ERROR] ReferenceError: fetch is not defined
0|mm | at fetchCalendar (/home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js:51:3)
0|mm | at CalendarFetcher.startFetch (/home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js:96:3)
0|mm | at Class.createFetcher (/home/pi/MagicMirror/modules/default/calendar/node_helper.js:79:11)
0|mm | at Class.socketNotificationReceived (/home/pi/MagicMirror/modules/default/calendar/node_helper.js:15:9)
0|mm | at Socket. (/home/pi/MagicMirror/js/node_helper.js:91:10)
0|mm | at Socket.onevent (/home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:462:26)
0|mm | at Socket._onpacket (/home/pi/MagicMirror/node_modules/socket.io/dist/socket.js:430:22)
0|mm | at /home/pi/MagicMirror/node_modules/socket.io/dist/client.js:214:24
0|mm | at process.processTicksAndRejections (node:internal/process/task_queues:78:11)

Strange, but have Hyper-v debian running with MM and no problem there

Anyone?

Hey there,

Great work on this module. But you say you are not an experienced programmer? well, compared to me…
not to sound lazy, but any change you could convert from csv to json query like thingy?
as seen on the home automation sites, people query http://json.mijnafvalwijzer.nl/?method=postcodecheck&postcode=&street=&huisnummer=&toevoeging=&platform=phone&langs=nl&

and get the results needed
(https://community.home-assistant.io/t/garbage-pickup-date-mijnafvalwijzer-nl-custom-component/34631/12)

please be honest, no is also an answer and I would completely understand.
… but i thought you might like a challenge ;-)