@Monocle

Thank you, the tag @fake-fmtp along with @proxy-tcp works a treat now. Takes around 15 seconds to load the stream but once it does it is fine. No failures either!
I moved my DNS to PiHole and disabled the “DNS Proxy” option in my router settings. Added an exception for the Alexa device on both its WiFi IP’s and made them static… Happy days till something updates…

Cheers

@FineSir

In my experience the latency seems to be camera dependent. Some cameras I am using have a 10-15 second latency and other have a 5-10 second latency.

There may be a slight latency difference were the 10" may edge out the 8", but it may be only a second or two. Certainly not a dramatic improvement/difference.

I believe the latency has more to do with the limited processing power and H264 decoding capabilities of these devices. I see similar latencies when viewing my camera feeds from a Raspberry Pi.

Thanks, Robert

@shelzmike Hi - in the end (for more reasons than just this) I ditched the Ubituity routers and went back to Asus, purchasing a blue cave - as soon as I did that it worked perfectly.

Monocle is now running on my Qnap Nas router in a container.

yes my devices do require authentication - but if the cameras work on an old device (say a show 1) then I cant think why they wouldn’t work with exactly the same config on a new device (Firestick 4k) providing the gateway is behaving.

@shelzmike

The delay/latency you describe is unfortunately typical. The best I have seen is about 5-8 seconds. 10-15 is common though. It seems to highly depend on the camera. I suspect it’s something to do with the limited processing power of the Alexa devices or the lack of hardware H.264 decoding. I get about the same latency when trying to view a RTSP stream from a Raspberry Pi (similar ARM-based device). If I view a RTPS stream from a desktop computer, I don’t see much delay at all.

The Monocle Gateway should not add any additional noticeable delay. Maybe 1 second or so. So the gateway is not where the bottle neck is.

Thanks, Robert

Another one interested on this! o/

@Hamerdrome

The Monocle Gateway is required for Echo Show 5 and 8. It’s not a camera limitation in this case, but rather a limitation of these Echo Show models.

Thanks, Robert

@Monocle - Any news regarding HLS support? - Did you have the chance to look into that?

I have 3 Reolink cameras all showing up on request on Echo Show 5, Show 8 and Spot. All I had to do was update the firmware on my RTLC-410, RLC-511 and RLC-423 and then install the Reolink Alexa smart app.
Monocle was not required. https://support.reolink.com/hc/en-us/articles/360037976953-How-to-Add-Reolink-Cameras-to-Amazon-Alexa
https://support.reolink.com/hc/en-us/articles/900000616606-Which-Reolink-Cameras-can-Work-with-Amazon-Alexa
Update the firmware first…

Chris Muriel, UK.

That Echo model is a 10 not an 8. I’ll try and figure out how to edit shortly.
Dale

@kwijibo00

Nope, same issue running on a different system, (Windows 10). Same error

Cannot read property ‘match’ of null’

@endermouse

I don’t think we have any dependency on Java itself – of course it very well could be some other (shared) dependency that gets installed along with the Java installation package.

Thanks for the follow-up!

Robert

@YumYumTuete

Please try rebooting your Monocle Gateway instance if it’s still not connecting.
There was a short period of time this morning (about an hour) where this service was down for maintenance. But it should all be up and running now.

Thanks, Robert