Motion Detector

bhepler

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

alexyak

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

bhepler

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

DirkS

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.

bhepler

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.

DirkS

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

bhepler

@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

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.

bhepler

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

done

Hi and thanks to everybody making this module work!

@cpramhofer Did your solution solve the issue that the monitor did not switch on again after a longer period of time?