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

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.

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!

@sdetweil

> magicmirror@2.29.0 start
> DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js

[2024-10-08 19:41:58.640] [LOG]   Starting MagicMirror: v2.29.0
[2024-10-08 19:41:58.693] [LOG]   Loading config ...
[2024-10-08 19:41:58.698] [LOG]   config template file not exists, no envsubst
[2024-10-08 19:41:59.497] [INFO]  Checking config file /home/MagicMirror/MagicMirror/config/config.js ...
[2024-10-08 19:41:59.584] [ERROR] Your configuration file contains syntax errors :(
Line 94 column 5: Parsing error: Unexpected token weatherEndpoint

That parsing error is for the new line added in for weatherEndpoint

@sdetweil I have it exactly as you have it above.

can you share a config for this module as an example?
I can’t even check if this is working with pm2 not launching the MM

@sdetweil so my config was identical to above, so I’ve added you new line “weatherEndpoint…”

I’m using Putty to access the MM and used pm2 to stop the MM.
which it did.
However now, pm2 via Putty is no longer having any effect on the MM.
MM isn’t launching.

run pm2 logs mm and get a parsing error over adding the new line
unexpected token weatherEndpoint your configuration file contains syntax errors.

all I’ve added is weatherEndpoint: “/onecall”, to a final line under the apiKey line above.

any thoughts?

edit to add, pm2 status and logs show that pm2 exists still it’s just not launching. can pm2 be “updated” or should I follow the process for a first install?
for completeness I don’t want it to launch MM on boot I just want to be able to start and stop the MM using pm2.

@sdetweil So I’ve upgraded to my account on OpenWeather (and added payment details.
Generated a new APIkey and added this to the config of the weather module but it is still stuck on loading.

So I’ve run your update, and the weather still doesn’t load.

Seems odd that the API issue would only arise following the update.
Is this likely?

@butchkemper Is this the default weather module or an additional one?

@karsten13 how do I update this specifically.

Everything was working fine prior to the latest MM update.

I’ve just updated the MM to the latest version, everything seems to have gone fine except the default weather module, which is now stuck in a “loading” phase.

I found an older post saying the newer version of this module needed an APIkey over an APIid but the MM setup is newer than this post so already has this change.

Has anyone had this same issue since this latest update, or have any ideas how to sort this?

Seems I can’t even update the MM without causing an issue.

for completeness I got this at the bottom of the update using
git pull && npm run install-mm,

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: magicmirror@2.29.
npm ERR! notsup Not compatible with your version of node/npm: magicmirror@2.29.
npm ERR! notsup Required: {“node”:“>=20.9.0 <21 || 22”}
npm ERR! notsup Actual: {“npm”:“10.1.0”,“node”:“v20.8.0”}

npm ERR! A complete log of this run can be found in: /home/MagicMirror/.npm/_los/2024-10-06T07_38_42_762Z-debug-0.log

would these errors cause the issue I’m seeing?
cheers.

@sdetweil That was exactly how PIR sensor lite worked on the same pi 3.
screen would turn off after time interval - i had it set to 5 minutes - pi would detect a hand swipe past the PIR sensor, pi would wake the screen up and the 5 minute cycle would start again.

do we (you) think the mode 4 for HDMI in this module will function the same?

@sdetweil
So if I stick with MMM-Pir am I right in thinking if u set the mode to mode 4 in the script it would turn the screen off via the HDMI?

Just read that it is set to mode 1 by default which uses vgencmd but my screen and pi are connected via HDMI.

Would be handy to get this one turning the screen off entirely (if possible) and use the PIR to turn it back on, as the rest of the MM is working nicely.