MM doesn't start after last update

[matt216]

@JoeFranz I’m getting these vulkan warnings too - any idea what they/it is?! Doesn’t seem to affect my mirror working…

[sdetweil]

@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…

[JoeFranz]

@sdetweil

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 rejec

tion. 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

[sdetweil]

@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

[sdetweil]

@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 install

restart mm

[JoeFranz]

@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 :-)

[nechry]

@JoeFranz hello I also got, I think same issue, about 2 ical didn’t load. did you figure out the issue?

[JoeFranz]

No, unfortunately not… :-(

[sdetweil]

@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…

[sdetweil]

@JoeFranz lets get you back to working, move you back to whatever release worked…

stop mm if running

on the command line

git  tag -l 

to 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.0

if successful
then

rm -rf node_modules
npm install 

and give it a try