Read the statement by Michael Teeuw here.
Motion Detector
-
-
@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 :(
-
@DirkS forget my last posts… i restarted (reinstall MM) everything and i m trying to figure out how to avoid the black screen now…
-
This post is deleted! -
@chrisvanlaar said in Motion Detector:
After reading here the motion works on my MM.
Now ik want to go out of the sleep mode when a new mail or i get a phonecall. (it reads from my Fritzbox).
Can i build in this option also? or is it better in the phone/mail module.Chris
I mean that i have the camera module connected to my PI3. In the /boot/config.txt i had the (@reboot sudo modprobe bcm2835-v4l2 ) and it works! :-)
Chris
-
Hi All,
I’ve revamped the motiondetector module to use a more optimised code to detect the motion from the web camera. The old one was performing very poorly. The new code works many times better. Just pull the latest from
https://github.com/alexyak/motiondetector
- Alex
-
Hi Alex,
thank you so much for your work! Unfortunately my MM start with a black screen after the update. I tried to reboot my Raspi but it didn’t help. Should I make a npm install after the update?
THX -
and this is the error:
-
@trividar My apologies. This should be fixed. Just pull the latest.
-
@alexyak Now my MM start. But after awhile (2 min) i got this error and my MM freeze:
I disabled the DHT module but than i got this error:
Do you have also a solution for this? THX a lot!
-
@trividar I don’t see anything related to the motiondetector in your logs. It seems the error coming from the mmm-systemperature/node_helper.js
-
I disabled mmm-systemperature and now I have no errors on my log but after first deactivation of the monitor my raspberry freeze completely. Before the pull everything works perfekt beside DHT, now nothing works ;o( strange…
-
@trividar I’m having a similar issue. My mirror will turn on and off a few times, but after a few minutes it will peg the RAM and completely lock up the pi. Not sure what to try next.
-
I have also experienced something similar, always while running under a heavy load. Are you running a lot of modules, or anything that is very intensive? Some tasks like video streaming are incredibly demanding on the CPU.
My working solution was to modify my module selection so I’m not overworking the processor, and to increase the ‘updateInterval’ in my SystemStats section of config.js. Maybe try 15000 or 20000ms, see if it the crash occurs less often. I also run WatchDog and it would register the SystemStats failure. I don’t see WatchDog in these logs so this may not apply, but I also added increased ‘interval’ and ‘timeout’ settings to config.js. I have not seen this SystemStats crash for quite a while.
FWIW - after this crash WatchDog/pm2 does NOT restart my mm shell. All the other failures auto-restart, but something about this one crashes to the desktop. Also - sorry for threadjacking a “Motion Detection” thread!
-
I tried to increase the updateInterval to 200000ms and disabled all other modules, but always after the second time the monitor turn off my raspberry freeze completely and I have to reboot. My CPU is around 9 -15% when they freeze. I try again with the old version oft he motion-detector and it works, not perfect but works.
-
@in_a_days I guess I do run more modules than what “fit” the screen, but they’re cool and I can’t make up my mind which ones I want to keep lol.
However, I don’t believe that is the issue here. I have disabled all but three modules and still face the same issue. The second time the screen goes to sleep, it will not wake up. It doesn’t seem to matter what the CPU load or RAM is at.
Watching the pm2 logs, I get an uncaught exception error when the screen is supposed to wake up, but that is all the details I get from it. (That I know how to see, still new to this)
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