@J9Web

Some Alexa devices require using our Monocle Gateway software running inside your network to facilitate the requirements for newer Amazon devices like the Echo Show 5 and all of the current generation FireTV 4K devices.

I don’t have a recent FireHD 8 to test with, but I suspect its the same issue.

More details here:
https://monoclecam.com/monocle-gateway

The information on this page outlines why this is needed. (albeit for the FireTV 4K – but same reasoning.)
https://forum.monoclecam.com/topic/112/fire-tv-stick-4k-3rd-generation-2018

Thanks, Robert

@travisb1 In general, the Amcrest cameras and NVRs work well with Alexa. The Monocle Gateway is required for some Alexa devices; it may not be for all.

1920x1080 is known to work. Higher resolutions may not work; I haven’t tried.

I have blueiris as well. Unfortunately as it stands it isn’t supported. I did reach out to the developer of Blue Iris. He said this is his top priority so expect it in the next couple of months he said

I have the same camera and can’t get it work.

I can get the rtsp work on VLC, using this guide https://support.amcrest.com/hc/en-us/articles/206813947-RTSP-Stream-URLs-for-HD-CVI-DVRs-1080P-HD-CVI-

But I can’t get it work on my alexa using the monocle skill. I haven’t tried Monocle Gateway.

Have you solved this?

Nope H265 does not work
You can generally set the network or sub stream to h264 anyway. That’s what I do on UNV equipment.

Not working on two approved devices with verified proper rtsp urls (verified with VLC). I have tried every working possible combination and it looks like it tries connect but ultimately fails. Even tried opening/forwarding ports for 554 and 443 (for your proxy) with no joy. It almost looks like Alexa has been updated but the App hasn’t been.

Works with Alexa Show 1.0 without the Monocle Gateway Service.

Can’t get it to work with the monocle gateway service and my Firestick 4K (or echo show) though.

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:

address=/<FQDN value>.mproxy.io/192.168.1.8

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!