If there is no TCP connection information in the log after this, then it means the Alexa devices are not able to connect to the Monocle Gateway. It is most likely a networking related issue.

It could be a firewall blocking access to incoming connections on port 443 on the computer running the gateway. The Alexa devices and Monocle Gateway need to be on the same internal network. Or most likely the issue is DNS rebinding. See: https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding

Thanks, Robert

Apologies but Monocle Gateway is not currently open source.

We do have something called “Monocle Gateway” on GitHub however, this is not the same code. This github project was an early project providing PTZ control for Alexa connected cameras. The “Monocle Gateway” name was re-used and re-purposed but the old GitHub was not taken down. We should take it down or rename it to avoid confusion.

Thanks, Robert

@victorpatinor75

The Echo Show 5 and 8 require using our Monocle Gateway software (https://monoclecam.com/monocle-gateway). These newer devices impose stricter security requirements that prevent Alexa devices from simply accessing the camera streams directly on your private network.  Basically these devices will only connect to encrypted camera stream using real DNS hostnames and valid SSL certificates. The Monocle Gateway helps accomplish this for you and encrypts the camera stream keeping everything private and local on your network.

Thanks, Robert

It’s the other way around. The Alexa device is attempting to connect to the RTSP stream and performing a DESCRIBE requests as part of the RTSP protocol. It’s the RTSP server (v4l2rtspserver) that is giving the 404 error in response to the DESCRIBE request.

This would typically mean the RTSP URL is wrong, but it could also mean the RTSP server did not accept how we (Monocle Gateway) formed the request.

Is there any way you can temporarily host this stream and allow us to connect to it from here across the Internet. We can perform some additional tests. Is so, you can PM me the connection details.

Thanks, Robert

@scturn

Apologies for the delayed response. You should see some “INITIALIZE CAMERA STREAM” messages or something to that affect in the Monocle Gateway logs each time you attempt to make a camera request via Alexa. If you are not getting this in the logs, then maybe your camera configuration in the Monocle web portal is missing the @tunnel or @proxy tag? https://monoclecam.com/monocle-gateway/tagging

Thanks, Robert

Apologies for the delayed response. I did not think the log included the password, but its possible — I don’t think there is any other sensitive information in the log as long as you don’t care about local IP addresses and such. You are welcome to PM me the log as well.

Thanks, Robert

Glad to hear this has finally fixed the connectivity issues.

Thanks, Robert

@Monocle You did it! It works agin. Thank you very much.

@spalmisano

Understood :-)

I’m not sure why. It might have been the default or I changed it for some reason.
The below pic shows the camera itself is 554 but the NVR is 8554 for RTSP.
camera_vs_nvr.png

@ggillen

Glad you were able to get it working!

Thanks, Robert

@evanh

Sorry for the delayed response. An ARM64 build is available for Monocle Gateway on a Debian-based Linux: https://monoclecam.com/monocle-gateway/install/linux-arm64

Thanks, Robert

@jkwhle23

OK, I have the same firmware version. I’m going to post my camera settings so you can compare and maybe try them out to see if you get any better results. I do remember that the audio codec settings were a little picky on these older camera models. I think I had to drop mine down to 8K from 16K.

Video Settings:
video-settings.png

Audio Settings:
Screen Shot 2020-06-04 at 3.21.38 PM.png

System Info:
Screen Shot 2020-06-04 at 3.22.03 PM.png

Thanks, Robert

@Monocle

Hi Robert.

I didn’t make it clear in my last post, I’m not actually sure how to send you the relevant logfile that you need to help to troubleshoot the issue.

Could you please tell me how I can access the log file (also, how can I PM you on here).

Appreciate your time

thank you

@ggillen

Sorry, this is an Amazon issue. All of the rendering of the camera stream is handled entirely by the FireOS. Please report this is as a bug to the Amazon Alexa team. Sadly the FireTVs and Shows run separate branches of firmware so that is probably why it work on the Show and not the FireTV.

Thanks, Robert

@Willi-Monocle

When I read “Windows 2016 Server” in your original post, I assumed Windows server for the Monocle Gateway.

So please go ahead and forward the log that captured the startup and let’s see if there are any errors on startup. Else could the QNAP be blocking access to port 8554?

Thanks, Robert

I have the same issue (Works on G1 but not 8). If your stream allows you to lower the resolution it might work for you https://forum.monoclecam.com/topic/744/echo-show-8-2019

Neither of my Dahua streams allow me to drop to a compatible resolution.

It always responds to my North Idaho “Red Neck” accent! Go figure?

@sachdientugoogle

Based on the log data, the camera is returning a 404 (NOT FOUND) error code when we attempt to issue the RTSP “DESCRIBE” request to the RTSP URL provided: “rtsp://192.168.5.45:554/onvif1”. Have you confirmed this RTSP URL working in VLC or some other RTSP viewer?

Thanks, Robert

@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