Hello, checking to see who has this working through the NVR? I can easily get this working from the camera direct but if the camera is plugged direct into the nvr using the internal network I am unable to view the stream. I can get it to work from vlc. I use the ip of the nvr and tried what the rtsp port is and also the virtual host port of 65002. (rtsp://10.0.0.121:10554/Streaming/Channels/102) I have tried changing the rtsp ports as well and nothing. I am tiring to view this from fire stick or alexa and nothing. I am also using simple passwords to eliminate any issues and i have the gateway running, thinking it may have something to do with the internal address and routing but that does not explain why i can get it working from vlc. any help would be appreciated.

@Ralph
There may be a Monocle config hack to get it to run other than on 443. The problem then would be that Alexa insists on port 443. I’m pretty sure that if I were still in practice that I could do a transparent proxy pipe to another port on an Apache server on Linux, so you may be able to that with IIS. Monocle likes 127.0.0.1, so that should improve security/performance at least marginally over a true network proxy pipe.

@kickapoo as much of an annoyance as it is, you could try changing the audio codec to NONE which may help with the buffering

Is the camera and the rasbery pi connected to the same router

I was having issues as I had my rasbery pi connected to a different router, I connected both to my main router and it works fine

I have the same camera and the same problem. It’s been over a year with no response so I suppose it’s safe to say the developers of Monocle have disappeared.

@mudgen Two cameras - Genbolt GB-100S and IEGeek Outdoor 1080p CT0414BKUK, both have the same problem, Yes it looks as if some connection is being made successfully but then nothing happens and the connection closes immediately. I have used the noaudio tag to rule out one possible issue. All is fine under other mobile and PC apps and VLC Player and so it has to be that Alexa is being sniffy about some setting or other. Perhaps she simply doesn’t like these cheap cameras.

i saw this error. what is?
[DEBUG] <RTSP-PROXY> [RESPONSE] <-- [451 (Invalid parameter)] <cseq=1> (session=undefined)

@aatommy said in Dahua IPC-HDBW4421F-AS & Alexa ECHO Show 5:

Thanks, I have already tried that, I also tried some other Dahua Cameras with the same results. My conclusion is something to do with the show5, I can connect all my cameras using the free Dahua supported IMOU App (only sends substream) which seems a better option than having to have a proxy server running, I liked the idea of having the cameras run internally on my network and that I might be able to choose the wide screen display option, but on reading the forum it suggests that Amazon are going to force additional security which means I would have to use the gateway.
The way the Monocle works and the simplicity all make for easy setup but like others I have been frustrated with getting it working, I will try on Fire TV when it arrives, just to see if it was me all along.

i have same problem with dahua camera

Same issue, Hmmm camera is not responding. I have non-standard RTSP ports configured on the camera configuration with Amcrest IP Cameras. Port forwarding enabled in the Linksys router config just in case.

This is the same on 2 different Amcrest cameras.

Is there relevance with the last number in the RTSP url? Does it need to be 2 for channel 2 or sub stream?

Has anyone found a solution.

Same. All the fields and ports are correct. Invocation to Alexa to show camera - hmm the camera is not responding. Not sure if there is an issue with the RTSP url or something else.

Found part of problem i hope, when i initialize the gateway one of the lines says “rtsp proxy stopped” with a code, so i think this is the problem, just not sure how to resolve.

Thanks

Not sure what happened above.

I’ve tried the connections below, the first image is to show that someone has succeeded at getting the same camera working. The following one is my settings.

rtsp://192.168.1.156/11 - Can view in VLC media play but Alexa says “the camera isn’t responding”

rtsp://192.168.1.156:554/11 - Can view in VLC media play but Alexa says “the camera isn’t responding”

Ha, sorted now, when i installed the Visual c++ ,i put the (*64) package on, because i have a 64 bit machine, after some more intergoogleing i put the (*86) package on and i works a treat now.

Thanks for you help.

Sorted now, had to reset password then seemed to let me back in.

yes, I experienced the same, here it is about 40seconds.
I use the proxy-tcp for my alexa 5. after 40 seconds they start buffering and about 3 seconds later is the connection stopped

I also have alexa 10" they don’t use proxy or tunnel and are working flawless. no time limit.

common problem.
some people have 20 seconds, I myself have about 40 seconds.

thee seems to be no solution…