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

[Maros]

Yes i’ve active mmm-pir module.
I’ll try your solution and let you know
Thank you ;)

[Maros]

i’ve removed line from rc.local and mirror is still working as should (turn on when there is movement and turn off after 30s as set up in MMM-PIR module)

[MadScientist]

Was the MMM-PIR sensor module active while you tried the script of 2.2? You will have to disable the module. Then you create and load the scripts and create the cronjob. If you don’t disable the MMM-PIR module then it will keep waking up the screen even if you disabled the pir.py script.

Please excuse me if that’s what you did and I just got it wrong.

[cruunnerr]

Hey sorry, i thought u disabled the MMM-PIR for sure.

U cannot use both (Module and the script) at the same time.

Thats because i said u should disable the autostart in the rc.local to see if the MMM-PIR is active.

So please disable the module and just use the script. Then the pkill command will work as u want :)

[Maros]

everything is working after disabling module :)

just one remark there is needed to add also to crontab to turn off monitor at f.e. 21:02 because if there will be movement in last seconds before pir.py will be killed monitor will stay on :)

[teitlebot]

@Module-Developers im trying to do something a bit different maybe you can help.
I’d like to use PIR but I also want that on one particular day of the week PIR shouldn’t work and it should stay on no matter what.
Is that possible?

[cruunnerr]

Read the last few posts ;)

For example u want to use the pir from Sunday 22pm over the whole week until next Sunday 6am.
So on every Sunday from 6am to 22pm the monitor should stay on.

So you just need two cronjobs. On Sunday, 6am u need to kill the pir.py and on Sunday, 22pm you need to start it again :)

Try it like this:

1. nano killpir.sh

2. Write this into file and save with CTRL+X and Yes

#!/bin/bash
sudo pkill $(ps aux | grep python pir.py | awk '{ print $2 }')
vcgencmd display_power 1

3. chmod +x killpir.sh

4. sudo nano /etc/crontab

5. Write this into file and save with CTRL+X and Yes:

0 22 * * 7 /usr/bin/sh /home/pi/killpir.sh
0 6 * * 7 /usr/bin/python /home/pi/pir.py

So for example your crontab looks like this:

# /etc/crontab: system-wide crontab
# Unlike any other crontab you don't have to run the `crontab'
# command to install the new version when you edit this file
# and files in /etc/cron.d. These files also have username fields,
# that none of the other crontabs do.

SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# m h dom mon dow user  command
17 *    * * *   root    cd / && run-parts --report /etc/cron.hourly
25 6    * * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6    * * 7   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6    1 * *   root    test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
0 22    * * 7   root    /usr/bin/sh /home/pi/killpir.sh
0 6     * * 7   root    /usr/bin/python /home/pi/pir.py
#

[Mykle1]

@cruunnerr

You’re the king of cronjobs!

[komodoteler]

@cruunnerr

I tried your script but unfortunately it doesn’t seems to work yet. Like @blebbens , my MM is on the floor and activated a little bit too easy.

Any other suggestion?

Regards,

[cruunnerr]

Well, for my solution it is totally necessary to NOT use the PIR-Module. You must use just my external script solution!
Tests i made working fine… :)

Anyhow… You could try to use clear nail polish.

I used it to cover certain regions and it works :)
Just paint several layers of the polish over the area u want to cover.

Or play with the sensitivity