Read the statement by Michael Teeuw here.
Motion Detector
-
hello! as understood there are 2 topics ongoing here "PIR module of @cowboysdude " and "motiondetector of @alexyak ". I will not ask which is the best module, you both did a great job, thx!
don’t take it bad but i just wanted to have opinions and feedback on which one is running currently without any, less issues please? (i am starting my mirror and don’t want to be too much demanding on the forum if not working - wise ;-))@cowboysdude : i have already implemented Paviro’s module to test and i wanted to know if i should remove it before installing your one?
Thx in advance for your relpies and have a good day/eve :)
-
@bibi said in Motion Detector:
hello! as understood there are 2 topics ongoing here "PIR module of @cowboysdude " and "motiondetector of @alexyak ". I will not ask which is the best module, you both did a great job, thx!
don’t take it bad but i just wanted to have opinions and feedback on which one is running currently without any, less issues please? (i am starting my mirror and don’t want to be too much demanding on the forum if not working - wise ;-))@cowboysdude : i have already implemented Paviro’s module to test and i wanted to know if i should remove it before installing your one?
Thx in advance for your relpies and have a good day/eve :)
Honestly I will you this… I liked the motion sensor BUT @ianperrin worked out a module scheduler that I liked much better! I can turn modules off and on at specific times and turn it all off when I"m not home only to have it back on again when I arrive home.
All-in-all it really depends on your needs. NOTHING is without issues of some kind. I just really disliked the PIR sensor sticking out …
I hoped this help you in some way.
OH but of course @strawberry-3-141 also made a voice module that you can just tell the mirror to turn off too :) The usb mike is about the same price as a pir sensor!!! It’s REALLY awesome!!!
-
@done said in Motion Detector:
@strawberry-3.141 Ok, I’ll give it a try. Tomorrow morning, I will test again. Thx!
WORST case senario is you install a screen saver program and disable it… period. :)
-
@cowboysdude 1st thx for taking time to reply. much appriciated! the PIR is ok but as it needs to get hidden somewhere, etc it’s less convinent. Yes you are right, the solution depends on my personnal need… i just need a way to switch on MM when i am in front of it BUT also completly switch off the monitor when nothing detected and not only the MM.
oh great, i will check @strawberry-3-141 module for sure!
@IngmarSwart also designed a solution with motion detection with a Picam behind the glass which seems to be nice to. i let you check it if interest…by the way, do i have to remove Paviro module to install your one?
i couldn’t find @strawberry-3-141 module… can you pls forward me the link? -
@strawberry-3.141 said in Motion Detector:
@done propably everything is working for you guys and you can just see the screensaver, be sure to disable the screensaver
Negative. The screensaver has been disabled but the
motiondetectionmodule isn’t working. I gave the Facial Recognition module a try, but with the camera behind the glass, there isn’t enough light to train the system to recognize anyone.At this point, I’m considering downgrading my chromium to something without the new security “features”.
-
I’m still working this problem. To help with @paphko 's concern about processor utilization, I finally figured out how and where to put a delay in the main image comparison loop. @alexyak is using the RequestAnimationFrame feature to run the comparison as fast as the browser can render the UI.
If you wish to include a delay, modify your
motion.jsfile’s main function to read as such:function main(frequency) { render(); if(rendering == true) { setTimeout(function() { raf(main.bind(this)); }, 500); } }That last number (the 500) is the milliseconds between each image comparison. I think half a second between comparisons is enough to keep the CPU usage down and the effectiveness up.
-
Thx @bhepler
this helped to reduce my temperature from 80 °C to 50-60 °C.
Maybe the 80 °C even caused the wake up problem? :)Anyway, I think I’ll try the voice activation module tomorrow.
Somehow it’s even very sweet to say “Mirror, Mirror on the wall. Wake up!”. -
That is the reason why my screen doesn’t switch on after a couple of hrs switched off.
Any idea what the cause of unavailable tvservice is?Testwise i used the scripts reported here before. They where called if a PIR detects motion or no motion.
Nov 1 08:22:00 MagicMirror kernel: [86411.138649] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.138665] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.138670] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.139138] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.139148] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.139152] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.140642] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.140654] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.140659] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.140777] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.140785] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.140789] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.140856] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.140863] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.140868] bcm2708_fb_pan_display(0,0) returns=-22 Nov 1 08:22:00 MagicMirror systemd[1]: Started Getty on tty6. Nov 1 08:22:00 MagicMirror kernel: [86411.256398] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.256413] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.256418] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.256758] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.256770] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.256775] bcm2708_fb_pan_display(0,0) returns=-22 Nov 1 08:22:00 MagicMirror kernel: [86411.296428] raspberrypi-firmware soc:firmware: Request 0x00040002 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.296455] bcm2708_fb soc:fb: bcm2708_fb_blank(0) failed: -222016.11.01 08:05:04 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to power off HDMI Powering off HDMI 2016.11.01 08:05:57 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_on.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to set property 4 2016.11.01 08:07:37 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to power off HDMI Powering off HDMI 2016.11.01 08:09:00 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_on.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to set property 4 2016.11.01 08:09:42 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to power off HDMI Powering off HDMI 2016.11.01 08:09:59 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_on.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to set property 4 ping: icmp open socket: Operation not permitted 2016.11.01 08:10:41 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to power off HDMI Powering off HDMI ping: icmp open socket: Operation not permitted 2016.11.01 08:21:59 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_on.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to set property 4 2016.11.01 08:22:50 2: KuMagicScreen: {system("sudo /opt/fhem/monitor_off.sh &")}: -1 tvservice-client: Failed to connect to TV service: -1 [E] Failed to power off HDMI Powering off HDMI -
So here i found a workaround. Maybe it fixes the issue but let’s see. I just modified my test script and need to see it the next hrs/days
-
Hi,
for all the people here I wrote it more cleary :D
i had big problems by switching off my screen with the PIR or another module with camera. The problem was not the module itself it is a firmware problem of the PI. I could see the same problem outside of MagicMirror as well by trying different things.
Reported also here:
https://github.com/raspberrypi/linux/issues/487The symptom is that after a while of switching on and off the screen it remains off.
Dmesg reports the problem:
Nov 1 08:22:00 MagicMirror kernel: [86411.138649] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.138665] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.138670] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.139138] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.139148] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.139152] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.140642] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.140654] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.140659] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.140777] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.140785] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.140789] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.140856] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.140863] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.140868] bcm2708_fb_pan_display(0,0) returns=-22 Nov 1 08:22:00 MagicMirror systemd[1]: Started Getty on tty6. Nov 1 08:22:00 MagicMirror kernel: [86411.256398] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.256413] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.256418] detected fb_set_par error, error code: -22 Nov 1 08:22:00 MagicMirror kernel: [86411.256758] raspberrypi-firmware soc:firmware: Request 0x00048003 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.256770] bcm2708_fb soc:fb: Failed to allocate GPU framebuffer (-22) Nov 1 08:22:00 MagicMirror kernel: [86411.256775] bcm2708_fb_pan_display(0,0) returns=-22 Nov 1 08:22:00 MagicMirror kernel: [86411.296428] raspberrypi-firmware soc:firmware: Request 0x00040002 returned status 0x80000001 Nov 1 08:22:00 MagicMirror kernel: [86411.296455] bcm2708_fb soc:fb: bcm2708_fb_blank(0) failed: -22Switching off the screen with
/opt/vc/bin/tvservice -o
and on with
/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chat 7
does not work reliable! The git issue tells you more about.
The workaround is a not yet described solution inside the config.txt
https://github.com/raspberrypi/documentation/pull/245/files
the option “hdmi_blanking=1” is your friend in this case! :D
Now i’m switching off the screen with
vcgencmd display_power 0
and on with
vcgencmd display_power 1
And it is working now like a charm! Did started to use it one day before this report and it is still working without any issue :)
Honestly speaking i don’t use any MM module for switching off anymore. But maybe my discovered solution will help any other and might be a way to change the module as well.
If you have trouble with on/off as well please check the output of dmesg. If you have the frambuffer problem you can fix it.
My personal solution is to have the PIR state at FHEM and from FHEM i’m using a script to switch the screen. But that’s a special case and for the most people here the usage of a MM Module will be the better way.
regards
Dirk -
@DirkS thx for sharing! one question please : where is located the option : “hdmi_blanking=1” ???
-
@bibi Based on that pull request, it looks like it’s in the
config.txtof your Pi. So/boot/config.txt -
@bibi yes you need to include it into /boot/config.txt
-
-
-
@DirkS Thank you. Pi doesn’t die over nights :D
But before I mess it up:
Would the motion detection with the common script work or not?
How did you realize it? Where did you enter your new script?And don’t you want to make an additional motion detector module for those who have the same problem? :)
I don’t see the original programmer caring to much. ;)cheers
done -
@done as discribed above by @cpramhofer (thanks to you :) ) i created the monitor_on and off.sh script.
With FHEM i’m polling the PIR status and use a DOIF to call on or off. Because my homeautomation depends in FHEM i have much more control instead of using a MM module, i switch much more devices with the PIR as well. I have several Pi’s with FHEM installed so it is also on the PI for the Mirror. -
@bib you are providing a bit less information to give you some tipp.
-
@DirkS ok here you go. 1st: when the Pi is started the screen directly goes into sleep. it’s a bit annoying but i can live with that as i will not reboot it everyday. 2nd: to wake up the system with a motion during this sleep mode, it takes quite a while (don’t know why) 3rd: when motion is detected, screen wakes up and stays up accordingly the time defined in config.js and goes sleep again (this is fine) but suddently it wakes up again without motion and this last behavior is unpredictable. i hope it’s enough info for you but don’t hesitate to ask more if needed. thx
moreover your script is i guess different from the one of this pull… -
@DirkS and i see now after few hours, it won’t wake up anymore :(
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login