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.

    Motion Detector

    Scheduled Pinned Locked Moved Utilities
    213 Posts 38 Posters 486.7k Views 39 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.
    • paphkoP Offline
      paphko
      last edited by

      I just tried this module but cpu load made me stop using it. Please tell me, how busy is your Raspberry with and without the motiondetector module? Mine is as follows on a Raspberry Pi 2:

      • With motiondetector enabled, there is always an electron process with ~100% cpu
      • With motiondetector disabled, I observed one or two electron processes with up to 15% cpu

      I used a dedicated motion daemon on my old version of the mirror to switch on the screen on motion and I think I will set it up again. IIRC, it used ~40% cpu on a (single-core) Raspberry Pi 1 B+. What is your opinion?

      bheplerB 1 Reply Last reply Reply Quote 0
      • bheplerB Offline
        bhepler Module Developer @paphko
        last edited by

        @paphko I just looked at my Pi 3 and I’m showing 40% usage with the motion detection module running (and failing). I suspect it’s the constant pic-compare-pic-compare loop that runs. It would be trivial to insert a wait in that loop to lower the CPU usage. Even a delay of 750 ms would probably help quite a bit.

        1 Reply Last reply Reply Quote 0
        • A Offline
          alexyak
          last edited by

          @bhepler you’re right. putting a delay should help with the CPU usage.

          bheplerB 1 Reply Last reply Reply Quote 0
          • bheplerB Offline
            bhepler Module Developer @alexyak
            last edited by

            Thanks, @alexyak. Any idea about how to get around the issue with the new security surrounding webcams?

            1 Reply Last reply Reply Quote 0
            • D Offline
              DirkS
              last edited by

              Hi, i had some issues with the PIR module where the screen doesn’t switch on anymore. Now with a original PI Camera i tried this module. Same issue, the screen doesn’t switch on but in this case no motion seems to be detected. (the PIR did detect)

              with /opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7 i can switch on the screen manually.
              I followed every tip here in the thread. So i have no idea what is going on :(

              mm-0 (out): monitor has been deactivated
              mm-0 (out): monitor :state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
              mm-0 (out):
              
              

              That is the only thing i can see in the log.

              1 Reply Last reply Reply Quote 0
              • bheplerB Offline
                bhepler Module Developer
                last edited by

                Check the console log. I suspect you’ll see a security error preventing the browser from accessing the monitor. Either launch your mirror in dev mode (modify your mm.sh script to read DISPLAY=:0 npm start dev and then restart via pm2 restart 0) or browse to your mirror’s address via a web browser and enter developere mode.

                1 Reply Last reply Reply Quote 0
                • D Offline
                  DirkS
                  last edited by

                  i don’t have a mm.sh script. Where should it be located?

                  bheplerB 1 Reply Last reply Reply Quote 0
                  • bheplerB Offline
                    bhepler Module Developer @DirkS
                    last edited by

                    @DirkS Aha. You probably haven’t set it up yet. No worries. You normally start your mirror by going into ~/MagicMirror and entering npm start, right? Just append the dev switch and you should see both the mirror UI and the browser console on your mirror: npm start dev

                    If you’re starting your mirror via SSH, prepend the command to send the output to the mirror’s display: DISPLAY=:0 npm start dev

                    1 Reply Last reply Reply Quote 1
                    • D Offline
                      DirkS
                      last edited by DirkS

                      The mirror is starting at reboot. So maybe there is a script, i installed it a few month ago, i don’t remember :D

                      If i’m testing new settings i use pm2 restart mm for example. npm i’m just using to install new modules.

                      bheplerB 1 Reply Last reply Reply Quote 0
                      • bheplerB Offline
                        bhepler Module Developer @DirkS
                        last edited by

                        @DirkS Interesting. Following the instructions I found via the GitHub MagicMirror repository, the pm2 should be using /home/pi/mm.sh to start the magic mirror process. Editing this file and appending DEV should give you the web browser console with log.

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 7
                        • 8
                        • 9
                        • 10
                        • 11
                        • 21
                        • 22
                        • 9 / 22
                        • 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