Motion Detector

[trividar]

Thank you guys! you are amazing!

[sero]

Same here, works like a charm!
Thanks guys :)

[alexyak]

Huge thank you to @strawberry-3-141 for helping to troubleshoot this issue and suggesting the solution! While I know all kinds of dev languages and tools, I am pretty new RPI and Linux.

[trividar]

Hi guys,
I have a problem. My MM do not turn on the display in the morning. I is possible that my pi camera is in a kind of sleepmode or standby? I have to restart with pm2 stop mm and start again an than it works fine.

[cowboysdude]

@trividar said in Motion Detector:

Hi guys,
I have a problem. My MM do not turn on the display in the morning. I is possible that my pi camera is in a kind of sleepmode or standby? I have to restart with pm2 stop mm and start again an than it works fine.

I have encountered that MANY times… don’t exactly know why myself… It’s not just this module it happens with most of them… I believe once it sleeps long enough the PI doesn’t want to wake up LOL

[cpramhofer]

Hi Guys,

had exactly the same problem with mit Raspi NOIR Cam V2.1.
the sudo modprobe bcm2835-v4l2 command solved my problem.

maybe you should add this Tipp in your Readme as many people out there have the same problem.

greets
Christoph

[trividar]

Hi Christoph
Unfortunately it didn’t work for me;o( Today my screen did not turn on. My Pi works and I can connect over ssh but I have to stop and start my MM and thank works again fine. I just think that my camera stop working if there is no motion a long time (during night).

I got some errors during the night:

[alihallo]

First of all, I also had the problem which could be solved by adding

@reboot sudo modprobe bcm2835-v4l2

at the last line of the crontab. Thank you very much!

It works fine for some hours, but suddenly the monitor does not show up again.
I cannot see error messages, but the following commands does not get an answer anymore…

/opt/vc/bin/tvservice -s

There is no return value anymore, it is just loading forever.
In the log it looks like this:

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

As soon as the problem occures, the command

/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7

also does not switch the monitor on again.
It seems that the tvservice command just got a problem after some hours… Any idea how to solve this?
I need to restart the pi to get the monitor on again, after that everything works fine for some hours…

Best regards,
alihallo

[cpramhofer]

Hi alihallo,

i have exact the same problem. i also added the @reboot sudo modprobe bcm2835-v4l2 command into my cronetab.

but once the screen is off for some hours it will not switch on again.

for me it seems that the RPi 3 is going into some kind of sleepmode if the monitor is switched off for too long.

kind regards
Christoph

[cowboysdude]

This post is deleted!

[paphko]

Just as a side note, I have the same issue that my RasPi screen does not switch on again after a random time. But I am running v1 of the mirror (so not this motion detector module) and I use motion for motion detection. My guess is that this is an issue with the RasPi firmware because it was working fine several months ago (and I was frequently updating RasPi firmware)…

[cowboysdude]

I just run a straight cron job with a file called pir.py that runs two other files…

monitor_on.sh
monitor_off.sh

It’s not incorporated into the mirror it runs the entire pi and I’ve had great luck with it! :)

[cpramhofer]

hi @cowboysdude ,

could you please give me (and maybe others) the detailed instruction how these files look in detail and where those are located?

thanks a lot in advance,
Christoph

[cpramhofer]

here is what i have done, actually it works - i will watch it a few days.

switch to /bin/

cd /
cd bin

open nano and create a shell script

sudo nano monitor_on.sh

write the “On” Command in it and save with Ctrl+x

/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chat 7

open nano and create another shell script

sudo nano monitor_off.sh

write the “Off” Command in it and save with Ctrl+x

/opt/vc/bin/tvservice -o

make both shell scripts executable

sudo chmod +x monitor_off.sh
sudo chmod +x monitor_on.sh

open the crontab and add the following at the end

switches the monitor off and on every 15 minutes. this is for experimenting, i will look how it works and will set the

time up as.

15 * * * * sudo /bin/monitor_off.sh
15 * * * * sudo /bin/monitor_on.sh
@reboot sudo modprobe bcm2835-vl2

[cowboysdude]

Well hey Thanks for making that easy… was JUST working on that LOL I’m putting it on github with instructions and the files…

[cowboysdude]

https://github.com/cowboysdude/Pir-Sensor

[cowboysdude]

Update:

https://github.com/cowboysdude/Pir-Sensor

Monitor was only partially coming back on this should fix that.

[chengstark]

my monitor won’t turn back on
when I run “npm start dev”, it shows “compare result=Infinity,Infinity;0,0” , seems like it can’t capture any movement
the camera module works outside MagicMirror
when I tried “sudo modprobe bcm2835-v4l2”, it says “modprobe: invalid option – ‘4’”
how can I fix this

[cpramhofer]

Hi @cowboysdude

thank you for your files and the explanation. what i don´t understand is how this all works together with the “Motion Detector” - i would prefere to use a camera instead of a PIR Sensor but as far as i see i have to install the pir.py file which is calling the on&off files and referring to the PIN with the connected PIR sensor.

is there a way to use the on&off files with the “Motion Detector” Module?

greets
Christoph

[cpramhofer]

Hi guys

as it looks that it isn´t an MM problem but an Pi Problem…another try:

sudo nano /etc/kbd/config

change the values to zero

BLANK_TIME=0
POWERDOWN_TIME=0

good luck