@sdetweil
I thought you would find that interesting, I never thought much about it until the previous post came about. Like I said it doesn’t bother us or cause any issues. They really are at least with in 45 seconds of each other. If I reboot the pi it will sync up for most of the day… Maybe that is his answer to restart his pi just before bed, assuming it is that important…

@sdetweil
Mine is off a full minute right now. Funny thing is it will usually catch up in a few minutes. I notice it most often around xx:45 to xx:49 in the afternoon, evening .
Not a big deal to me what is 30 to 45 seconds matter anyways.
Now as I am writing this it caught back up. I would not notice at all if I dd not have another clock running directly below it that gets it’s time from the network too.

@sdetweil
I actually know what it means I just couldn’t figure out how it was happening in a module. I rearranged the display and it now is working. Some of these modules are so touchy…

???Getting this Bad Gateway Error code 502???
What does this mean on my MagicMirror ???
SEE PICTURE FOR MORE INFORMATION…

@cgillinger
Sounds good. I will watch this form post for the update.

@FalcoonnnnPUNCH
@emlowe
@sdetweil
I have had that problem before and it was a bad card. One other time it was a bad USB drive… Might try a different sdcard.

@cgillinger
I was going to ask if you had found a work around for pages and MMM-Birthdays. I also tried it with pages and just one other module. MMM-Birthdays takes over even MMM-MPlayer and it is a bully too.
Always wanting to be on top… You idea is awesome, but the deployment needs a little work…
I am trying a few different setups now that I have a “test setup”.
I really want to make MPLayer and Birthdays to play nice on one of my displays. So far no bueno…

Does anyone use this module? It shows up but I think I need more information to get it to work.
Here is what I have put in my config.js

        {
                module: "MMM-edgerouter-throughput",
                position: "middle_center",
                header: "Unifi",
                config: {
                        gateway: "https://192.168.1.1",
                        user: "Plainbroke",
                        pwd: "HIDDEN INFORMATION",
                        title: "Unifi",
                        interface: "USG Pro3"
                }
        },

And this is the output from my USG router

@chrisfr1976
@sdetweil
Thank you both for the help.
/usr/local/bin/pm2 restart mm
worked so I set it up to stop now and if (fingers crossed) works.
I am golden.
Wonder why I never had to use the full path before?
Maybe my pm2 path was /home/pi/pm2 before.
Doesn’t really matter as long as it works, I am a happy camper.
It works.
Thank you so much… I will mark this solved.
Well I would if I could… strange.

By the way " which pm2 " shows the path that I needed to use in crontab -e

@chrisfr1976 said in pm2 doesnt work with crontab:

find / -iname pm2

/usr/local/bin/pm2
/usr/local/lib/node_modules/pm2
/usr/local/lib/node_modules/pm2/bin/pm2
/usr/local/lib/node_modules/pm2/lib/templates/logrotate.d/pm2
/usr/local/lib/node_modules/pm2/pm2


/home/pi/MagicMirror/node_modules/.bin/pm2
/home/pi/MagicMirror/node_modules/pm2
/home/pi/MagicMirror/node_modules/pm2/bin/pm2
/home/pi/MagicMirror/node_modules/pm2/lib/templates/logrotate.d/pm2
/home/pi/MagicMirror/node_modules/pm2/pm2

Which is the true one and one to use?

@rkorell said in MMM-Pir disappeard on github:

MMM-Pir

Don’t the authors usually leave their github live, so that others can work on them if they want to keep using them… ?

@sdetweil
From that post about an hour. and it was supposed to trigger this morning around 6:30 am.
It did not and it did not leave anything in the logs since last night when I pm2 stop all then pm2 flush. around 8:30 pm .
So that means cron job did nothing with pm2 over night
I have been experimenting so there are a couple different job lines.
I really expected something in the log. But this is all I get.

pi@MM:~ $ pm2 logs --lines=100
[TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 100 lines:
/home/pi/.pm2/logs/mm-out.log last 100 lines:
/home/pi/.pm2/logs/mm-error.log last 100 lines:

My Crontab on 2 different MM setups. I get the same nothing on both.
Both are running Bookworm and MM 2.3.1

05 20 * * * pi /usr/local/bin/pm2 start mm
15 07 * * * pi pm2 start mm
30 21 * * * pi pm2 stop mm
05 20 * * * root /usr/local/bin/pm2 start mm
15 07 * * * root pm2 start mm
30 21 * * * root pm2 stop mm

@sdetweil
Got ya, I miss understood before.
Running and waiting for results now…

Finally got results useing the proper path.
@sdetweil
You can mark this resolved.

@sdetweil
pi is my user. I know not very original or safe but it is on a closed network.
that is why I tried the pi user in the crontab.
and it shows up when I do crontab -l.
So I think it is setup under pi correctly.
Do I need to do it as root sudo crontab -e and use pi or root as the user?

@cgillinger
As Sam said b it stays on the screen always. Just the message though.
Sorry it annoys you so.
Take your time I am not in a hurry, never am.
Just thought I would let you know. I am sure others are watching this to add to their pages too…

@sdetweil
My old crontab does not work in debian 12 aka bookworm
Is there something i need to add to it to get it to work again?
Really liked how it worked and the fact that I was getting a fresh restart of mm every morning…

15 07 * * * pm2 start mm
30 21 * * * pm2 stop all

Tried this too.

15 07 * * * pi  pm2 start mm
30 21 * * * pi  pm2 stop all

@cgillinger
Works on the fireworks, but not on the MESSAGE part, It stays on the screen.
The fireworks came and went with the page it was supposed to.

@sdetweil
I am using your mmm-pages. I just haven’t gotten that involved in it yet…
I know sooner or later I will definitely take advantage of the different amounts of viewable content.

@captsi
Can you reconfigure the new router to the same settings you had in the old one.
or update the pi to the new wifi?