{HowTo} turn on/off your monitor (Time based, PIR/Button, App)

OdomLinx

disable the HDMI port with

vcgencmd display_power 0

and enable with

vcgencmd display_power 1

Most monitors then go into standby. Some also show ‘NO Signal’.

E3V3A

@OdomLinx copy paste error?

OdomLinx

@E3V3A Yes copy paste error, I adjusted it

E3V3A

Most modern monitors also have a PowerSave function that completely turn off the monitor when there is no HDMI signal, after a set amount of time. So I guess experimentation will be needed as to what really happen after you have turned it off using either:

vcgencmd display_power 0
sudo tvservice -o
DISPLAY=:0 xset dpms force off (Notice, it’s not necessary to export!)
xset -display :0 dpms force off

The first 2 turn off HDMI and most likely put your monitor into PowerSave mode, eventually.
The last 2 only blanks the screen (visible when dark), and does not disable HDMI signals.

ninjabreadman

@E3V3A Some monitors, but almost all television displays turn off after delay (and then cannot be woken in software).

That, and some folks have complained that they can’t hear a podcast or Alexa because their integrated speakers turn off when the monitor is in powersaving.

You’re right, it takes some experimentation to tailor to a given use case/situation depending on requirements.

MadScientist

I would like to use the MMM-PIR-sensor module to trigger the relay to power off the LCD. However, whenever I set
relayPIN: 27, in the config.js, the motion detector doesn’t do anything anymore. Anyone know what else I have to change in the config? It’s working just fine without the relay.

Config working without relay (switches off HDMI):

                {
                module: 'MMM-PIR-Sensor',
                config: {
                        sensorPIN: 22, 
                        relayPIN: false,
                        powerSaving: true,
                        }
                },

Not working with relay:

                {
                module: 'MMM-PIR-Sensor',
                config: {
                        sensorPIN: 22,
                        relayPIN: 27,
                        relayOnState: 1,
                        powerSaving: true,
                        }
                },

The problem is I am using a V59 LCD controller board which doesn’t power on again once the HDMI is re-activated.

cruunnerr

Can u turn on GPIO27 with gpio -g write 27 1 and off with gpio -g write 27 0 ?
Have u tried just to connect a LED on GPIO27 ?
What relay do u use and how exactly is it connected? ?

MadScientist

Hmm, I get

Unable to determine hardware version. I see: Hardware   : BCM2835
,
 - expecting BCM2708 or BCM2709. Please report this to projects@drogon.net

when I run gpio -g write 27 1 .

cruunnerr

@MadScientist said in {HowTo} turn on/off your monitor (Time based, PIR/Button, App):

Unable to determine hardware version. I see: Hardware : BCM2835

Huh… a quick google search tells, that this could be several causes. Some wrote to update or downgrade the kernel., some wrote to update wiring pi and so on.
So its not a problem of the module at all. I’m sorry but for the first u should try to google.

Maybe start with this: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=182191

However you should start a new thread if you cannot get to target :(

randomnoise

@MadScientist said in {HowTo} turn on/off your monitor (Time based, PIR/Button, App):

Hmm, I get

Unable to determine hardware version. I see: Hardware   : BCM2835
,
 - expecting BCM2708 or BCM2709. Please report this to projects@drogon.net

when I run gpio -g write 27 1 .

I had the same issue. I just followed the instructions on the wiring pi site to install. Don’t have my notes but there was a different version depending if you use wiringpi or wiring-pi. I’ll see if I can find the right one.

randomnoise

So I think as wiring-pi is the npm specific version the reason it didn’t work was because they haven’t compiled it to work with the pi3 chip.

Try http://wiringpi.com/download-and-install/

MadScientist

Thanks so far. I did npm uninstall wiring-pi and installed wiringpi via git. Now I don’t get the error anymore but the relay still does nothing. It’s getting late and won’t have the time today anymore to look into it. Let me know if you have other ideas and I will continue tomorrow.

Thanks so far.

randomnoise

I think I kept the npm wiring-pi on there as well… There’s probably some other stuff in there that makes it work in mm.

cruunnerr

U could also quick try the script from this tutorial (at point 5). It will be done in 2 minutes ^^
Maybe u missed the connection?

MadScientist

Two minutes if you know what you’re doing…
The problem is I don’t have a button. I did create the relay.py script and run it. It triggers the relay exactly once and then stays like this. I can’t even stop the script anymore once it’s running…

Man, I really thought setting up the relay would be as easy as adding one line to the config. Wish I had tried to set it up earlier.

Still need help with this. :-(

cruunnerr

Ah I see…
I will write u this evening. We will get it working ;)

MadScientist

Thank you so much!

cruunnerr

@MadScientist
Alright…

Because your relay turns on i think you did everything right. Probably there is a problem with your Module installation… but thats just a guess. Maybe u didn’t give the module the rights to turn on gpio’s?
sudo usermod -a -G gpio pi (the „pi“ at the end stands for your username)

If u did that and it doesn’t work at all you can try to do it with an external script. Follow these steps:

cd
nano monitor_on.sh

put in this:

gpio -g mode 27 out
sleep 0.2
gpio -g write 27 1

save with “ctrl+x” and “y”

nano monitor_off.sh

put in this:

gpio -g mode 27 out
sleep 0.2
gpio -g write 27 0

save with “ctrl+x” and “y”

chmod +x monitor_on.sh (to make it executable)
chmod +x monitor_off.sh

nano pir.py

put in this:

#!/usr/bin/env python

import sys
import time
import RPi.GPIO as io
import subprocess

io.setmode(io.BCM)
SHUTOFF_DELAY = 120 # in seconds, how long the monitor will be on until next button press or PIR detection
PIR_PIN = 22       # 15 on the board (this needn't to be a PIR. Can be a button also)
LED_PIN = 16      # optional

def main():
    io.setup(PIR_PIN, io.IN)
    io.setup(LED_PIN, io.OUT)
    turned_off = False
    last_motion_time = time.time()

    while True:
        if io.input(PIR_PIN):
            last_motion_time = time.time()
            io.output(LED_PIN, io.LOW)
            print ".",
            sys.stdout.flush()
            if turned_off:
                turned_off = False
                turn_on()
        else:
            if not turned_off and time.time() > (last_motion_time + 
                                                 SHUTOFF_DELAY):
                turned_off = True
                turn_off()
            if not turned_off and time.time() > (last_motion_time + 1):
                io.output(LED_PIN, io.HIGH)
        time.sleep(.1)

def turn_on():
	subprocess.call("sh /home/pi/monitor_on.sh", shell=True)

def turn_off():
	subprocess.call("sh /home/pi/monitor_off.sh", shell=True)

if __name__ == '__main__':
    try:
        main()
    except KeyboardInterrupt:
        io.cleanup()

save with “ctrl+x” and “y”

chmod +x pir.py

You can check if your button works by simply typing python pir.py. Every time u move through the PIR or press the button it will show you several …
End the test with “ctrl+c”

The Shutoff delay in the script defines how long the relay will be turned on after detection through the pir.

If that works u can add the script to the rc.local to start it automatically when booting up.

MadScientist

Ok, I did all that and I do get the “…” when I run the pir.py, but the relay doesn’t get triggered. Tried the monitor_oX.sh with and without sudo. Maybe I should just start all over new. Everything seems to be a bit messed up. I reverted back to motion detector only and also that isn’t working anymore in MM.

Edit: Started a new thread here.

cruunnerr

@MadScientist
sorry, did a mistake. I edited my post above. just edit the *.sh files.