Read the statement by Michael Teeuw here.
MMM-Loxone
-
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]
-
@bobbythemoh Ok, thanks. No unhandled rejections.
-
@idoodler , did “vcgencmd” solve the issue?
-
@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 contentin 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”
-
@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.
-
@bobbythemoh I just pushed some changes, please update. Don’t forget to execute
npm install
after updatingMMM-Loxone
. -
David, you are my hero, it works!!!
Energy Consumption of RPI + 24" Monitor Powered ON = 56W; 3.4W if no one is present in the room. AWESOME!
Thank you for the efforts!
May I also ask you for the feature request with displaying variables from the Miniserver? Id like to see things like the PV production or an analog value like the level in a tank.Thank you so much!
-
@bobbythemoh please create a separate Issue in Github for the power consumption thing.
-
@bobbythemoh Please check the latest version of
MMM-Loxone
. It’s not possible to display custom states:)