MMM-Loxone

bobbythemoh

@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?

idoodler

@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 wrote hdmi_blanking_1 but it should be hdmi_blanking=1.

bobbythemoh

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?

idoodler

@bobbythemoh Did you reboot after correcting the option?

idoodler

@bobbythemoh You may also try to uninstall xscreensaver

E3V3A

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

@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/Linux

SuperSchenk

@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/Linux

Bobby do you have a solution for this? I’m having the exact same problem since updating my pi to the latest version of rasbian

bobbythemoh

no, solution yet unforunately.

idoodler

I just experienced a similar issue, but It appears not to be caused by MMM-Loxone. I am Invastigating it…

bobbythemoh

@idoodler
I found this passage in your code:

    _togglePresence: function _togglePresence(isPresent) {
        if (isPresent) {
            // Check if hdmi output is already on
            exec("/opt/vc/bin/tvservice -s").stdout.on('data', function(data) {
                if (data.indexOf("0x120002") !== -1)
                    exec("/opt/vc/bin/tvservice --preferred && chvt 6 && chvt 7", null);
            });
        } else {
            exec("/opt/vc/bin/tvservice -o", null);
        }
    }

So you are using “tvserice -o” which seems not to work for me.
would this be an alternative? Link

Executing the commands vom @E3V3A here Link brings the Monitor Signal back, but only 1 time.

Any idea?

bobbythemoh

Hi, using this command brings back the Monitor signal:

xset -display :0 -dpms

idoodler

I just implemented vcgencmd it looks like it is a bit quicker. I will check it out the next few days and will push it if everything works.

E3V3A

@idoodler said in MMM-Loxone:

I just implemented vcgencmd it looks like it is a bit quicker. I will check it out the next few days and will push it if everything works.

Yeah, but that only work with Rapsberry Piss , so if you want it to work on other devices, you need to use xset, and if you want to use xset on the Pi, you now also need to tell it that the blank screen should be black, with xsetroot -display :0 -solid black.

idoodler

@e3v3a I think xset just blanks the screen without powering off the HDMI signal?

idoodler

@bobbythemoh Can you please post your pm2 log. You can optain it by executing pm2 log MagicMirror if you are using pm2.

I just detected some unhandled rejections which may cause the black screen.

bobbythemoh

pi@MagicMirror:~ $ pm2 log MagicMirror
[TAILING] Tailing last 15 lines for [MagicMirror] process (change the value with --lines option)
/home/pi/.pm2/logs/MagicMirror-error-0.log last 15 lines:
0|MagicMir | [865:0515/052002.614227:FATAL:bus.cc(1197)] D-Bus connection was disconnected. Aborting.
0|MagicMir | #0 0x0000007fd980 <unknown>
0|MagicMir | #1 0x000000841db2 <unknown>
0|MagicMir | #2 0x0000012700d2 <unknown>
0|MagicMir |
0|MagicMir | npm ERR! code ELIFECYCLE
0|MagicMir | npm ERR! errno 1
0|MagicMir | npm ERR! magicmirror@2.3.1 start: `sh run-start.sh`
0|MagicMir | npm ERR! Exit status 1
0|MagicMir | npm ERR!
0|MagicMir | npm ERR! Failed at the magicmirror@2.3.1 start script.
0|MagicMir | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
0|MagicMir |
0|MagicMir | npm ERR! A complete log of this run can be found in:
0|MagicMir | npm ERR!     /home/pi/.npm/_logs/2018-05-15T05_31_52_606Z-debug.log

/home/pi/.pm2/logs/MagicMirror-out-0.log last 15 lines:
0|MagicMir | MMM-Loxone Search LightControls and LightV2Controls in room
0|MagicMir | MMM-Loxone Found LightControl (Lichtsteuerung) in room OG Bad
0|MagicMir | MMM-Loxone NotificationUuid: 0ea3ebd1-008d-029d-ffff390cde3b9b45
0|MagicMir | MMM-Loxone Enabling statusupdates
0|MagicMir | MMM-Loxone Successfully executed 'dev/sps/enablebinstatusupdate' with code 200 and value 1
0|MagicMir | MMM-Loxone Got lightMood change [1]
0|MagicMir | MMM-Loxone Got room temperature: 21.8
0|MagicMir | MMM-Loxone Got lightMood change [777]
0|MagicMir | MMM-Loxone Got lightMood change [778]
0|MagicMir | MMM-Loxone Got lightMood change [1]
0|MagicMir | MMM-Loxone Got lightMood change [777]
0|MagicMir | MMM-Loxone Got lightMood change [1]
0|MagicMir | MMM-Loxone Got lightMood change [777]
0|MagicMir | MMM-Loxone Got lightMood change [778]
0|MagicMir | MMM-Loxone Got lightMood change [1]

idoodler

@bobbythemoh Ok, thanks. No unhandled rejections.

bobbythemoh

@idoodler , did “vcgencmd” solve the issue?

idoodler

@bobbythemoh No. I think there is an issue within the communication module for the Miniserver. If the module crashes when the screen is turned off the screen will never be turned on again and vice versa.