@DimChik2903 all the weather operations are done in the browser, so u need to open the developers window,
ctrl-shift-i on the keyboard and
then select the console tab and
put weath in the filter field

for the v3 key, u probably have to use the apiVersion config property

@Lusbueb or, you can get my fork of MMM-Buttons which fixes the install problem

https://github.com/sdetweil/MMM-Buttons

@Lusbueb said in After update MMM-Buttons breaks, made things worse trying to fix it:

Please change your Installation -Instruktion in your GIT

no… mine is a fork of the master… you should know to substitute my URL for the one in the doc (if any)

if I were to change the link AND submit it to the author, AND they took it, then their doc would point to MY repo incorrectly…

this is how the fork process works…

SO, if you git clone my url and do the npm install, does it fail?

@mumblebaj buster is broken… do NOT upgrade buster machines…

lsb_release -a

to see what you have

@Klinge u need to be at node 18 at least…

run my upgrade script

https://github.com/sdetweil/MagicMirror_scripts

note that update is a 2 part process…

1. test, no changes,
2. apply

use force instead of apply , on the apply command

@kevmang

local version 2.25.0 already same as master 2.25.0

you need to use force on the upgrade command instead of apply

also, show the output of npm start

@CurlyQ12391 so, if you want to try this

cd /usr/local/lib/node_modules/npm
npm install graceful-fs@latest
cd ~
node -v

other than that its rebuild the sd card

@kevmang awesome,!!! thanks for the feedback

@wwats ok, do

d

to delete it

then node -v

@wwats try this from the n info

Remove the installed Node.js (does not affect the cached versions). This can be useful to revert to the system version of node (if in a different location)

sudo n prune
sudo n uninstall

@wwats and what does
node -v
show now?

@wwats can u do

ls -laF /usr/local/bin/node

@wwats ok, lets run this

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/node20_install.sh)"

@wwats

type the command

which node

and show the output

@sil3ntstorm my install/upgrade scripts

https://github.com/sdetweil/MagicMirror_scripts

that is the (bullseye) image I use as well…
pi0w gets the legacy (buster) image

@sil3ntstorm is it the 64 bit OS, or 32? 64 bit seems to be the biggest trouble spot…

I would use the 32 bit image

then run my install script as the first thing…

we had trouble with the preinstalled node 12 too…

@sil3ntstorm my scripts auto install 20.8.0

the problem is your system installed 20.5.1 instead…

we don’t know why yet, and don’t have a reliable fix.

pm2 can’t run cause node is broken,

so far the only fix is to rebuild your sd card …

use my backup script to save your MM config , modules, …
https://github.com/sdetweil/MagicMirror-backup-restore

reflash the sd card, use my install script and then restore script…
(note that you have to get the ~/MM_backup folder to safety… maybe on github …

the fixes suggested by folks on the node distro group do not work.

@sil3ntstorm thanks… the ‘problem’ is that we have a mangled node configuration…

we asked for node 20.8.0, but got 20.5.1 which is broken

@sil3ntstorm can u do this on a command prompt

n

and

nvm

do either respond?

@sil3ntstorm said in Magic mirror does not start automatically when booting:

@sdetweil No, I re-flashed the SD card and could now reinstall the Magic Mirror software. Should I access my Pi and run this?

bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh)”

Or do I have to do something else beforehand so that the Magic Mirror software is installed correctly?

yes, just run that. it has all the latest fixes and has been tested on bookwork, bullseye and buster