Read the statement by Michael Teeuw here.
MMM-Loxone
-
@idoodler
Here is what i have observed:
XScreensaver is installed, Screensaver is disabled.
Rebooting the magic mirror with presence ON and light in the room on gives the magic mirror as it should be.
Leaving the magic mirror in this state (and also the light in the room) does not lead to screensaver, the picture stays as it is.
Switching off the light in the room also blacks out the monitor, power consumption goes down to 5W also without “#hdmi_blanking_1” but here is the issue:
Switching on the light in the room after blacked out monitor brings the monitor backlight and the power consumption back but not the UI.With VNC i can see the UI, moving the mouse does not bring the UI back on the direct connected monitor.
Any idea?
-
@bobbythemoh I guess you have some sort of other “power saving” feature activated I am not familiar with.
MMM-Loxone
directly toggles the HDMI output on or off. It isn’t displaying a black view on top of the screen.Please verify your
/boot/config.txt
!
In one ofyour posts you wrotehdmi_blanking_1
but it should behdmi_blanking=1
. -
OK you were right, i changed it but there is no change in the behaviour. The Monitor remains without video signal just with backlight if i switch the light in the room on. Do you have any hint for me what i can check?
-
@bobbythemoh Did you reboot after correcting the option?
-
@bobbythemoh You may also try to uninstall
xscreensaver
-
There is indeed some very weird issue going on with the HDMI and screen saver/blanking as I reported here. It started after I updated my kernel (from 4.9.80) & what else came with it. Out of curiosity, what is your OS version?
-
-
@bobbythemoh said in MMM-Loxone:
@idoodler yes i did reboot. and i just uninstalled xscreensaver (after that i did a reboot) but no change in the behaviour.
@E3V3A I used “uname -a”:
Linux MagicMirror 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/LinuxBobby do you have a solution for this? I’m having the exact same problem since updating my pi to the latest version of rasbian
-
no, solution yet unforunately.
-
I just experienced a similar issue, but It appears not to be caused by
MMM-Loxone
. I am Invastigating it…