Read the statement by Michael Teeuw here.
{HowTo} turn on/off your monitor (Time based, PIR/Button, App)
- 
 @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. 
- 
 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 readallto 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
- 
 @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! 
- 
 :) 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_onoffJust try out :) 
- 
 @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? 
- 
 try the shell scripts without the python script. sh monitor_off.shshould show a black screen (not turning HDMI off)
 sh monitor_on.shshould 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
- 
 @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. ¯_(ツ)_/¯
- 
 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.shshould show a black screen (not turning HDMI off)
 sh screen_on.shshould disable the black screen.
- 
 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! 
- 
 Good work, mate! I like it. :-) 
 
 
 
 
 


