@MMRIZE When I cd MagicMirror I get into that directory
but the /modules/MMM-CalendarExt3 says it isn’t recognised.

I’ve had the notification on the top bar saying there’s an update to my MMM-calendarExt3 module, that the current installation is 2 commits behind the main branch.

What is the correct way of dealing with this?

It may seem a daft question however…
The last time I had an update the issues off the back of it - when the update ran into issues and failed part way - and the entire MM stopped working and some kind people on here rescued me from the point of binning the whole setup.
Cheers.

sdetweil edit: change topic name

Thought I’d drop in here rather than start a new thread, with this current setup pm2 stop mm in terminal no longer stops the mirror from relaunching after using shift+Q.

Any ideas how I stop the MM to allow me to shut the pi down safely for a brief time?

Sam, scratch my last message, I was just about to turn everything off as it’s getting pretty late here.
used ctrl c to stop the MM so I could shutdown the pi and attack it another day.
pm2 restarted the MM and hey presto the mirror seems by and large back to normal.

I’m away with work for the next 3 days but will have a proper butchers (look) when I’m back home.

Thank you so much for both your patience and help.
I had genuine fears I’d have to start the entire build (modules bit) again and I was lucky I got it up and running like I did in the first place.

thank you!

I had 2 versions of the PIR sensor module as one didn’t work, I don’t know if I ended up using the lite version or the other one.

some of the modules are saying they have old lockfiles (this is for the ISS module) or in the case of dad jokes it has an ERR! code eresolve.

Any ideas why the calendar extension hasn’t popped back up? It was calendar ext2 I was using I think.

So I run the restore and some things have loaded up fine, so the default calendar and new headlines. everything else hasn’t.
I had an extended calendar module, and a PIR sensor to shut the screen off after 5 minutes.

The were some npm err and npm warn issues.

The PIR sensor was the most useful feature I had but I genuinely don’t think I could replicate how I got it working in the first place. It was a case of loads of misses then an eventual hit (plenty of luck).

DO I need to restart the pi for some of these changes to come into effect, or do I need to start messing with modules again, or do I need to do a further update to some modules? Is this the parm you mentioned?

yea that’s the little widget that wasn’t moving all that much for a good while, low and behold not 2 minutes after posting it starting carrying on. I tried to come and delete the pending post but you got in there pretty quick with the reply.

once this has run do I need to run your update code or will this be the most current version of MM?

made the name change and started the install.
How long should the install take? After installing the helper tools it’s got about half way across the screen on updating packages and hasn’t moved for about 10 minutes, prior to that it was pretty quick. I tried to use the arrow keys on my keyboard to move up the terminal window a little and have ^[[A[ and ^[[C[ in the list, is this an issue?

once a new name is picked can it later be changed back to magicmirror just to keep everything standard?

Also, when you say,
mv magicmirror newname, I’m guessing the newname bit is actually what I want to call it, or do I put the new name after?
I’ve got a terrible feeling I’ll have to start the whole thing again which I definitely won’t look forward to.

sorry to sound extremely daft, but what should I be renaming it? Is there a preferred name or one which makes most sense?

may sound like a daft question but how do I rename the magicmirror folder? I’ve run your back up (hopefully).

@sdetweil I’m away with work until Friday but obviously want to try and get to the bottom of this.
I’ll likely end up moving the mirror to somewhere way closer to the WiFi router.
Will this stay open until the end of the week?

Out of curiosity when launching via pm2 should it (in the little box that pops up in terminal) mention fork?

@sdetweil after running the npm install now getting a different ENOTEMPTY for nodes_modules/basic-auth.
Same issue of directory not empty

@sdetweil this is on a 3b+.
when running npm install I’m now back to an error for ENOTEMPTY for node_modules/ansi-escapes.
it says directory not empty.
I think it wants it renamed no_modules/.ansi-escapes-TiTd7xs1

@sdetweil when I run npm start from the MM folder I get:

magicmirror@2.23.0 start
DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js

sh: 1: ./node_modules/.bin/electron: not found

@sdetweil Managed to run it a second time and everything seems happy, however, the pm2 start mm.sh still isn’t launching the MM itself.
Is there any other way to launch the mirror, or a way to check why it’s suddenly lost function (it was always happy launching and stopping the MM) ?

@sdetweil Sorry to double reply, I ran the last 2 again and they worked ok, right up until the very end of the npm install when I got an ERR_SOCKET_TIMEOUT.
I’m assuming this is a wifi strength issue as the position of this mirror means it struggles at times.

@sdetweil yes ran all three lines you posted.

@sdetweil Thanks for your reply, your helping of others has helped me out endlessly with this project.
I run the npm install then get an error ENOTEMPTY around /home/pi/MagicMirror/node_modules/ansi-escapes.
saying the directory isn’t empty.

Hey guys, frequent searcher of this forum but this issue is the first which has me completely stuck and not able to solve with lots of Googling.

MY MM prompted an update last week, which I did following the update guidance on the main builder site. Part way through the update failed, I had to go away for the bank holiday here in the UK and I’m now picking it back up.

As per the title I launch the magicmirror in terminal using pm2 start mm.sh (it’s always worked) it says it’s done but then the MM never actually launches.

when I check the pm2 logs I get an error around a directory no being empty and the node_module engine.io needing renaming.
any thoughts on sorting this? I don’t know if this is just the first hurdle or the only reason the MM is no longer launching.
I don’t have a programming background so please be gentle.
Cheers.