Read the statement by Michael Teeuw here.
MMM-MotionEye - surveillance video stream on your mirror!
-
@cato
made a new installation as describek by @KirAsh4 with the same result as already mentioned but found some maybe related entries in the pm2 mm-out-0.log.> magicmirror@2.1.1 start /home/pi/MagicMirror > sh run-start.sh Starting MagicMirror: v2.1.1 Loading config ... Loading module helpers ... No helper found for module: alert. No helper found for module: clock. Initializing new module helper ... Module helper loaded: calendar No helper found for module: currentweather. No helper found for module: weatherforecast. Initializing new module helper ... Module helper loaded: newsfeed Initializing new module helper ... Module helper loaded: MMM-MotionEye All module helpers loaded. Starting server on port 8080 ... Starting server op port 8080 ... You're using a full whitelist configuration to allow for all IPs Server started ... Connecting socket for: calendar Starting node helper for: calendar Connecting socket for: newsfeed Starting module: newsfeed Connecting socket for: MMM-MotionEye Starting module: MMM-MotionEye Sockets connected & modules started ... Launching application. Create new calendar fetcher for url: http://xxx Create new calendar fetcher for url: http://xxx Create new news fetcher for url: http://www.spiegel.de/schlagzeilen/tops/index.rss - Interval: 300000 Hiding camera: undefined Motion registered: undefined Motion registered: undefined Motion registered: undefined Motion registered: undefined
maybe a helpful hint ???
-
I’m on vaccation until next week (back 8th of May) and don’t have any chance of doing any testing.
Just wondering about your configuration. The values for width, autoHide, autoHideDelay and debug is not a string and you should not have the hyphen ( ’ ) around them. Not shure if it matters, but could you try to remove them?
-
@Cato
Hi, I had a bit more time over the weekend. By trial an error I found out that the problem is related to my motioneye URL string providing userid and password. Apparently the Electron browser can’t handle this. After disabling authorization in Motioneye the problem was solved. In another MM installation on a Pi Zero I use Midori as browser and this works since month without problems. Thanks for MMM-Motioneye and your help in this case. -
This post is deleted! -
which camera du you suggest? I never had one. Should work for and in my garden (to observe the kids)
-
Just have a look for the noir camera. Have a look for amazon.com. There is an official cam - I think - by the raspberry company. But any other that support the onboard psi cam plug is imho better than usb cam. But that is your decision.
-
@emos
I had that same issue. I ended up just creating a few mmm-mogioneye module entries in the config file -
Did you ever get an answer back on this one? I am having the same problem. I see everything fine without autohide active, but if I activate autohide, I see it for a bit during page load and never again after. I get detected motion emails and photo uploads so the detection isn’t the problem. It just doesn’t get fed to the mirror module somehow. Maybe my Web-hook config is off?
It would be helpful to know if you fixed your issue and how you did it.
-
Hey, SdeGeata
No, actually I didn’tI circumvented it by setting up a motioneyeos raspberry pi zero. As I needed the larger image on my Magicmirror I used “fast…?” option, which does not provide any of the motion activities,. what was fine to me.
I do think, this is not merely a problem of motioneye, but of the MM its self.
With every update of MM the Gap went bigger, I got more problems.
Now, streaming the motioneyeos to two MMs it is more steady, nonetheless I do habe outages. I don’t see a picture,. although my browser directed to motioneyeos shows an actual one. Restarting MM solves that issue- normally,…
Good look to You ! -
Thanks for the info. I’ll keep trying stuff out and see what happens.