CORS, MotionEye & MMM-Remote-Control

[sdetweil]

@SdeGeata we updated libraries we use, so it could be anywhere.

[SdeGeata]

@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]

@SdeGeata the physical adapter ip address
the command

ip addr

will give you the configured addesses

[karsten13]

@SdeGeata

Its funny though, it is only since MM v.2.17 I have been having issues with MMM_MotionEye

MM is an electron app and electron uses chromium as browser. All browsers are more and more restrictive concerning cors when releasing new versions.

I tested MMM-Motioneye with my setup and was not able to get it running.

Another approach is to use MMM-iFrame instead which worked on my side.

[SdeGeata]

@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.