@Reif

I installed Plinkington in mine. Completely satisfied. I did however buy it from a local glass shop, they ordered it in and cut it to my specs. I would suggest you do the same as the shipping alone is twice the cost of the mirror.

That’s great news! I’m gonna install it today and give it a whirl. I’ve spent too much time swearing about the other one not working like it should. I’ll let you know how it goes.

@anhanyoung91

MMM-Ring, although not maintained, it still works. I am currently using it. It does indeed work with motion, but your ring needs to be configured for motion alerts. There are a couple of problems though. There is about a 10 second delay before your feed shows up on your mirror, my guests are often already in my place before the feed shows. Also, the authentication key will need to be manually updated every month.

Have fun with the module though.

@karsten13 Yeah, I was messing with that a little today. I couldn’t find an iframe that was reliable enough.

I ended up installing a Home Assistant add-on called go2rtc to serve the video and on the magic mirror, I installed the MMM-WebView module. It works a lot like an iFrame but more stable.

So far, it seems to be working. I have MotionEye and SecuritySpy sending command line webhooks upon motion triggers to Home Assistant that in turn shows and hides the module on the magic mirror. I would have liked to get MotionEye working, but this actually sems faster and more stable.

Thanks so much for your help though, to both of you.

@sdetweil So what would you suggest? Is there another address I can have MotionEye listen on while leaving the Magic Mirror address on 0.0.0.0? I see an option to configure that in MotionEye.conf. I just don’t know what to set it to.

@sdetweil said in CORS, MotionEye & MMM-Remote-Control:

they check the IP address/name of the client making the request.
localhost is inside the same system
192.168 or 10. or 172. are non routablebip addresses, so sekfvcontainedvsyatens like localhost
0.0.0.0 is undetermined… and is mostly rejected .
as I said, it’s not a valid IP address, so it should never be sent to the other side as part of the request

Its funny though, it is only since MM v.2.17 I have been having issues with MMM_MotionEye and the address: "0.0.0.0" issue. It was fine before. I don’t know what changed other than CORS.

@sdetweil

I turned off the ipWhitelist, I was unable to connect MMM-Remote-Control or send any command line to the MM.

I did notice that MotionEye and the Mirror are both listening on “0.0.0.0”. Is that normal? Could that be my conflict? Can i set MotionEye to listen on another ip, if so, which one???

@sdetweil Hello Sam;

In playing with the address, I have discovered that MotionEye does seem to display an image using address: "192.168.1.200", (the direct URL of the Magic Mirror, and running MotionEye). However, Motion Webhooks show the image then won’t hide anymore. They just stay onscreen.

Currently, I have my config set as so:

address: "0.0.0.0",

…

ipWhitelist: ["::1", "::ffff:192.168.1.200", "::ffff:192.168.1.1/120", "127.0.0.1", "::ffff:127.0.0.1", "::ffff:192.168.1.42", "::ffff:192.168.1.23", "::ffff:192.168.1.69", "::ffff:192.168.1.100"],

trying to cover all bases here. The Mirror still shows a broken image icon, but if I log into the web portal of the mirror, that show’s the camera feed no problem. How can I fix this??>

So this is not so much of a bug as a conflict within the system. It seems that since verson 2.17, CORS is preventing MMM-MotionEye from loading an image. I just get a broken image icon. If I change address: "0.0.0.0", to address: "localhost",, I get an image, but can no-longer run it from the web interface or command line. Further, MMM-Remote-Control requires address: "0.0.0.0", be set in config.js.

I have messed with all kinds of ip whitelist stuff to no avail, as well as played with all kinds of options in motion.conf and motioneye.conf. Nothing seems to work.

Does anyone here have a solution or work-around? I can’t get any answer back on the MotionEye Git Hub.

Any help would be greatly appreciated! I need this module to work!

@piwy Salut Piwy;

Essaye de changer des paramètres dans motion.conf & motioneye.conf. Il ne sont pas accessible de la GUI. Voir avec Terminal; /etc/motioneye/motion.conf et trouve webcontrol_localhost, si c’est “on” change ça pour “off”.

En /etc/motioneye/motioneye.conf Change motion_control_localhost true pour motion_control_localhost false .

Essaye ça.

@Reif

I installed Plinkington in mine. Completely satisfied. I did however buy it from a local glass shop, they ordered it in and cut it to my specs. I would suggest you do the same as the shipping alone is twice the cost of the mirror.