MM doesnt work after update to version 2.26

[davismorehead]

i did

git pull && npm run install-mm

Some of my replies take a long time to be approved. Is there a secret to get them approved faster.

[sdetweil]

@davismorehead if you have already installed, then you don’t run install again…
so, are you running headless? (no screen?)

so you would not do npm start, you would do npm run server

[sdetweil]

@davismorehead said in MM doesnt work after update to version 2.26:

Some of my replies take a long time to be approved. Is there a secret to get them approved faster.

I review every post for every user with reputation below 2.
this keeps out all the spam…

i DO do other things…

[davismorehead]

sorry, didn’t know how it worked. Didn’t realize you did it.

[davismorehead]

not running headless. Just don’t have a keyboard attached to pi. so SSH intomachine.

[sdetweil]

@davismorehead I use ssh exclusively, so that’s not it. and you are running in graphical mode, w the desktop…right?

I’ve had that check in there for 3 years now… and I just checked on all my pi systems. it never fails to find the file…

[davismorehead]

i checked i don’t have that file. looking on internet it says During the booting up of the system, systemd activates default. target , which is generally a symbolic link in the /etc/systemd/system/ directory to either graphical. target or multi-user. target . It is equivalent to the default runlevel, which the system administrator used to set in the /etc/inittab file.

I don’t have graphical.target or multi-user.target but I have graphical.target.wants

[sdetweil]

@davismorehead weird

[davismorehead]

so should i try and get your script to work or do something else to fix this

[sdetweil]

@davismorehead you could try upgrade, with force instead of apply.

[davismorehead]

how do I do that?

also if I run the command
pi@raspberrypi:~ $ systemctl get-default
graphical.target

I get graphical even though I don’t have the file

[davismorehead]

I did

npm update.

i did pm2 start mm

and it works. Thank you very much

[sdetweil]

@davismorehead what npm update?

[davismorehead]

I will look at your script later.

So in the future I should run npm update not npm install?

[davismorehead]

cd MagicMirror/
pi@raspberrypi:~/MagicMirror $ npm update

added 495 packages, and changed 6 packages in 3m

195 packages are looking for funding
run npm fund for details

That worked

[sdetweil]

@davismorehead i don’t understand

when we release a new version, we have dependency changes additions, removals

so to handle all that you do
npm run install-mm
install-mm is a script tag in the package.json

it just turns off as much of the noise as we can…

my script does the same thing…

I don’t know what npm update does. we don’t use it

[davismorehead]

@sdetweil said in MM doesnt work after update to version 2.26:

ad you could try upgrade, with force instead of apply.

so based on this post i Tried npm update. Not sure what you meant me to do. So sounds like we solved it but don’t know why.

[davismorehead]

@sdetweil said in MM doesnt work after update to version 2.26:

ad you could try upgrade, with force instead of apply.

so based on this post i Tried npm update. Not sure what you meant me to do. So sounds like we solved it but don’t know why.

[sdetweil]

@davismorehead what I meant was to use my upgrade script

its a two step process…

test
do

on the ‘do’
its the same command as test, but with the parm ‘apply’ on the end

I check if you have already upgraded, and won’t let you do it again, accidentally

SO, as you HAVE already downloaded the new code, I would just end
but if you change apply to force
then upgrade will happen again …

my objective is to NOT screw up your wonderful mirror system .

[davismorehead]

oh. I have to figure that out since I cannot get it to run because of the default.target file not existing on my pi.

Again thanks for your help.