Just a small remark: /del/null is a typo.
When off works, then on will work when you change to /dev/null.
Unless it is right on your system and the typo is in your thread.

ended
(motion stopped)
started
(motion started)

same as my doc says for the motion config

@plainbroke autoreconfig?

u don’t have to build motion, they have binaries (on every platform I’ve tried so far)

my script (launched by something outside mm)
creates an empty file in a known folder for each motion event

detected
ended

my module node_helper watches for those files to be created, and then sends notification to my module side to signal sleep or wake depending on the config.

the default folder is ‘motion’ inside the MMM-SleepWake folder

the script locates the running mm instance, and uses it’s path to locate the module folder and this it’s motion folder

the script assumes the path includes the username mm is running under and that username is used to set file permissions, so the module can remove them after processing the detection

So if I send a empty file ended to the motion folder in MMM-SleepWake that triggers the timer in config.js to blank screen?
and then in the morning send empty file detected to the same motion folder in MMM-SleepWake it should turn the modules back on.
Have I got this correct in my head or am I still wondering at sea?

just works

I fiddled w delay, and some light flash settings but thing else…

sudo apt install motion

was all I needed

I cannot turn off any of mine, so I hide modules instead, but get a glow… (my nightlight)

If I understand you correctly the dimmer is dimming the modules, but the monitor is still giving off light. A cron job set to turn on/off the monitor at specific times is what you’re looking for.

u don’t have to build motion, they have binaries (on every platform I’ve tried so far)

my script (launched by something outside mm)
creates an empty file in a known folder for each motion event

detected
ended

my module node_helper watches for those files to be created, and then sends notification to my module side to signal sleep or wake depending on the config.

the default folder is ‘motion’ inside the MMM-SleepWake folder

the script locates the running mm instance, and uses it’s path to locate the module folder and this it’s motion folder

the script assumes the path includes the username mm is running under and that username is used to set file permissions, so the module can remove them after processing the detection

Thought if there is a way to run your script manually I would then just incorperate that into a cron job and be done with it.
The module I am running autodimmer still glows at night and you can see the modules faintly in the background…

it signals motion start and end.
the library provides tons of config options and supports just about every camera.

I provide the interface script that is called on motion start/end and signals my sleep/wake module to turn off screen or hide modules.

you could use the script I provide in the cron job to signal wake up or go to sleep on a timed schedule

Good eye. And yes! This was the issue. Thank you

Just a small remark: /del/null is a typo.
When off works, then on will work when you change to /dev/null.
Unless it is right on your system and the typo is in your thread.

using my Sleep wake module
https://github.com/sdetweil/MMM-SleepWake

hdmi-off.sh file contains :
vcgencmd display_power 0

hdmi-on.sh file contains:
vcgencmd display_power 1

Don’t forget to
sudo chmod +x hdmi-off.sh
sudo chmod +x hdmi-on.sh
If you go this route.

Now I use MMM-AutoDimmer
my setup in config.js it works great

{
        disabled: false,
        module: "MMM-AutoDimmer",
        position: "fullscreen_above",
        header: "",
        // Don't change anything above this line
        config: {
        maxDim: 1,
        brightTime: 700,
        dimTime: 2130
              }
},

take of the redirects >
so u can see the errors in the cron log