@Edgargg88

Glad to hear it was that simple!

@Monocle

first: thanks for testing. Amazon is not a good HW supporter, so i think it will be a other CAM model if the “wansview” doesnt work anymore.
But in the first step, i try with ffserver to build a rtsp server but i think the raspi is to slow for this, when it only works with reencode.

Thanks and regards
Dave

@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

@anon2828

I know this sounds trite, but try rebooting both the camera and the Alexa device. Sometimes the Alexa devices get into a state where they refuse to show an known/previously working camera feed.

If its still no working … if you are able to temporarily provide access to the camera stream over the Internet, I can test it here and see if I can get it working or at least try to determine where it is failing. You can PM me the private connection information. I should be able to test it out tomorrow.

THE ONLY difference I can see in VLC between the camera that IS working versus those that are NOT working is this:

The VLC Media Information window shows the “Decoded Format” of the camera that IS working as “Planar 4:2:0 YUV” - the other 5 cameras that are NOT working show no information in the “Decoded Format” section. All other information is identical between cameras as it pertains to the information shown in the VLC Media Information Window in the Codec Details tab.

It could be an audio related issue, but I would have to test the stream using some additional tools to find out more info.

Thanks, Robert

@TheCyberShocker

Glad to help!

Thanks, Robert

Well… I tested all possible tag combinations

@proxy, @noaudio
@tunnel
@tunnel, @noaudio
@proxy-tcp
@proxy-tcp, @noaudio

and nothing worked… :(

I am back to @proxy that gives me 5-7 sceonds worth of footage and hope someone comes up with a solution to this problem.

@MegaMatze

Sorry for the delay, I have been out of the office for a couple of weeks.

Thanks for the log. It’s telling us that the gateway is configured properly and it’s properly receiving the Alexa camera requests from the Monocle servers.

What is missing is immediately after the “INITIALIZE RTSP STREAM” block, we should see incoming TCP requests from the Echo device into the gateway and recorded in the log.

This issue usually comes down to some networking related problem. The Echo device is not communicating with the Monocle Gateway for some reason.

(1) . Is the Echo device on the same network as the Monocle Gateway. (i.e. not on a guest network or VLAN)

(2) Make sure the computer running the Monocle Gateway does not have a firewall blocking access to port 443. Make sure this computer does not already have some other service already using port 443 (Apache web server/ NGINX, etc) . You can restart Monocle Gateway and look at the log that captures the startup info to make sure it’s successfully binding to port 443.

(3) DNS REBINDING. https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding

I found the solution: it was due to the dns was dns rebinding .
the dns on my notebook was different from the one obtained from show 5.
I assigned a static ip and dns to show 5 and now it works!
thanks a lot

@Jouster-74

Glad to hear its working now! Thanks, Robert

Hi - thanks for the responses - i uninstalled everything from the synology NAS drive and tried to install on one of my PC’s that is permanently on.

Followed the (much simpler) instructions but when I ask alexa to connect it says “Hmmm the camera isn’t responding”.

Any pointer to what to adjust would be gratefully received.

Thank you in anticipation.

here is the data dump I get

INITIALIZE RTSP STREAM: Back Door NAME : Back Door LABEL : PRIMARY URL : rtsp://192.168.0.67:554/ch1/main/av_stream UUID : STREAM:1381e0f8-779e-44e3-88e7-9d3417dc738f SESS : e5f510c1-9ab6-4859-b77b-cdbbca59c676 MODIF : Wed Dec 18 2019 21:47:38 GMT+0000 (GMT Standard Time) TAGS : @tunnel

2019-12-18T21:50:19.980Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP CLIENT SOCKET CONNECTED
2019-12-18T21:50:20.112Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP CLIENT ATTACHED TO STREAM: Back Door (STREAM:1381e0f8-779e-44e3-88e7-9d3417dc738f)
2019-12-18T21:50:20.117Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT SOCKET CONNECTED {192.168.0.67:554}
2019-12-18T21:50:20.120Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT REQUEST] --> [DESCRIBE] rtsp://c120dfbd-dcf0-4e82-a200-5ad2502c1d9e.mproxy.io:443/STREAM:1381e0f8-779e-44e3-88e7-9d3417dc738f?session=e5f510c1-9ab6-4859-b77b-cdbbca59c676
2019-12-18T21:50:20.120Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT REQUEST] --> [HEADERS] {
“accept”: “application/sdp”,
“user-agent”: “Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)”,
“cseq”: “1”
}
2019-12-18T21:50:20.121Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.0.67:554/ch1/main/av_stream
2019-12-18T21:50:20.123Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT REQUEST] --> [HEADERS] {
“accept”: “application/sdp”,
“user-agent”: “Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)”,
“cseq”: “1”
}
2019-12-18T21:50:20.127Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [401 (Unauthorized)] <cseq=1> (session=undefined)
2019-12-18T21:50:20.128Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“www-authenticate”: “Digest realm=“IP Camera(C6181)”, nonce=“d6e2fe894410953a2653ec2b70a17a8c”, stale=“FALSE”, Basic realm=“IP Camera(C6181)””,
“date”: “Wed, Dec 18 2019 21:50:20 GMT”
}
2019-12-18T21:50:20.130Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT REQUIRES AUTHENTICATION: Digest realm=“IP Camera(C6181)”, nonce=“d6e2fe894410953a2653ec2b70a17a8c”, stale=“FALSE”, Basic realm=“IP Camera(C6181)”
2019-12-18T21:50:20.133Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT ATTEMPTING AUTHENTICATION: DIGEST
2019-12-18T21:50:20.134Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.0.67:554/ch1/main/av_stream
2019-12-18T21:50:20.135Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT REQUEST] --> [HEADERS] {
“accept”: “application/sdp”,
“user-agent”: “Fire OS/6.0 stagefright/1.2 (Linux;Android 7.1.2)”,
“cseq”: “1”,
“authorization”: "Digest username=“admin”, realm=“IP Camera(C6181)”, nonce=“d6e2fe894410953a2653ec2b70a17a8c”, uri=“rtsp://192.168.0.67:554/ch1/main/av_stream”, response=“b219684613e374b05cf50a7bc40214f4"”
}
2019-12-18T21:50:20.173Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2019-12-18T21:50:20.176Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“content-type”: “application/sdp”,
“content-base”: “rtsp://192.168.0.67:554/ch1/main/av_stream/”,
“content-length”: “470”
}
2019-12-18T21:50:20.177Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [ENDPOINT RESPONSE] <-- [BODY]
v=0
o=- 1576705820426873 1576705820426873 IN IP4 192.168.0.67
s=Media Presentation
e=NONE
b=AS:5050
t=0 0
a=control:rtsp://192.168.0.67:554/ch1/main/av_stream/
m=video 0 RTP/AVP 96
c=IN IP4 0.0.0.0
b=AS:5000
a=recvonly
a=x-dimensions:3840,2160
a=control:rtsp://192.168.0.67:554/ch1/main/av_stream/trackID=1
a=rtpmap:96 H265/90000
a=Media_header:MEDIAINFO=494D4B48010300000400050000000000000000000000000000000000000000000000000000000000;
a=appversion:1.0

2019-12-18T21:50:20.177Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT AUTHENTICATION SUCCESSFUL: DIGEST
2019-12-18T21:50:20.181Z [DEBUG] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2019-12-18T21:50:20.182Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“content-type”: “application/sdp”,
“content-base”: “rtsp://192.168.0.67:554/ch1/main/av_stream/”,
“content-length”: “462”
}
2019-12-18T21:50:20.183Z [TRACE] [192.168.0.63:54334 <BkNX1XOCS>] [CLIENT RESPONSE] <-- [BODY]
v=0
o=- 1576705820426873 1576705820426873 IN IP4 192.168.0.67
s=Media Presentation
b=AS:5050
t=0 0
a=control:rtsp://192.168.0.67:554/ch1/main/av_stream/
m=video 0 RTP/AVP 96
c=IN IP4 0.0.0.0
b=AS:5000
a=rtpmap:96 H265/90000
a=control:rtsp://192.168.0.67:554/ch1/main/av_stream/trackID=1
a=recvonly
a=x-dimensions:3840,2160
a=Media_header:MEDIAINFO=494D4B48010300000400050000000000000000000000000000000000000000000000000000000000;
a=appversion:1.0

2019-12-18T21:50:20.184Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP CLIENT SOCKET CLOSED
2019-12-18T21:50:20.194Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP CLIENT DETACHED FROM STREAM: Back Door (STREAM:1381e0f8-779e-44e3-88e7-9d3417dc738f)
2019-12-18T21:50:20.196Z [INFO] [192.168.0.63:54334 <BkNX1XOCS>] RTSP ENDPOINT SOCKET CLOSED [192.168.0.63:54334 <BkNX1XOCS>]

@ijourneaux ******************************************************************

__ __ ___ _ _ ___ ___ _ ___ * | \/ |/ _ \| \| |/ _ \ / __| | | __| * | |\/| | (_) | .` | (_) | (__| |__| _| * |_| |_|\___/|_|\_|\___/ \___|____|___| * * MONOCLE RUNTIME ENVIRONMENT

VERSION = 0.0.4
OS/ARCH = win32\x64
PROCESS = monocle-gateway (PID=10408)
TIMESTAMP = 2019-12-23T00:07:46.159Z

MONOCLE GATEWAY SERVICE (Version: 0.0.4)

[Monocle Starting]
[Monocle Connecting]
[Monocle Started]
[RTSP Server Starting]
[RTSP Server Listening] 0.0.0.0:8555 (RTSP)
[RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS)
[RTSP Proxy Started] (PID=10092)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
[Monocle Connected]
[RTSP Server Registered]

MONOCLE RTSP SERVICE - INITIALIZED FQDN = 462b9051-c4b6-449c-91a3-97f3dd47dc44.mproxy.io
HOST = 10.8.2.24
PORT = 443 INITIALIZE RTSP STREAM: Backyard NAME : Backyard LABEL : PRIMARY URL : rtsp://192.168.1.32:88/videoMain UUID : STREAM:9b691104-7a44-4bc4-8fbb-f5135e69db7a SESS : d03168da-f2dd-4ca6-8e6a-ced46d2a3afa MODIF : Sun Dec 22 2019 19:06:55 GMT-0500 (Eastern Standard Time) TAGS : @tunnel

I have never been able to get my Reolink RLC-520’s working on my Echo Show 8. These cameras work great on the Echo Show 10 2nd Gen and also on the Fire TV 4k Stick. Any ideas?

@mattbradley109 the fact we get nothing logged in the gateway makes me think its not getting very far at all…

@chester40391

If the Show 8 is updated to allow H265 would this change the 1080P requirement?

It’s possible, but that is entirely up to Amazon. I for one would love to see them add H.265 support … but I’m not holding my breath. It could be a hardware limitation if they are using hardware decoding capabilities.

Also odd that my shiny new Echo Show 8 has a lower resolution than my original now ancient 1st gen Show.

I was surprised as well by the 1080P limitation. It’s all up to the Amazon OS system software. On the larger Echo devices, they can handle up to 4K streams and simply scale down for their native screen resolutions. I don’t know if it’s some processing power limitation on the Echo Show 5 and 8 devices or if they just imposed some arbitrary limit for no good reason. It is a bummer and pretty sad.

Thanks, Robert

@FineSir I have tried both digest and basic as well as no authorization. Iv tried just about everything I can think of. Gotta be something simple I’m missing. Thanks for the suggestion. I’m gonna try and get a log posted. Pretty quiet around these forums though…

Mines working too. Thank you!

@Monocle Thank you very much for your feedback. The cameras are working normally.

The certificate issue should be resolved now. You may need to restart your Monocle Gateway instances.

Thanks all is good!

ah. I didn’t pay close enough attention- I see the firestick now - there has been recent dialogs about a nuance between the 5 and 10" vs the 8" having some problems with SSL cert and I have 1 of each so was looking for your feedback thats why my stupid question.
1 sec speeds - wow. I’ve a full 5 second display delay - but I blame that on the BlueIris server being underpowered on my end (and too many HD cams feeding!)
I recently installed a 10Gb switch at a prison to handle some traffic of the 300+ cameras - I’ve been considering getting one for the house and then a few 10Gb NIC for each of my machines (3 servers, 1 workstation). Not sure if that will have any impact on the delay tho. I guess I could throttle the streams and see if the speed improves. When I switched from Direct to cam using Monocle web proxy to BlueIris front ending my cameras I doubled the delay from 2.5 secs to 5. I had to do this because certain cams just won’t work due to various reasons - but the BI solution got all my cameras going :) I’m looking at your solution as a way to possibly improve that delayed response. thanks for all the input!