@MZ-BER what do you think of these new messages Checking for modules with removed libraries require for node-fetch in module MMM-NewsAPI not found in package.json bypass installing node-fetch for module MMM-NewsAPI , doing test run updating dependencies for active modules with package.json files processing for module birthdaylist please wait ---------------------------------- skipped processing for birthdaylist, doing test run processing complete for module birthdaylist

@sdetweil @karsten13 Message from MMM-OnSpotify. Its now fixed in V3.1.0, both the icon color change (now the helper css classes are loaded on a separated file), and the clock translation error (locale settings were getting overwritten by the module instance of the moment library). Installed the update and problem solved. Thanks for helping!

@Syosse and your troubles convinced me to look at the pm2 setup problem from the script, and I was able to see the issue and fix it for others… thanks… Sam

@hikano765 a better thing would be to change the address: to address:“0.0.0.0” then it will listen on all the active network adapters . you will also have to fix the ipWhitelist to allow apps from outside systems to connect while you are developing your mm solution it’s easiest to do ipWhitelist:[], to allow apps from any system on your local betwork

@1eretoile c’est exact

@Laz As all of my systems are behind a firewall - I’ve opened the Mirror to “public” access by using the config of var config = { address: "0.0.0.0", port: 8080, ipWhitelist: [], ... then, I simply load the mirror in my main computer’s browser with http://mirror:8080 and use the devtools of my browser to view the errors and such.

@Cliff365 sorry typo in command, my phone thought it knew better!!! sudo apt-get remove nodejs -y

@sdetweil Seems to be working great! Thank you very much for taking the time to make this a multi-instance module! Also great that you eliminated the need for npm install node-fetch@2. Even though I don’t know very much about java script, I understand it much better than these horoscopes :grinning_squinting_face:

@sdetweil this works thank you.

@rmcon great that you got it working on the test run, mostly currently it’s looking for mm files you might have changed for some reason, and conflict w the new release. most of the other issues I handle, upgrade node, npm and pm2 if needed. and in this release on pi0, increase swap space and increase the node heap space.

@itsmemario1 can u send me the upgrade log? did you use the apply.link? did u try upgrade before using the script note the script is a 2 part process for upgrade test w no changes then changes if u already upgraded manually, my scripts will abort as I won’t upgrade it again unless you force it.

Hello Team, I have a minor issue, I am using the module EXT-Screen, and it’s currently working; however, it doesn’t fully shut off. I can see the backlight of the monitor still on and most noticeable at night, the old MM 2.24.0 worked correctly, I’m not sure if I have to modify the /boot/config.txt? I’ve done something years ago, had a similar issue. Thanks for the help and all the work the Team put in.

@sdetweil Wooooooooooooow it works, thank you very much This worked after I typed this: sudo env PATH=$PATH:/usr/local/bin /usr/local/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/pi then that: pm2 start ~/MagicMirror/installers/pm2_MagicMirror.json pm2 save

@Roncham weird. try this pm2 stop all cd ~/MagicMirror export ELECTRON_DISABLE_GPU=1 npm start wait and see if the errors occurs if not add the export line to the script that starts mm in front of the npm start if you used my install script, that is ~/MagicMirror/installers/mm.sh

@mgustin As long as it works properly, there is no need to update it just to look “active” “Working or not” implies various cases, not a simple reason. Worked before, but not now, due to obsoleted/deprecated dependencies. Some might be fixable easily with a tiny effort. (e.g. install a few recent/alternative dependencies) Some might need the whole restructuring, and the module owner seems to have abandoned it; <= It can be said that “Not Working” In some cases, A user is just misusing the module. For example, incomplete installation, wrong configuration, mistypes, missing preparation, choosing the wrong module that is not fit for the purpose, etc. And there are many (yes, maybe too many) equivalent/alternative modules you can try. Cheer up.

I had magic mirror for, about a year and a half. There was one failure due to bad sd card, so it was upgraded to SSD. Started having random blank screen with cursor and I couldn’t find any problems. Made update to version 2.20. It worked for a few weeks and problem came back. I didn’t shut it off because I was runnung pihole on the same RPI3. A week a go, i replaced my airlive router with OPNsense running on thin client, and MagicMirror simply started working again. One thing i noticed is slightly better latency on the internet. And pihole is still running on that same Pi.

@CurlyQ12391 I think at the moment it’s better to rebuild backup your mm config see my backup script https://github.com/sdetweil/MagicMirror-backup-restore it will save the config.js, css, and a list of all the module urls and can use GitHub to store and version that all run from GitHub no required download

@Jonae ok do flash again, do not do any apt commands. run my install script

@sil3ntstorm i make sudo rm -r /usr/lib/node_modules then i used the upgrade-script bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” apply. the script above bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/node20_install.sh)” not work for me, error arch=: Zeile 1: “#!/bin/bash: Datei oder Verzeichnis nicht gefunden. after that i make npm install in the MagicMirror directory. Now all works fine for me

@sdetweil Oh, that was quick with the response, thanks! Well, that’s just the way it is!