Love this module ! Instead of grouping by divisions, is there a way group by conference instead for NBA?

Love this module ! Instead of grouping by divisions, is there a way group by conference instead for NBA?

Very post ! Can you please share with MM modules you have used ?

@ftap Have you tried adding “appendLocationNameToHeader: false” to the config block ?

       {
            module: "weather",
            position: "top_left",
            config: {
                type: 'forecast',
                weatherProvider: "openweathermap",
                weatherEndpoint: "/onecall",
                apiKey: "***", // your OpenWeatherMap API key
                windUnits: "imperial",
                updateInterval: 180000,
                timeFormat: 12,
                showPeriod: true,
                showHumidity: true,
                degreeLabel: true,
                colored: true,
                fade: false,
                roundTemp: true,
                showPrecipitationAmount: true,
                appendLocationNameToHeader: false,
                lat: ***, // your latitude
                lon: ***, // your longitude
            }
            }, 

@sdetweil said in Help with MMM-SleepWake:

@chanster ok, my module doc gives u the new lines for motion.conf

Yes, nothing wrong with your docs at all.

@sdetweil It was in the sample config file for Motion. It’s a rookie mistake that I should have replaced “value” and not merely append to this line :

# 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

# 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

@sdetweil Thank you !! I’m so stupid. Removing “value” did the trick ! Thank you for this module. Works perfectly.

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.