MM shuts down after an hour

Lazershrimp

@sdetweil Yes, I use PM2 to start MM. If you by base OS mean RPi OS, then yes.

sdetweil

@Lazershrimp can u minimize mm ctrl-m and use the preferences (top left menu)
to see if blank screen was turned back on?

or from a terminal or ssh window, run my screensaveroff script from

https://github.com/sdetweil/MagicMirror_scripts

next to the last thing listed on the page, copy/paste the one line

jasondreher

I had a similar issue, the screen would go black after an hour or so (never the login screen just always went black). On of my modules was not compatible with the upgrade. Once I removed that module all was well.

sdetweil

@jasondreher can u tell me about that module? I like to keep track of troubles users experience

jasondreher

@sdetweil
https://github.com/scottcl88/MMM-DynamicWeather

Once I removed this module I had no issues.

sdetweil

@jasondreher that module suffers from this

https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later?page=1

Lazershrimp

@sdetweil said in MM shuts down after an hour:

or from a terminal or ssh window, run my screensaveroff script from
https://github.com/sdetweil/MagicMirror_scripts
next to the last thing listed on the page, copy/paste the one line

Thanks, I am now trying the screensaveroff script. Will have to wait for an hour to see if it works.

@sdetweil said in MM shuts down after an hour:

@jasondreher that module suffers from this
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later?page=1

I have checked my modules for the package.json files, all good

sdetweil

@Lazershrimp you are not checking for package.json, except to apply the fix

the fix is to

npm install xxxx

where xxx is the missing library as found in the log error messages

Lazershrimp

@sdetweil said in MM shuts down after an hour:

@Lazershrimp you are not checking for package.json, except to apply the fix
the fix is to
npm install xxxx
where xxx is the missing library as found in the log error messages

This I don’t understand. You write in “fix for black screen in 2.16 and later” that some MM modules used libraries, which are now removed.

By navigating to the module folder and running “ls package.json”, I am checking whether the module contains this file or not, yes? If it does not, the fix is to install it by typing “npm init -y”

But since my modules all seem to contain the package.json, I’m guessing that this is not what causes my problem.

Or am I wrong?

sdetweil

@Lazershrimp you are wrong

if you have a black screen

you look at the messages put out from npm start

if you see

cannot find module xxxx

then this mm module has the problem

the fix is to install the missing library (called module in the message,) IN the mm module folder

NOW as part of the fix process we want the file put in the right place NOT in the MagicMirror folder.

to DO THAT , the mm module MUST supply a package.json file

this is where the ls command comes in to the fix process

it it already exists, cool, do the npm install for the missing library

if it does NOT exist, create it it with the npm init -y command
AND then do the npm install for the missing library.

but, the 1st step is to identify the missing library from the message output.
if that is NOT the problem, then the rest of the instructions don’t matter

there are.multiple libraries that could cause the problem, that’s why I have to read the messages to determine which ones are needed