Read the statement by Michael Teeuw here.
MM doesn't start after last update
-
Hello and happy new year :-)
Yesterday I updated to 2.26 using the script from sdetweil.
Unfortunately MM doesn’t start anymore :-(
Hope that someone can helpGreetings Jörg
/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines: 2|MagicMir | at node:internal/modules/cjs/loader:929:27 2|MagicMir | at Function._load (node:electron/js2c/asar_bundle:2:13327) 2|MagicMir | at Module.require (node:internal/modules/cjs/loader:1150:19) 2|MagicMir | at require (node:internal/modules/cjs/helpers:121:18) 2|MagicMir | at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-SoccerLiveScore/node_helper.js:10:15) 2|MagicMir | at Module._compile (node:internal/modules/cjs/loader:1271:14) 2|MagicMir | at Object..js (node:internal/modules/cjs/loader:1326:10) 2|MagicMir | at Module.load (node:internal/modules/cjs/loader:1126:32) 2|MagicMir | at node:internal/modules/cjs/loader:967:12 2|MagicMir | at Function._load (node:electron/js2c/asar_bundle:2:13327) 2|MagicMir | at Module.require (node:internal/modules/cjs/loader:1150:19) 2|MagicMir | at require (node:internal/modules/cjs/helpers:121:18) 2|MagicMir | at loadModule (/home/pi/MagicMirror/js/app.js:181:19) 2|MagicMir | (Use `electron --trace-warnings ...` to show where the warning was created) 2|MagicMir | [02.01.2024 08:21.55.970] [ERROR] (node:21245) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) 2|MagicMirror | Warning: vkCreateInstance: Found no drivers! 2|MagicMirror | Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER 2|MagicMirror | at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88) 2|MagicMirror | at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458) 2|MagicMirror | at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344) 2|MagicMirror | at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266) 2|MagicMirror | at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521) -
> magicmirror@2.26.0 start > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js [02.01.2024 12:11.41.006] [LOG] Starting MagicMirror: v2.26.0 [02.01.2024 12:11.41.016] [LOG] Loading config ... [02.01.2024 12:11.41.022] [DEBUG] config template file not exists, no envsubst [02.01.2024 12:11.42.733] [ERROR] (node:19253) UnhandledPromiseRejectionWarning: Error: Cannot find module 'node-fetch' Require stack: - /home/pi/MagicMirror/modules/MMM-SoccerLiveScore/node_helper.js - /home/pi/MagicMirror/js/app.js - /home/pi/MagicMirror/js/electron.js - /home/pi/MagicMirror/node_modules/electron/dist/resources/default_app.asar/main.js - at node:internal/modules/cjs/loader:1084:15 at Function.<anonymous> (node:electron/js2c/browser_init:2:116646) at Module._resolveFilename (/home/pi/MagicMirror/node_modules/module-alias/index.js:49:29) at node:internal/modules/cjs/loader:929:27 at Function._load (node:electron/js2c/asar_bundle:2:13327) at Module.require (node:internal/modules/cjs/loader:1150:19) at require (node:internal/modules/cjs/helpers:121:18) at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-SoccerLiveScore/node_helper.js:10:15) at Module._compile (node:internal/modules/cjs/loader:1271:14) at Object..js (node:internal/modules/cjs/loader:1326:10) at Module.load (node:internal/modules/cjs/loader:1126:32) at node:internal/modules/cjs/loader:967:12 at Function._load (node:electron/js2c/asar_bundle:2:13327) at Module.require (node:internal/modules/cjs/loader:1150:19) at require (node:internal/modules/cjs/helpers:121:18) at loadModule (/home/pi/MagicMirror/js/app.js:181:19) (Use `electron --trace-warnings ...` to show where the warning was created) [02.01.2024 12:11.42.736] [ERROR] (node:19253) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) Warning: vkCreateInstance: Found no drivers! Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:88) at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:458) at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344) at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266) at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521) -
@JoeFranz did u upgrade w my script? or manually
go to the module folder and do
npm install node-fetch@2
-
@sdetweil
It’s working again now, thank you very much :-) -
@JoeFranz I’m getting these vulkan warnings too - any idea what they/it is?! Doesn’t seem to affect my mirror working…
-
@matt216 I think the vulcan warnings are a side effect of another error…
can u send me that somefile.txt… same userid as here at gmail…
i don’t look at any personal info… so try not to filter it… -
MMM-Tado doesn’t start, here are the error messages :-(
/home/pi/.pm2/logs/MagicMirror-error.log last 15 lines: 1|MagicMir | at process.processTimers (node:internal/timers:512:7) 1|MagicMir | [02.01.2024 16:25.56.242] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 36) 1|MagicMir | [02.01.2024 16:30.56.239] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: TypeError: self.tadoClient.login is not a function 1|MagicMir | at Class.getData (/home/pi/MagicMirror/modules/MMM-Tado/node_helper.js:20:25) 1|MagicMir | at Timeout._onTimeout (/home/pi/MagicMirror/modules/MMM-Tado/node_helper.js:103:22) 1|MagicMir | at listOnTimeout (node:internal/timers:569:17) 1|MagicMir | at process.processTimers (node:internal/timers:512:7) 1|MagicMir | [02.01.2024 16:30.56.240] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 40) 1|MagicMir | [02.01.2024 16:35.56.242] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: TypeError: self.tadoClient.login is not a function 1|MagicMir | at Class.getData (/home/pi/MagicMirror/modules/MMM-Tado/node_helper.js:20:25) 1|MagicMir | at Timeout._onTimeout (/home/pi/MagicMirror/modules/MMM-Tado/node_helper.js:103:22) 1|MagicMir | at listOnTimeout (node:internal/timers:569:17) 1|MagicMir | at process.processTimers (node:internal/timers:512:7) 1|MagicMir | [02.01.2024 16:35.56.243] [ERROR] (node:1226) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 44) 1|MagicMir | /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT -
@JoeFranz yeh tado seems to be affected by a change in how nodejs does context scoping.
I’ll try to make fork in the morning
-
@JoeFranz try my fork
rename the current module folder out of the way
cd ~/MagicMirror/modules git clone https://github.com/sdetweil/MMM-Tado cd MMM-Tado npm installrestart mm
-
@sdetweil
That worked, thank you very much :-)
Now I’m only missing two calendars that aren’t displayed.
One from icloud and one from google. Other iCloud calendars are displayed. I hope I find the error :-) -
@JoeFranz hello I also got, I think same issue, about 2 ical didn’t load. did you figure out the issue?
-
No, unfortunately not… :-(
-
@JoeFranz still trying to find the cause…
so far every cal url I have received works great on my local MM systems. 2.25 and 2.26, x86, pi3, pi4 and pi5.
so, i’m not use what is going on…
in all the cases if the cal is parsed the events are broadcast but cal says no events… ???
weird…
-
@JoeFranz lets get you back to working, move you back to whatever release worked…
stop mm if running
on the command line
git tag -lto list the tags (checkpoints in the list f changes, made at every release)
you should see a list
then whichever release you were last working on do
git checkout -b tempbranch tags/v??? the number, 2.25.0 or whatever like git checkout -b tempbranch tags/v2.25.0if successful
thenrm -rf node_modules npm installand give it a try
-
@sdetweil
Don’t work so hard…
It was just a calendar where the appointments weren’t displayed. I have now copied these into another calendar and they are now displayed there. I’m glad that everything else is working fine again, thank you for your help! :-)
The command “git tag -l” only shows me up to version v2.2.0.
I think I’ll leave it like that for now…:winking_face: -
@JoeFranz weird. but thanks for the info
-
@sdetweil > git tag -l
Sam,
I am running MM 2.24.0 if I update to 2.26 Do you think it will break MMM-RTSPStream? I have 4 different instances of it running in carousel. We love the way it works showing us video of all 4 sides of our house outside. -
@plainbroke no idea, don’t upgrade
if u see the new update message, just adddisabled: true
to the updatenotifications module
and restart mm -
Ok thanks for the honest answer.
You the man. -
@plainbroke there is NEVER any reason to upgrade, unless there is something you NEED .
if it ain’t broke, don’t ‘fix’ it…
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