Read the statement by Michael Teeuw here.
Losing display output after 5 minutes
-
@sdetweil I’m able to VNC to the pi, and when I move the mouse the TV will turn back on. It will then stay on for 5 minutes before TV lose HDMI connection. I have also keep the VNC connection open and watch the TV lose signal and the app continue to work.
I have missed with the PI config file to increase the HDMI signal but same outcome.
Also, I did setup CEC, 6 months ago, to control when the TV turns on and off. I was thinking there was an issues with the pi, so I created a con job to turn the TV, then restart the PI. This setting worked for about a week. Now if I do not restart the PI it comes up with no HDMI signal.
I wondering if its an issues with the TV itself?
-
@danjvd if you stop MagicMirror, does the screen turn off?
-
@sdetweil I have not tried that. I will let you know later today of the outcome.
Thanks Sam!
-
@danjvd It sounds as if your screen saver wasn’t disabled correctly?
https://github.com/MichMich/MagicMirror/wiki/Configuring-the-Raspberry-Pi
-
@zoltan if u run my install script it will turn off screensavers if u say yes.
also a separate script if u change your mind
we are still waiting to see if it’s mm related or not
-
-
@danjvd ok so this means one of the modules you are using is turning off the display
can you do
grep module: ~/MagicMirror/config/config.jsto show us a list of the modules used
-
@sdetweil said in Losing display output after 5 minutes:
grep module: ~/MagicMirror/config/config.js
Here are the modules that I have been using for the past 6 months before the issues started. I have not added/removed any modules after this setup, only updates.
module: "alert", module: 'MMM-BackgroundSlideshow', module: "updatenotification", module: "clock", module: 'MMM-CalendarExt2', module: "MMM-OpenWeatherMapForecast", -
@danjvd weird.
so next I would disable one module at a time.
(not the defaults)add
disabled:true,after the module: line
-
Before I was able to start disabling modules, MM would not start this morning. There are the logs that I got from pm2:
0 info it worked if it ends with ok 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] 2 info using npm@6.14.12 3 info using node@v10.24.1 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle magicmirror@2.17.1~prestart: magicmirror@2.17.1 6 info lifecycle magicmirror@2.17.1~start: magicmirror@2.17.1 7 verbose lifecycle magicmirror@2.17.1~start: unsafe-perm in lifecycle true 8 verbose lifecycle magicmirror@2.17.1~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/bin:/bin 9 verbose lifecycle magicmirror@2.17.1~start: CWD: /home/pi/MagicMirror 10 silly lifecycle magicmirror@2.17.1~start: Args: [ '-c', 10 silly lifecycle 'DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js' ] 11 info lifecycle magicmirror@2.17.1~start: Failed to exec start script 12 verbose stack Error: magicmirror@2.17.1 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js` 12 verbose stack spawn ENOENT 12 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18) 12 verbose stack at ChildProcess.emit (events.js:198:13) 12 verbose stack at maybeClose (internal/child_process.js:982:16) 12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 13 verbose pkgid magicmirror@2.17.1 14 verbose cwd /home/pi/MagicMirror 15 verbose Linux 5.10.63-v7l+ 16 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" 17 verbose node v10.24.1 18 verbose npm v6.14.12 19 error code ELIFECYCLE 20 error syscall spawn 21 error file sh 22 error errno ENOENT 23 error magicmirror@2.17.1 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js` 23 error spawn ENOENT 24 error Failed at the magicmirror@2.17.1 start script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ]
