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

hoofta

@cruunnerr Right, sorry about that. I forgot you included it. When I did that during initial setup, the dots scrolls across without stopping. Motion or not, dots keep generating.

cruunnerr

then u probably connected it wrong and the gpio which is used in the script is set to high (1). u can check this…

type gpio readall to see the GPIO Breakout.

pi@MagicMirror_Test:~ $ gpio readall
 +-----+-----+---------+------+---+---Pi 2---+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |
 |   2 |   8 |   SDA.1 |   IN | 1 |  3 || 4  |   |      | 5v      |     |     |
 |   3 |   9 |   SCL.1 |   IN | 1 |  5 || 6  |   |      | 0v      |     |     |
 |   4 |   7 | GPIO. 7 |   IN | 1 |  7 || 8  | 1 | ALT0 | TxD     | 15  | 14  |
 |     |     |      0v |      |   |  9 || 10 | 1 | ALT0 | RxD     | 16  | 15  |
 |  17 |   0 | GPIO. 0 |  OUT | 1 | 11 || 12 | 0 | IN   | GPIO. 1 | 1   | 18  |
 |  27 |   2 | GPIO. 2 |  OUT | 1 | 13 || 14 |   |      | 0v      |     |     |
 |  22 |   3 | GPIO. 3 |   IN | 0 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |
 |     |     |    3.3v |      |   | 17 || 18 | 1 | IN   | GPIO. 5 | 5   | 24  |
 |  10 |  12 |    MOSI |   IN | 0 | 19 || 20 |   |      | 0v      |     |     |
 |   9 |  13 |    MISO |   IN | 0 | 21 || 22 | 0 | IN   | GPIO. 6 | 6   | 25  |
 |  11 |  14 |    SCLK |   IN | 0 | 23 || 24 | 1 | IN   | CE0     | 10  | 8   |
 |     |     |      0v |      |   | 25 || 26 | 1 | IN   | CE1     | 11  | 7   |
 |   0 |  30 |   SDA.0 |   IN | 1 | 27 || 28 | 1 | IN   | SCL.0   | 31  | 1   |
 |   5 |  21 | GPIO.21 |   IN | 1 | 29 || 30 |   |      | 0v      |     |     |
 |   6 |  22 | GPIO.22 |   IN | 1 | 31 || 32 | 0 | IN   | GPIO.26 | 26  | 12  |
 |  13 |  23 | GPIO.23 |   IN | 0 | 33 || 34 |   |      | 0v      |     |     |
 |  19 |  24 | GPIO.24 |   IN | 0 | 35 || 36 | 0 | IN   | GPIO.27 | 27  | 16  |
 |  26 |  25 | GPIO.25 |   IN | 0 | 37 || 38 | 0 | IN   | GPIO.28 | 28  | 20  |
 |     |     |      0v |      |   | 39 || 40 | 0 | IN   | GPIO.29 | 29  | 21  |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+---Pi 2---+---+------+---------+-----+-----+

In the script the BCM pin 22 is used for the PIR. This is GPIO 3 and physically it is pin 15.

Please check if your pir is connected correctly.

Edit:

Oh, and take a look at your PIR. u can set the delay time from 0.3seconds up to 5 minutes. Maybe its set very high.
For using the soloutions of this tutorial the PIR adjust time should be set very low, as u can set the time within the script :)
https://www.mpja.com/download/31227sc.pdf

hoofta

@cruunnerr As many have said your patience and helpfulness is much appreciated. I did have the ground and the power swapped. I turned off the Pi swapped them and turned it back on and re-ran the test. Got the same thing. I grabbed another PIR and ensured I plugged it in properly. Hooray! (I guess I fried the other one by swapping PWR and GND) Your python test works and it activates MM for the proper amount of seconds after the time delay. Woohoo! Now I need to get it to go to a black screen instead of turning off since after the PIR Sensor stops sensing motion I then see the “NO SIGNAL” screensaver bounce around my TV. One step closer!

cruunnerr

:)

thank you very much ^^

I am very glad u found out what went wrong. :)
So now u should be able to use the “screen_on/off” files instead of the monitor_onoff

Just try out :)

hoofta

@cruunnerr I just redid step 2.2 with the alteration of screen_on/off.sh (instead of monitor) and the HDMI is still being disabled and giving me the “no signal” screensaver.

How do I know that the chmod +x steps are actually making the script executable?

cruunnerr

try the shell scripts without the python script.

sh monitor_off.sh should show a black screen (not turning HDMI off)
sh monitor_on.sh should disable the black screen.

if this is working for u, then your pir.py script seems not being correct.

the chmod +x step is necessary for the python script execute the shell scripts.

But first try the commands above. If this doesn’t work, then i have to think about and search for a solution.
But i tried it just a few seconds ago, and it works fine here

hoofta

@cruunnerr for me $ sh monitor_off.sh returns the following
sh: 0: Can’t open monitor_off.sh
I then inputted $ nano monitor_off.sh and it’s empty when I just inputted the commands from your instructions. ¯_(ツ)_/¯

cruunnerr

again one step closer :D

put in the content and save with “ctrl+x” and “y”

try everything agin and report if u got trouble again :)

edit:

oh sorry. Aren’t we using “screen_on/off”?? :D

so try

sh screen_off.sh should show a black screen (not turning HDMI off)
sh screen_on.sh should disable the black screen.

hoofta

I GOT IT! I stepped back a few steps with the module removed from the config.js file and it wouldn’t blank anymore so it made me think I had something wrong with the pir.py file.

I looked into Paviro’s files in the PIR-Sensor folder and found in the node_helper.js file a reference to tvservice -o/p. I found where my xscreensaver was located /usr/bin/ and I had the node_helper file execute the xscreensaver instead of the tvservice.

Bingo! No more “No Signal” bouncing around when the PIR-Sensor module kicks in! Many thanks to Cruunnerr for the help. Definitely could not have figured this out without you!

Mykle1

@hoofta

Good work, mate! I like it. :-)

PaulB

@cruunnerr,

Thank you so much! What a great ‘How-to’- Guide :)

You and your post helped a lot. :)

hnperkins

hey all, im having a issue with my pir module. i have run the pir.py script and its constantly scrolling the … until i move and then it stops for a brief second, and when i load the module in my config file the screen just stays black. is this some kind of interference or do i just have it hooked up backwards or something?

randomnoise

@hnperkins if the script is working the opposite way round it could be that you have a pir board which uses inverted signals. The board I had originally worked this way. So when no motion is detected it gives you a 1 & when you move it gives you a 0. Instead of running the script try typing gpio read 0 (substitute the pin number you used here… remember gpio “wiring pi” numbering will be different to the number you input in your file. See https://pinout.xyz/). It only shows the current state so you need to keep putting this in as you move in front of the sensor to test it. Hit up + enter to “retype” the command quickly in the console.

If this is the case then unfortunately the script will not work in your case… it’s written for true or 1 to be when movement is detected.

If you use paviro’s module there is a configuration option to invert the input pin.

As to the screen being black when starting mm. It’s probably an error in your configuration. Search the forum to find info on how to check the config as that has been well covered.

hnperkins

@randomnoise ok so when i do the gpio read command it always shows a 1, when i use a pin its not connected to it shows a 0, is this what you were talking about?

randomnoise

@hnperkins yes, if it’s always showing a 1 then your sensor is ‘inverted’ to the standard way most pir boards work. Note it should go to 0 when the pir detects movement (you might need to continually wave your hand in front of the pir at the exact moment you hit enter after typing the gpio read to see the 0. If you never see a 0 then you may have a faulty pir).

Although I initially did get my ‘inverted’ sensor working using the invert configuration option in paviros module, it eventually stopped working correctly (my mirror would register a false detection every 3 mins or so causing my screen to stay always on). Not sure why it broke… seemed to happen after I upgraded to a newer version of mm, but issue didn’t go away after I tried rolling back. Final thing I did to stop false triggering was to install a ferrite choke on my input wire & to move where my pi sat at the back of my monitor (it was quite close to the monitors power converter initially).

Ultimately the way I got it working was to buy a different pir board (the kind with the 2 potentiometers for sensitivity & time adjustment) which also happened to be 0 for no movement & 1 for movement). I then used the pir.py script instead of the module to trigger screen on / off. I was fairly sure it wasn’t a single faulty pir unit (mine came in a pack of 3) but nothing I did got it working so in the end spending an extra fiver on a different type of pir seemed worth it to me.

fabbr

I had the script running and all I got was “…” turns out I had the POWER and GROUND swapped because I was following the drawing on the initial post. I suggest looking at the your PIR board to make sure you are connecting the wires on the correct order.

Overall fantastic write up. Thanks for sharing

hnperkins

@fabbr i just got it working today. hadn’t had time to mess with it much. i was able to invert it in the config for the plugin and its been working great

fabbr

I used the method 2.2 Using PIR-Script and it work fine however, after a long period of time (that the screen is off and I am not doing anything on the raspberry) when I move in front of the PIR I can see the ON signal is sent to my monitor (the monitor LED change) but all I get is a blank screen.

I did some testing and notice that when I connect with VNC to the raspberry the screen immediately comes back on so it makes me wonder if there’s some kind of screensaver or something of that nature that is on.

Does anyone knows anything about this or had this problem before?

Mykle1

@fabbr

Have you disabled the screensaver? The easiest, most common way of doing that is to install xscreensaver and disable the screensaver that way

fabbr

@Mykle1 Thank you that was the problem. Xscreensaver was easy use. Thanks

Another problem I had was: when I changed the orientation of my monitor when it was coming back on all I saw was a black screen… so I did more research and found that that I could replace the tvservice for:

vcgencmd display_power 0 turns off the screen

vcgencmd display_power 1 turns on the screen

That worked better with my monitor for some reason.