MagicMirror² v2.11.0 is available! For more information about this release, check out this topic.
READ THE CHANGELOG BEFORE UPDATING!

MMM-Loxone


  • Module Developer

    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.



  • @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.


  • Module Developer

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


  • Module Developer

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



  • 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 
    0|MagicMir | #1 0x000000841db2 
    0|MagicMir | #2 0x0000012700d2 
    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]
    
    
    

  • Module Developer

    @bobbythemoh Ok, thanks. No unhandled rejections.



  • @idoodler , did “vcgencmd” solve the issue?


  • Module Developer

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



  • @idoodler , i dont think so. Let me explain the behaviour of the Module:

    Light in the Room Switched ON, Booting the Mirror gives me the Mirror as it should be
    Switching the Light off, switches the Monitor off.
    Switchint the Light on again activates the Background light of the Monitor but does not give content
    Entering the command “xset -display :0 -dpms” while the light is switched ON brings back the content

    in my opinion this is not a miniserver issue since I can observe an reaction (Backlight of the monitor comes alive), this is an issue with the “tvservice”


  • Module Developer

    @bobbythemoh You misunderstoodme. I think the issue is in my code with the communication layer crashing resulting in not receiving any state changes, hence the mirror doesn’t know to enable the display again.

    I just found an issue and testing it over the night.


Log in to reply