I also tested my old echo show 1st gen, and this driveway camera works (as do the others) flawlessly on the old echo show technology.

Bear in mind that you will be proxying your rtsp stream out to AWS and back. This probably fine if you’re on a fast unmetered Internet connection.

@mwoodage said in Reolink Camera wont show on Alexa TV [SOLVED]:

@james123 said in Reolink Camera wont show on Alexa TV [SOLVED]:

/etc/init.d/dnsmasq force-reload

Really interested in this post - i’ve got exactly the same problems with Reolink cameras, although i don’t have the same router as you. My router is a UK plusnet router, any ideas on how to get DNS binding active on that router?

Thanks in advance,
Martin

Hi,
I have Hikvision cameras and a Plusnet One Hub. Can find anywhere how to do the rebinding. I followed the guide on nslookup and its point to the binding issue. Anyone able to help a novice with some pointers?

Thanks

Steve

@paulbiod said in RTSP CLIENT SOCKET TIMEOUT:

. Anyway, I tried to delete this routing

Based on the log info posted it seems like your Monocle Gateway is working. It appears that your Echo Show 8 is attempting to connect to the camera stream but is immediately terminating the RTSP connection. This is a common behavior when the Alexa device REJECTS the RTSP stream. Unfortunately Alexa does not provide us any details on why she does not like the stream – even when its a perfectly playable stream in FFMPEG and VLC.

So all we are left with is shooting in the dark and trying to find some combination of settings that make Alexa happy. I would suggest trying the tags @fakefmtp,@noaudio,@tunnel or @fakefmtp,@noaudio,@proxy

443 port is free on my PC, but in my router is configured to route to my raspberry. An

No externally exposed ports are needed for Monocle Gateway. Monocle Gateway connects outbound to a Monocle Web Socket server to get notified of Alexa requests and then Alexa devices connect to the Monocle Gateway locally inside your network.

Thanks, Robert

I’m not too sure either.
Make sure all your ports are open on your gateway server. I did have issues when running PiHole DNS and a firewall on my gateway.
I’d troubleshoot the basic stuff, make sure you use the sub or third stream and set the encoding on the NVR or camera if it is standalone.
Might best best to directly RTSP from the camera to the Alexa, in that case set your encoding on the camera itself.

@julman64 Take a screen cap of both VLC strings that are working. is the only difference the IP address?
Regarding port forwards, I’ve never seen any commenter working on this problem discuss the need to do that. I didn’t need any changes, but I also do have uPNP set to on if that helps or matters.
At this point, you could attempt to enable a local gateway. It is possible your version of OS on the Alexa is newer and requires the TLS/SSL workaround the gateway provides.
The instructions on setup of a local gateway are located within these pages. I run completely without a gateway and have for a long time - but I’m using a BlueIris server which gives a consistency and simplifies things tremendously for me. Originally when I first setup (now years back) I did try the gateway as I was trying to go direct to the camera feeds and struggled. Once BlueIris added Amazon support I switched to using a BI stream and all my problems dissolved and the gateway was no longer needed in my environment.

One last thing, just to vocalize it in case it helps others, be sure you have the Amazon ‘Monocle’ skill linked. While helping someone else recently it was found that person was completely unaware it was needed! I noticed you said you linked the skill - but maybe a double check?

Speaking of Amazon - I will say this: Once a device is described in the Monoclecam Web, that device can be adjusted - as long as the NAME of the device is not changed. Be sure to ‘remove’ discovered devices and do the ‘discover’ on alexa to be certain the right device(s) are added at the Alexa devices list.

If you get this far and things still aren’t working and you begin to tinker with the local Monocle gateway - there are many options there to review and it is more complex; too much for me to discuss the little I know!. There are great instructions about how to check it’s use here within this forums and documentation. In the end, noting the similarity of the specs of your cameras, I think this is a simple IP problem IMHO.

@Monocle
Everything working as anticipated now. Thanks

Stream still doesn’t start. Echo only tells “Cam doesn’t react”.
Very disappointing.

I can’t seem to download it. I get a error cannot resolve host

Did you get to the bottom of this? I am seeing something similar with Eufy cameras (running factory default firmware). I can confirm they work in VLC and in their own native app.

@MOB

The Echo Show 8 will require the use of Monocle Gateway running locally inside your network. Also the @tunnel tag is only used with the Monocle Gateway.

I can’t speak to the compatibility of this specific camera, but if you don’t have the ability to run the gateway, then using Monocle is probably a NO-GO in your situation.

Thanks, Robert

@MacUsers

As far as I know I’m the only reported working success story on the Echo Show 10 Gen 3.
I never experienced it not working so it’s hard to say if its a camera compatibility issue or if some Amazon firmware/system update occurred that fixed the original issue.

So at this point, all I can suggest is that you try and it see … with the caveat that you may end up having to return it if it does not work for you.

Thanks, Robert