MMM-Remote-Control

KristjanESPERANTO

Node.js v20.18.1

@rkorell Thanks for the feedback and the good error description! I’ll optimize the error logging, but unfortunately you have to update to at least node 22. I recommend version 24.

For the current MagicMirror version, you also need at least version 22.

BKeyport

what’s with the microupdates? I’ve updated three times today. 🤣

S374n

4 updates today… :/ Kind of annoying to see the mirror changes the view with this notification.
anyway:

GUI looks better. Thanks!
First update changes my main.css - took me a while to figure it out and redo all my customizations.
Restart - doesn’t work. Shutdown i didn’t even try.
Restart Magicmirror2 - doesn’t work, says mm2 is not running.
Turn monitor on/off doesn’t work.
Minimize browser does it but then no way to revert. So point less, now need to reboot.

Any way to make it SSH from the phone? :)

rkorell

@KristjanESPERANTO

OK…

New version now shows the same error…
Actually my mirror works pretty fine…
So I hesitate to update node …
What are the risks - and if: How do I do update node?

Will my mirror run afterwards or do I have to upgrade the mirror as well?

Thanks for any advise!

Warmest regards,
Ralf

I’m not able to attach the logfile…
[2025-12-20T10_58_15_392Z-debug-0.log](Invalid file type. Allowed types are: .jpg, .jpeg, .png, .gif, .png, .jpg, .jpeg, .gif)

sdetweil

@rkorell to upgrade node use one of the tools

nvm or n

I prefer n
stop MagicMirror if running

sudo npm install n -g
sudo n 22.18
hash -r
node -v

Should confirm node is upgraded

Now we need to fix the MagicMirror dependencies

cd ~/MagicMirror 
rm -rf node_modules
npm install

Then start MagicMirror

In the future, if you want to upgrade MagicMirror, use my upgrade script and it will also upgrade node if necessary

sdetweil

@rkorell you can only upload pics here, you can paste some of the log into a message ( use the code block )

rkorell

@sdetweil
Dear Sam,
thanks for this.

Until now I had avoided to upgrade with the thought “never touch a running system” …
Now it seems to be time for an upgrade - because I like MMM-Remote-Control.
@kristjanesperanto said: " at least node 22. I recommend version 24" - would one of these versions be installed by your current upgrade-script?

Than I would feel much better using your script than doing it manually …

As far as I remember i had some local (code) modifications in standard-weather module - this would prevent your upgrade-script from upgrading, as far as I remember.
Is this still true? And if yes: There was a “force” ooption in the script?

Thanks a lot for your work!

Warmest regards,
Ralf

sdetweil

@rkorell force was if you already had started installing MM and had the latest code… NOT if you have code changes

the upgrade will report if files are changed and allow you to save them in git. but generally its intended to remind you where you made changes and do something about it…

the node upgrade should not impact the running MM… (I say that with ’ quote marks, cause I am not sure…)

WHY do you NEED the RemoteControl update?? if you don’t NEED it, then don’t take it…

sdetweil

@rkorell said in MMM-Remote-Control:

would one of these versions be installed by your current upgrade-scrip

today it will install node 22.18.0
after Jan 1 (2 weeks away) it will install 22.21.1 (for the next release)

rkorell

@sdetweil
Good point!
Unfortunately I’ve already DONE the upgrade of remote-control - and now it doesn’t work anymore :-)