@griceluke I had the same issue with Monocle unfortunately. I passed the camera feeds through Frigate and used the restreamed feed from there to feed through to Alexa rather than direct from camera.

Otherwise, you could try using ONVIF Device Manager to absolutely confirm the url and if you have 2 streams or more available, start by trying to view the lowest res stream first on the Alexa device.

I did run into a camera that I could not get to work in Monovle no matter what I did. I ended up after WAY to many hours of trying to solve it, moving to Scrypted. That also works with Alexa. Good luck!

So I figured it out thanks to this troubleshooting guide on DNS Rebinding. No idea what that is, but that was the problem!

On my router, which is an Asus RT-AC68R/U and uses the Advanced Tomato firmware, I had to add this to the Advanced Settings->DHCP/DNS Server (LAN)->Dnsmasq custom configuration field:

where the FQDN value was found in the monocle console window.

I couldn’t figure out how to add a wilcard *.mproxy.io. If anyone knows how to do that, that would be appreciated!

@warezmonster Anyone?

I have this exact same problem. Digest is not working. Would appreciate you guys having a look at this. I can include logging. The Axis Camera station is far less secure if we have to revert to basic authentication to make it work. Any chance for some help with this?

I have now got the Monocle gateway running successfully on a Raspberry Pi3.
Following the guide was straight forward although the .tar file didn’t work I just used the dpkg install instead and that worked first time.
Next step…
Add the Monocle app to the TV Firestick.
Thanks again to the team.

I can check the dlink RTSP work on VLS
rtsp://IPADDRESS:554/live1.sdp

but on Alexa, it does not.
what I am missing?

I have tried with/without tag

@tunnel
@proxy

Hello, I have Foscam G4P and C2 in use with the Monocle Gateway 0.0.4 in a Debian container under Proxmox. The display is an Echo Show 5 and Show 8, which works fine (except for the delay when the stream starts).
After a firmware update of the G4P to a version greater than 2.39 (currently 2.53), the streams of the G4Ps no longer work. However, the streams can be watched with VLC. Downgrade the firmware and it works again. However, I would like to use the current firmware. What can I do? What data do you need from me for help?

Best regards
953ebc7b-1568-4c76-940e-954690612e63-image.png
2fbca464-b07b-470d-8533-9e4701a33465-image.png
91c1b585-2ebf-43c0-b79d-754fb8c363c0-image.png

@Monocle
Hi Robert … mystery of the password solved.
In fact the password was blank (null).
Why onvif said it was ‘tlJwpbo6’ I have no idea or why it worked with that.
I reset password to ‘admin’ and used that and all is well (without the gateway and without the audio)

Kindest Regards
Graham

Trying again now using Home Assistant Proxy.

Works fine with VLC

Proxy stream is:

rtsp://192.168.244.172:5554/walkway

172 is HA box.

Hopefully this way the stream is faster.

No luck yet.

manufacturer : IPCAM
Model :C6F0SfZ0N0P0L0
HArdware : V11.1.4.5.1-20161104
Firmware : V11.1.4.5.1-20161104
rtsp://192.168.1.112:554/11
@tunnel

No fonction in Belgium on Echo Show 5