Clicking on the screen to wake (unhide) the modules also doesn’t work
It’s seams to be an MM² engine crash or an module crash
try to open dev tools when happen (in remote with CTRL+MAJ+I)
inspect red lines (error) and what module can do that
Ho bugs! That is quite a good idea! I can make this api call myself (i gues haha) but maybe can you help me with the (other modules to read) or pinpoint me to some sample code ( i am not that good of a coder :S . But most of the time i think to diffivult about stuff.) Thanks in advance!
Kind regards! P.s. i really enjoy your work! It is nice!
(I also connected with an other module Home Assistant to the screen. So i can see some parameter like temperature on the screen!!)
Hi, I don’t know how Alexa works, so I’m not able to help you.
Notes:
EXTs are plug-in and not Module.
Generaly is reserved to MMM-GoogleAssistant and not others.
They can’t works without MMM-GoogleAssistant
This forum website name is MMM-GoogleAssistant and not Alexa 😉
I would like to note, that I have to set:
“xset dpms 00 00 00”
So that the screensaver does not interfere with EXT-screen.
once I set the timeout for EXT-Screen back to 120000, the dpms was set to “60 60 60” and when the screen would go to sleep it would require keyboard/mouse input to wake up.
xset dpms 00 00 00 solved that issue.