Update from 2.15 to 2.16

sdetweil

@andyyy can u send me the ~/MagiMirror/installers/upgrade.log

| doah, not install , upgrade log… yeesh

my email is the same user ID at gmail

sdetweil

I can recreate the problem in my script

I bet u tried the develop branch. and switched back to master, and these files aren’t in master on 2.15, but the final versions are different than the develop versions.

andyyy

@sdetweil

Solved for now :)

I did:

sudo git fetch --all
sudo git reset --hard origin/master
sudo git pull origin master

My system is still very fragile. When do npm install after that, the screen turn black after reboot.

sdetweil

@andyyy said in Update from 2.15 to 2.16:

the screen turn black after reboot.

again, this si because libraries in 2.15 were removed in 2.16 and some modules didn’t document their requirements properly…

find the MM startup messages (npm start or pm2 logs)
and look for ‘module not found’

I REALLY hate reset --hard…

sdetweil

@andyyy I uploaded fixes to the upgrade script to handle this…

bdream

Hi!
I did the upgrade to my system to 2.16

Uploading upgrade.log with 600 lines is not possible… because of file format.

After reboot I have only the mouse in the middle of the screen but MM is not working.

Also I’m not able to get a connection wit ma Web-Browser.

Raspberry itself is accessible via SSH.

Any idea?

sdetweil

@bdream yes look at the mm startup messages
we call this the black screen

bdream

@sdetweil does it mean I have to do in MagicMirror folder?

sudo git fetch --all
sudo git reset --hard origin/master
sudo git pull origin master

sdetweil

@bdream no. u are probably missing some modules that mm removed

read the startup messages

npm start
or
if using pm2
pm2 logs --lines=100

Fozi

@bdream I strongly guess that one of the 3rd party modules is not compatible vith MM2.16.0. I had the same issues with MMM-MyCalendar, which caused a black screen after starting MM. My approach is to disable all 3rd party modules by adding the line

disabled: true;

for each module and enable it one after the other by setting it to

disabled: false;

Taht might discover quicker, which module is the culprit instead of poking in logs (that is my personal approach!).

When you found the module, that causes issues, contact the developer on github, or look for an alternative fork which seems to be maintained.

Regarding the above mentioned MMM-MyCalendar module, I reverted to the default calendar module, which works just fine and delivers the same features.