Read the statement by Michael Teeuw here.
Motion Detector
-
@reaper81 I had the following in my config.js:
{ module: 'motiondetector', config: { timeout: 5*60*1000 } },
You will need to ensure that the 3 files are located in the modules/motiondetector folder.
I ended up using a different method for motion detection though, as tvservice kept stopping working.
-
So after far too many months, I’ve finally gotten my mirror put together. Everything is working great, except for this module (sometimes). After a reboot everything works at least once, meaning that the monitor will turn off when no motion is detected and turn on once motion is detected. Sometimes, it will work correctly for an entire day. Others, it will work once and then the monitor will not turn back on until I reboot the pi. After the monitor refuses to wake up, I receive the following in the pm2 logs when it does detect motion.
0|mm | monitor :state 0x7ee68dbc [HDMI unknown AR x38128 HDCP], 2129038664x4287062190 @ 45744.00Hz, interlaced 0|mm | monitor :state 0x7ee8bdbc [HDMI unknown AR x13552 HDCP], 2129182024x4287062190 @ 21168.00Hz, interlaced 0|mm | monitor has been deactivated 0|mm | monitor :state 0x7ebe5dbc [HDMI unknown AR x25840 HDCP], 2126404936x4287062190 @ 33456.00Hz, interlaced 0|mm | monitor :state 0x7e9afdbc [HDMI unknown AR x13552 HDCP], 2124086600x4287062190 @ 21168.00Hz, interlaced 0|mm | monitor has been deactivated 0|mm | monitor :state 0x7e8dadbc [HDMI unknown AR x21744 HDCP], 2123214152x4287062190 @ 29360.00Hz, interlaced 0|mm | monitor :state 0x7efdcdbc [HDMI unknown AR x54512 HDCP], 2130562376x4287062190 @ 62128.00Hz, interlaced```
Does anyone have any thoughts on how to prevent this from happening? Is there a better place to look at logs other than pm2 to see exactly what is happening. It is very odd to me that it works for different amounts of time after each reboot.
For what it’s worth, when the screen stops waking up, I can navigate to rasperrybi.local:8080 in a browser and all of the modules are up and running.
Any thoughts or comments are appreciated.
-
@jdahli1
I don’t know this error, therefore the following two comments might be totally wrong:The motion detector uses
/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7
to switch the monitor on. What happens if you execute this command manually while the observed problem occurs (I assume you can still login to the PI?). Then you might know weather it is a problem of the motion detection (and MMM) or if it is a more general problem. Maybe you even get additional error messages that help you to identify the problem
- Do you know the HDMI-settings in /boot/config.txt ?
Maybe it is worth to play around withhdmi_force_hotplug
,hdmi_drive
,hdmi_group
andhdmi_mode
. See the file and here https://raspberrypi.stackexchange.com/tags/config.txt/info for more information. Maybe the “AR” in your error stands for “aspect ratio”, this could be set explicitly be these parameters.
If somebody got this module to work on a Raspberry Pi Zero (using the Midori browser) I would be highly interested in how it was done!
- Do you know the HDMI-settings in /boot/config.txt ?
-
@Hawking Thank you for the reply. Running that command does not appear to do anything. I let it sit for a minute and the command never completes, nor does the screen come on. It will sit until I ctrl + c. I will start to mess with the hdmi settings and see if that makes any difference.
-
@jdahli1
Can you just execute/opt/vc/bin/tvservice --preferred
to see if it is tvservice or chvt that does not respond?Here https://news.screenly.io/how-to-automatically-turn-off-and-on-your-monitor-from-your-raspberry-pi-5f259f40cae5 also problems with turning the screen back on using tvservice are mentioned. Maybe the other methods mentioned in the article are worth a try. If they work you can simply change the commands used in
~/MagicMirror/modules/motiondetector/node_helper.js
-
@Hawking So running that command has the same result - nothing happens until I ctrl + c. I have been messing with the hdmi_* commands, but no luck so far.
-
Can I use the Pi-Camera for Motion Detection and Face-Recognition at the same time or have I to use seperate cameras for each module?
-
@reaper81 said in Motion Detector:
Can I use the Pi-Camera for Motion Detection and Face-Recognition at the same time or have I to use seperate cameras for each module?
This uses a pir-sensor
-
@reaper81 You can use the same camera for both, but you’ll want to use a different module for motion detection. If you check out my posts, I put up a tutorial on using the PiCam for motion detection outside of the MirrorMirror framework. There’s no reason you can’t use my tutorial to get motion detection to turn your mirror display on and then the facial recognition module to switch the layout.
At least… no reason that I know of.
-
@jdahli1 Anyone have any thoughts as to what else to try? I have had no luck so far. Mirror continues to not turn back on randomly. Nothing I have changed so far seems to have worked. Any thoughts are appreciated.