MagicMirror² v2.15.0 is available don't work.

Stoffbeuteluwe

Hallo, i have installed the updatescript and than I have installed the valid url …the mirror starts normal and when i stop the Mirror I get this.

nal SIGINT
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.15.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the magicmirror@2.15.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/patrickhahn/.npm/_logs/2021-04-06T20_05_51_094Z-debug.log
patrickhahn@Mac-mini MagicMirror %

hope somebody can help me …thanks

sdetweil

@stoffbeuteluwe that’s ok when u stop

unfriendlydevice

@sdetweil what is the full command to run this? I’ve done some searching on the forum but haven’t found anything.

sdetweil

@unfriendlydevice run ‘this’???

unfriendlydevice

@sdetweil to run the electron-rebuild as you advised (sorry I think I replied to the main thread instead of your earlier reply)

sdetweil

@unfriendlydevice

cd ~/MagicMirror
npm install electron-rebuild

now change to your module folder where u need the electron rebuild
then

~/MagicMirror/node_modules/.bin/electron-rebuild

(note the dot . in front of bin)

unfriendlydevice

@sdetweil That’s great thanks

ChrizZz

@chrizzz said in MagicMirror² v2.15.0 is available don't work.:

I do have some strange things after the update.

At first, the new weather module is just “loading” without displaying content. Even after 30+ minutes. Is there something wrong with the config? I saw that there is a minor issue with the data request which will cause it to load for ~10min (or to reduce the update interval).
{
			module: "weather",
			position: "top_right",
			classes: "always",
			config: {
				// See 'Configuration options' for more information.
				type: "current",
				locationID: "YYY",
				appid: "XXX"
			}
		},

I checked this again with switching back to the old module and the old module works. The forcasting takes 10min (as expected) but the module itself works. I thought this might be something with the connection to the API. Any ideas?