• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.

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

Scheduled Pinned Locked Moved Tutorials
171 Posts 39 Posters 259.5k Views 54 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    cruunnerr
    last edited by cruunnerr Aug 24, 2018, 10:30 AM Aug 24, 2018, 10:23 AM

    cron will start the pir.py in background. The scenario will be like:

    Boot up magic mirror = starts pir.py via rc.local
    at 21pm = stops pir.py via cron
    at 7am = starts pir.py via cron

    from this on the circle is closed and cron will repeat this every day (in background)
    well… i think so… maybe i am wrong :/

    When u reboot the mirror between 21pm and 7am the pir.py will be active for sure until the next 21pm will be reached … ;)

    edit:
    it would also be possible to implement a while-loop in the pir.py script to check if it is between 21pm and 7am.
    But i never worked with that yet -.-

    maybe u can get what u want here or here or here

    1 Reply Last reply Reply Quote 0
    • M Offline
      Maros
      last edited by Maros Aug 24, 2018, 7:48 PM Aug 24, 2018, 7:26 PM

      ok i’ve checked and it’s not working fully.
      problem is with /usr/bin/sh /home/pi/killpir.sh

      there is no /usr/bin/sh only rsh

      edit.
      ok i’ve changed path to /bin/sh and now i get error :
      grep: pir.py: No such file or directory
      pkill: no matching criteria specified
      Try `pkill --help’ for more information.

      even if pir.py is running (i can see it in ps -ef |grep pir)

      edit ok i was able to fix it i’ve edited killpir.sh to
      sudo kill $(ps aux | grep python | grep pir.py | awk ‘{ print $2 }’)

      now it will kill process pir.py

      but problem is that even if this script (pir.py) is not running the mirror still turns on when there is movement and turns off after 30s no movement … strange

      1 Reply Last reply Reply Quote 0
      • C Offline
        cruunnerr
        last edited by Aug 24, 2018, 9:36 PM

        When the pir.py isn’t running, then it isn’t this script which turns on your monitor.
        Do you have the MM-PIR module active?

        Please try to edit your rc.local and delete the autostart of the pir.py to see, if the monitor still turns on/off when there is movement.

        if not, then the pkill command isn’t working, which would confuse me, because i just tried it by myself on my mirror.
        via ssh i just entered the sudo pkill $(ps aux | grep python pir.py | awk '{ print $2 }')" command and my pir wasn’t working.


        and to your first problem, which u solved by yourself…

        u could also try to edit the killpir.py to this:

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

        then u should be able to just let your cronjob look like:
        0 21 * * * root /home/pi/killpir.sh

        1 Reply Last reply Reply Quote 0
        • M Offline
          Maros
          last edited by Aug 25, 2018, 9:23 AM

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

          1 Reply Last reply Reply Quote 0
          • M Offline
            Maros
            last edited by Aug 25, 2018, 12:11 PM

            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)

            1 Reply Last reply Reply Quote 0
            • M Offline
              MadScientist
              last edited by Aug 25, 2018, 12:21 PM

              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.

              1 Reply Last reply Reply Quote 0
              • C Offline
                cruunnerr
                last edited by Aug 25, 2018, 1:47 PM

                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 :)

                1 Reply Last reply Reply Quote 0
                • M Offline
                  Maros
                  last edited by Aug 27, 2018, 7:28 PM

                  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 :)

                  1 Reply Last reply Reply Quote 1
                  • T Offline
                    teitlebot
                    last edited by Sep 20, 2018, 3:33 PM

                    @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?

                    1 Reply Last reply Reply Quote 0
                    • C Offline
                      cruunnerr
                      last edited by cruunnerr Sep 21, 2018, 8:04 PM Sep 20, 2018, 6:57 PM

                      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
                      
                      1. chmod +x killpir.sh

                      2. sudo nano /etc/crontab

                      3. 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
                      #
                      
                      Mykle1M 1 Reply Last reply Sep 20, 2018, 9:17 PM Reply Quote 2
                      • 1
                      • 2
                      • 7
                      • 8
                      • 9
                      • 10
                      • 11
                      • 17
                      • 18
                      • 9 / 18
                      • First post
                        Last post
                      Enjoying MagicMirror? Please consider a donation!
                      MagicMirror created by Michael Teeuw.
                      Forum managed by Sam, technical setup by Karsten.
                      This forum is using NodeBB as its core | Contributors
                      Contact | Privacy Policy