These are the two lines I updated in motion.conf

# Command to be executed when an event starts. (default: none)
# An event starts at first motion detected after a period of no motion defined by event_gap

on_event_start value /home/pi/MagicMirror/modules/MMM-SleepWake/external_motion started

# Command to be executed when an event ends after a period of no motion
# (default: none). The period of no motion is defined by option event_gap.

on_event_end value /home/pi/MagicMirror/modules/MMM-SleepWake/external_motion ended

I noticed something else. Last night, before I went to bed, I turned motion off (I was just running it from the command line, not as a service). This morning my display was in power saving mode again (yellow light) and I couldn’t get it to wake up. I had to manually run this command from the command line to get the screen to turn on again :

/opt/vc/bin/tvservice -p && sudo chvt 6 && sudo chvt 7

It’s strange that your module had put my screen to sleep even though there was no motion even to trigger it.

@sdetweil I’m hoping you can help me out with this. I have installed the Motion package and confirm that it works - I can view the livestream etc and it’s recording mkv files to the motion folder that I’ve defined when motion is detected.

I see these entries in motion.log :

[1:ml1] [NTC] [EVT] [Jan 09 01:19:36] event_newfile: File of type 8 saved to: /home/pi/Pictures/motion/01-20210109011936.mkv
[1:ml1] [NTC] [ALL] [Jan 09 01:19:36] motion_detected: Motion detected - starting event 1
[1:ml1] [NTC] [ALL] [Jan 09 01:21:26] mlp_actions: End of event 1
[1:ml1] [NTC] [EVT] [Jan 09 01:21:28] event_newfile: File of type 8 saved to: /home/pi/Pictures/motion/02-20210109012128.mkv
[1:ml1] [NTC] [ALL] [Jan 09 01:21:28] motion_detected: Motion detected - starting event 2
[1:ml1] [NTC] [ALL] [Jan 09 01:24:01] mlp_actions: End of event 2
[1:ml1] [NTC] [EVT] [Jan 09 01:24:18] event_newfile: File of type 8 saved to: /home/pi/Pictures/motion/03-20210109012418.mkv
[1:ml1] [NTC] [ALL] [Jan 09 01:24:18] motion_detected: Motion detected - starting event 3
[1:ml1] [NTC] [ALL] [Jan 09 01:33:05] mlp_actions: End of event 3

Your module did put my display to sleep but it didn’t wake it up. I tested these commands manually and they work to turn the HDMI on and off :

/opt/vc/bin/tvservice -p && sudo chvt 6 && sudo chvt 7
/opt/vc/bin/tvservice -o

I edited the motion.conf file to call your module when motion event starts / ends.

I notice this however in the motion log after I added the event calls to your module :

[30500488:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file /home/pi/.motion/motion.conf
[30500488:motion] [NTC] [ALL] motion_startup: Motion 4.1.1 Started
[30500488:motion] [NTC] [ALL] motion_startup: Logging to file (/var/log/motion/motion.log)
 &: 1:  &: value: not found
 &: 1:  &: value: not found -> this keeps repeating until I stop motion

I commented out the motion event calls and these messages stop. So they seem to be related to these two configuration entries :

on_event_start /home/pi/MagicMirror/modules/MMM-SleepWake/external_motion started
on_event_start /home/pi/MagicMirror/modules/MMM-SleepWake/external_motion ended

I noticed you mention that there should be two files in the motion directory under MMM-SleepWake but in my case, I do not see any files in that directory.

In my config.js, I just have this :

        {
            module: 'MMM-SleepWake',
            config:{
                delay: 15,               
                mode: 'PI'
            }
        },

Sorry for the long message, I hope you can suggest what I may have done incorrectly.

Thanks!

@Saabman That’s great! Once I got my MQTT feed up, this module worked very well to display the data from my PWS.

@Saabman Thanks again for all the work you have put into updating this module. Have you checked out MMM-Currentweather-MQTT ? I got it to work with my PWS. It takes an interesting approach of blending in data from PWS where available and supplements it with data from OpenWeather. It does require your PWS to publish its data via MQTT.

I normally either hit “Control R” if I’m in a VNC session or “pm2 restart mm” if I’m logged in via ssh.

@sdetweil Thanks ! That did the trick!

@sdetweil @Saabman

I’m pretty I’m running @Saabman 's fork now but I’m still running into a blank screen when MM loads. Here’s what I can see in the console :

Load script: modules/MMM-WunderGround//MMM-WunderGround.js
module.js:513 Module registered: MMM-WunderGround
loader.js:148 Bootstrapping module: MMM-WunderGround
loader.js:236 File already loaded: moment.js
loader.js:153 Scripts loaded for: MMM-WunderGround
loader.js:236 File already loaded: weather-icons.css
loader.js:195 Load stylesheet: vendor/node_modules/weathericons/css/weather-icons-wind.css
loader.js:195 Load stylesheet: modules/MMM-WunderGround/MMM-WunderGround.css
loader.js:155 Styles loaded for: MMM-WunderGround
translator.js:102 MMM-WunderGround - Load translation fallback: translations/en.json
localhost/:2 Uncaught SyntaxError: Unexpected token / in JSON at position 4
    at JSON.parse (<anonymous>)
    at XMLHttpRequest.xhr.onreadystatechange (translator.js:22)


@sdetweil Thanks !

I realized what the issue is but I don’t know why it’s happening. I was trying to git clone @Saabman 's fork but it keeps cloning the original MMM-WunderGround for some reason. I’ll manually download @Saabman 's version and try again.

@Saabman Thank you for doing this! When I tried out your version of the module, my MM loads with a blank screen. Actually I ran into this same problem when I tried to modify the modules myself a couple of days ago using the new API documentation that you found.

When I manually try using the API via the URL, it seems to return data (I’ve *** some data for privacy) ie

{"observations":[{"stationID":"***","obsTimeUtc":"2021-01-03T18:43:34Z","obsTimeLocal":"2021-01-03 10:43:34","neighborhood":"***","softwareType":null,"country":"US","solarRadiation":252.0,"lon":-121.763,"realtimeFrequency":null,"epoch":1609699414,"lat":37.32,"uv":0.7,"winddir":22,"humidity":85,"qcStatus":1,"metric":{"temp":12,"heatIndex":12,"dewpt":9,"windChill":12,"windSpeed":0,"windGust":3,"pressure":1024.38,"precipRate":0.00,"precipTotal":0.00,"elev":150}}]}

I cannot see anything in the logs that is helpful :(

[2021-01-03 10:39:25.741] [LOG]    Module helper loaded: MMM-WunderGround
[2021-01-03 10:39:27.778] [LOG]    Connecting socket for: MMM-WunderGround
[2021-01-03 10:39:27.779] [LOG]    MMM-WunderGround helper started ...
[2021-01-03 10:39:27.829] [LOG]    Sockets connected & modules started ...

I have both MMM-KeyBindings and MMM-TelegramBot installed and working well. Is there a way to have telegram simulate key presses for MMM-KeyBindings to respond to?

My scenario is this : I have MMM-Carousel set up to cycle through two pages but sometimes I want to manually advance the page. The only way MMM-KeyBindings works is when I’m connected to my Rpi using VNC. So that’s not very practical. If I can trigger a virtual keypress via MMM-TelegramBot, that would be awesome.

Has anyone tried this?