if you installed one of the calendar patches or used the develop branch
and intend to upgrade MANUALLY, YOU have to get back to the master branch ahead of time
check the current branch
cd ~/MagicMirror
git branch
output example
* _fix_clipping
develop
master
and if the highlighted (*) name is NOT master then
rm package-lock.json
rm package.json
git checkout master
use git branch
to verify master is selected before continuing
then do the commands as listed in the documentation
if you are using my upgrade script, it will handle all this for you.
this release requires a new version of nodejs, which is NOT available on the armv6l processor systems, raspberry pi 0w
the install and upgrade scripts will abort
manual install last step will fail nodejs test, but new code will be downloaded
to reverse the code download do
git checkout -b oldbranch tags/v2.30
# npm install not required if on this prior branch
hardware upgrade required!!!
@sdetweil said in Version 2.30.0 weather module, stuck loading, worked fine before upgrade:
@Assassins seems it doesn’t work anymore… using my old 2.5 key I get code failure with openweathermap
Strange, works on my sd card with MM2.29.0 and also works on MMM-DynamicWeather and on MMM-WeatherOrNot with MM2.33.0.
Don’t know why openweathermap doesn’t work with MM2.33.0.
Besides that, it may have something to do with the code in MM2.33.0 that has been rewritten.
MagicMirror install on pi0w broken with legacy OS… chromium startup yields
illegal instruction
uninstall/reinstall doesn’t fix… I think it installed the armv7l version incorrectly.
we have seen and verified that electron 8.5 and above are not working on raspian Jessie
but Jessie is pretty old…
u will see an error on npm start (after a version upgrade)
/home/pi/MagicMirror__RL1/node_modules/electron/dist/electron:
/lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /home/pi/MagicMirror__RL1/node_modules/electron/dist/electron)
strongly recommended to rebuild a new sd card with raspian Buster
fixes are published in the next release via the develop branch
to get there
if you did manual install
cd ~/MagicMirror
git checkout develop
git pull
npm install
restart MagicMirror as normal
if you used my install script
cd ~/MagicMirror
git fetch origin develop:develop
git checkout develop
npm install
if u are already ON the develop branch, and want to update to the latest,
git pull
npm install
restart MagicMirror as normal
@BiaGen the latest 2 releases run config check as part of startup, and fail if there is an error like that
I always recommend using manual start whenever changing config, for this very purpose
Stop pm2 mgmt if managing the app
Then
cd ~/MagicMirror
npm start
If any problems they are right there
Once good, ctrl-q MagicMirror
And then use pm2 to launch
@BKeyport yes, if I discover you are not on the master branch, I move you to master, then update from there.
For exactly this situation. Trying a specific fix or all of develop branch.
@dangerousden AWESOME!!! thanks for the great post…
one thing from above,
when posting config content or log info, please use the code block wrapper
past the text, blank line above and below,
select the text you just pasted,
hit the </> button to use the wrapper…
@tommyk sorry. Danger if I know. Maybe just examples of how it could be.
127.0.0.1 is the address for localhost
192.168. Is a typical default network address setup
I leave it empty, cause I don’t want to force my devices to fixed addresses (dont want the mgmt job)
