Read the statement by Michael Teeuw here.
Should I update?
-
Hi MM builders.
A long time ago (december 2017) I built my MM and it had been running without major issues since.
It must be far behind with updates (master branch and modules).
Should I update (and if so, how?)
Of just leave it running as it does now?
Greetings,
Peter -
@peter lots of changes since then
I would use my upgrade script
see
https://github.com/sdetweil/MagicMirror_scriptstwo pass
1st time is test and tell you about any potential issues i u need to fix (fix and run again til u are comfortable)
then u can do with apply to actually upgrade?u can also do my backup script
see https://github.com/sdetweil/MagicMirror-backup-restore
(have to clone this one)
saves config.js and github links to all the installed modules… -
@sdetweil thanks!
I noticed your script, but was wondering if it would work because I am so much behind.
I think I still run MM 1.x
And I love my MM.
Peter -
@peter make a backup of the MM folder before starting
the script will work, or I will fix it…
-
@sdetweil great!
Peter -
Hi Sam,
I have a similar problem.
My memory card is defective and I had to revert to an older backup.
Unfortunately, I have been a little lax with the backup, as I always have to get the mirror off the wall a bit awkwardly to back up the SD card.I am with the mirror still on Jessie.
When I stop the MagicMirror with “pm2 stop mm” and also stop node with killall node, I get a message from your scipt (test mode) that node and npm need to be updated.
How do I get them to the latest version?I am rather beginner in Linux - so have understanding for simple queries.
Can you help me?BR
Jens -
@mymirror jessie is very old
4 releases back now. almost nothing will support running there nowI would also suggest some of the mechanisms to backup over the local network
-
@sdetweil
Hi Sam,yes i know :-( … very old.
in the meantime I got the system on “Stretch” and wanted to take the next step to “Buster”.
But I get the following error (on german):
PGP error: http://ftp.de.debian.org/debian buster InRelease: The following signatures could not be verified because their public key is not available …How can I adjust/correct this?
Thanks a lot -
@mymirror i do not know… buster is also not current
-
@sdetweil finally I tried the update: MM will not start anymore.
I am on stretch by the way.
Peter -
@peter show me the messages… fromn npm start
stretch is WAY downlevel…
need to get to buster(legacy) or bullseye…
the internet keeps changing things every week… stetch is 4 years old now
-
Is it possible to update without having to start all over?
Peter -
@peter maybe… as i said, stretch is really old…
I do not know if you can upgrade OS in place from stretch
pretty sure u need to upgrade node and npm too
node -v
npm -vwhat pi is this ?
uname -a
-
@sdetweil I think it is a Pi2b.
In 2017 I built this MM and it has been running well since.
So, that is my question: update of not.
It took me very long to build, and I do not want to start all over again.
Peter -
@peter do not update
-
@sdetweil 😁
Saves a lot of work!
Maybe I start a fresh install some day.
Thanks for your help.
Peter
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login