Amazon Shows (vers 8 2nd gen, 8 3rd gen, 5 3rd gen) not connecting to any Ubiquiti G4 Pro cameras (13 total)

[cincyitguy]

I’ve spend a few hours combing through prior posts and learning about how Monocle works. All basic troubleshooting has not led me anywhere as everything appears to work on the surface. DNS for mproxy.io is working properly, RTSP streams from NVR for cameras resolving and working properly (tested with VLC) . No blocks in main firewall logs. No firewall running on host where gateway resides. Etc. Fresh install of v0.0.6 so this is an initial setup issue.

When I ask Alexa to “show me front driveway camera” I get the dreaded response “the camera isn’t responding”. I’ve included my logs from the monocle gateway below, which is running on a very healthy Ubuntu system. I can see 3 attempts to connect to the camera (same log data each time; only included one example for brevity) but no obvious errors that I can see. I do have a segmented network and thus the Show devices, Monocle gateway and Ubiquiti cameras are all running on different /24 networks but all security between the networks has been disabled during testing and everything is either configured by IP or DNS verified to work properly (aka zero network connectivity issues).

I’m hoping the below logs will provide some clue as to where the issue resides or some suggested additional troubleshooting steps can be identified to further debug. Thank you.

---

MONOCLE RUNTIME ENVIRONMENT

VERSION = 0.0.6
OS/ARCH = linux/x64
PROCESS = monocle-gateway (PID=1742)
TIMESTAMP = 2023-12-30T05:03:24.068Z

---

MONOCLE GATEWAY SERVICE (Version: 0.0.6)

[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=1752)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
[Monocle Connected]
[RTSP Server Registered]

---

MONOCLE RTSP SERVICE - INITIALIZED

FQDN = d86e619f-4ae9-44f7-b2b5-bacb511deb08.mproxy.io
HOST = 192.168.137.13
PORT = 443

---

INITIALIZE RTSP STREAM: Front Driveway

• NAME : Front Driveway
• CAMERA.MFG : Unifi
• CAMERA.MODEL : G4 Pro
• CAMERA.LABEL : PRIMARY
• RTSP.URL : rtsp://192.168.138.20:7447/r2xnf5Wqcai5VZJc
• STREAM.ID : STREAM:73e7328b-d422-4af2-af3f-42f93c20c17a
• SESSION.ID : f5223687-3f6b-4dce-9983-077c0dc773fd
• LAST.MODIFIED : Fri Dec 29 2023 19:31:36 GMT-0500 (Eastern Standard Time)
• TAGS : @tunnel

---

ATTENTION -> Next you should see log statements showing your camera
establishing an inbound connection to this gateway instance via:
-> DNS URL: rtsp://d86e619f-4ae9-44f7-b2b5-bacb511deb08.mproxy.io:443/STREAM:73e7328b-d422-4af2-af3f-42f93c20c17a
-> This DNS host address should resolve to: 192.168.137.13:443 on your network.

NOTE: If you don’t receive any inbound connection log statements,
please see: https://monoclecam.com/monocle-gateway-troubleshooting

2023-12-30T05:03:35.586Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP CLIENT SOCKET CONNECTED

---

INBOUND RTSP CONNECTION FROM ALEXA: [192.168.139.140:57578 <3ia65tzyj>]

• CLIENT.IP : 192.168.139.140 ( <-- this should be your Alexa device)
• CLIENT.PORT : 57578
• REQ.ID : 3ia65tzyj
• REQ.PROTOCOL : RTSP/1.0
• REQ.METHOD : DESCRIBE
• REQ.URL : rtsp://d86e619f-4ae9-44f7-b2b5-bacb511deb08.mproxy.io:443/STREAM:73e7328b-d422-4af2-af3f-42f93c20c17a?session=f5223687-3f6b-4dce-9983-077c0dc773fd
• STREAM.ID : STREAM:73e7328b-d422-4af2-af3f-42f93c20c17a
• SESSION.ID : f5223687-3f6b-4dce-9983-077c0dc773fd

---

2023-12-30T05:03:35.716Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP CLIENT ATTACHED TO STREAM: Front Driveway (STREAM:73e7328b-d422-4af2-af3f-42f93c20c17a)
2023-12-30T05:03:35.718Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP ENDPOINT SOCKET CONNECTING TO: {192.168.138.20:7447}
2023-12-30T05:03:35.719Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP ENDPOINT SOCKET CONNECTED {192.168.138.20:7447}
2023-12-30T05:03:35.720Z [DEBUG] [192.168.139.140:57578 <3ia65tzyj>] [CLIENT REQUEST] --> [DESCRIBE] rtsp://d86e619f-4ae9-44f7-b2b5-bacb511deb08.mproxy.io:443/STREAM:73e7328b-d422-4af2-af3f-42f93c20c17a?session=f5223687-3f6b-4dce-9983-077c0dc773fd
2023-12-30T05:03:35.721Z [TRACE] [192.168.139.140:57578 <3ia65tzyj>] [CLIENT REQUEST] --> [HEADERS] {
“accept”: “application/sdp”,
“user-agent”: “Fire OS/7.0 stagefright/1.2 (Linux;Android 9)”,
“cseq”: “1”
}
2023-12-30T05:03:35.721Z [DEBUG] [192.168.139.140:57578 <3ia65tzyj>] [ENDPOINT REQUEST] --> [DESCRIBE] rtsp://192.168.138.20:7447/r2xnf5Wqcai5VZJc
2023-12-30T05:03:35.722Z [TRACE] [192.168.139.140:57578 <3ia65tzyj>] [ENDPOINT REQUEST] --> [HEADERS] {
“accept”: “application/sdp”,
“user-agent”: “Fire OS/7.0 stagefright/1.2 (Linux;Android 9)”,
“cseq”: “1”
}
2023-12-30T05:03:35.723Z [DEBUG] [192.168.139.140:57578 <3ia65tzyj>] [ENDPOINT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2023-12-30T05:03:35.723Z [TRACE] [192.168.139.140:57578 <3ia65tzyj>] [ENDPOINT RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“cache-control”: “no-store”,
“content-base”: “rtsp://192.168.138.20:7447/r2xnf5Wqcai5VZJc/”,
“content-length”: “674”,
“content-type”: “application/sdp”,
“date”: “Sat, 30 Dec 2023 05:03:35 UTC”,
“expires”: “Sat, 30 Dec 2023 05:03:35 UTC”,
“pragma”: “no-cache”,
“server”: “Unifi Protect (www.ui.com)”
}
2023-12-30T05:03:35.723Z [TRACE] [192.168.139.140:57578 <3ia65tzyj>] [ENDPOINT RESPONSE] <-- [BODY]
v=0
o=- 1200 0 IN IP4 192.168.138.20
s=68D79AE2A826_1
u=www.ui.com
e=info@ui.com
c=IN IP4 192.168.138.20
t=0 0
a=recvonly
a=control:*
a=range:npt=now-
m=audio 0 RTP/AVP 96
a=recvonly
a=rtpmap:96 mpeg4-generic/48000/1
a=control:trackID=0
a=fmtp:96 streamtype=5; profile-level-id=15; mode=AAC-hbr; config=1188; SizeLength=13; IndexLength=3; IndexDeltaLength=3;
m=audio 0 RTP/AVP 96
a=recvonly
a=rtpmap:96 opus/48000/2
a=control:trackID=1
a=fmtp:96
m=video 0 RTP/AVP 97
a=recvonly
a=control:trackID=2
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=4d401f; packetization-mode=1; sprop-parameter-sets=Z01AH42NQCgC3/gLcBAQFAAAD6AAAu4CdoIhGoA=,aO44gA==

2023-12-30T05:03:35.723Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP ENDPOINT AUTHENTICATION SUCCESSFUL: NONE
2023-12-30T05:03:35.728Z [DEBUG] [192.168.139.140:57578 <3ia65tzyj>] [CLIENT RESPONSE] <-- [200 (OK)] <cseq=1> (session=undefined)
2023-12-30T05:03:35.728Z [TRACE] [192.168.139.140:57578 <3ia65tzyj>] [CLIENT RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“cache-control”: “no-store”,
“content-base”: “rtsp://192.168.138.20:7447/r2xnf5Wqcai5VZJc/”,
“content-length”: “659”,
“content-type”: “application/sdp”,
“date”: “Sat, 30 Dec 2023 05:03:35 UTC”,
“expires”: “Sat, 30 Dec 2023 05:03:35 UTC”,
“pragma”: “no-cache”,
“server”: “Unifi Protect (www.ui.com)”
}
2023-12-30T05:03:35.729Z [TRACE] [192.168.139.140:57578 <3ia65tzyj>] [CLIENT RESPONSE] <-- [BODY]
v=0
o=- 1200 0 IN IP4 192.168.138.20
s=68D79AE2A826_1
u=www.ui.com
c=IN IP4 192.168.138.20
t=0 0
a=control:*
a=recvonly
a=range:npt=now-
m=audio 0 RTP/AVP 96
a=rtpmap:96 mpeg4-generic/48000/1
a=fmtp:96 streamtype=5; profile-level-id=15; mode=AAC-hbr; config=1188; SizeLength=13; IndexLength=3; IndexDeltaLength=3;
a=control:trackID=0
a=recvonly
m=audio 0 RTP/AVP 96
a=rtpmap:96 opus/48000/2
a=control:trackID=1
a=recvonly
a=fmtp:96
m=video 0 RTP/AVP 97
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=4d401f; packetization-mode=1; sprop-parameter-sets=Z01AH42NQCgC3/gLcBAQFAAAD6AAAu4CdoIhGoA=,aO44gA==
a=control:trackID=2
a=recvonly

2023-12-30T05:03:35.736Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP CLIENT SOCKET CLOSED
2023-12-30T05:03:35.736Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP CLIENT DETACHED FROM STREAM: Front Driveway (STREAM:73e7328b-d422-4af2-af3f-42f93c20c17a)
2023-12-30T05:03:35.736Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP ENDPOINT SOCKET CLOSED [192.168.139.140:57578 <3ia65tzyj>]
2023-12-30T05:03:35.736Z [INFO] [192.168.139.140:57578 <3ia65tzyj>] RTSP ENDPOINT SOCKET CLOSED {192.168.138.20:7447}

[Toto]

Hi
you tagged only @tunnel, you must tag @fixaudio too…

BR
Toto

[RS]

@cincyitguy

Hi

I thought that Monocle auto identified Ubiquiti Cameras and applied the @fixaudio, but I think they need to be set as “Ubiquiti” in the monocle gateway portal. I may have got this wrong so as mentioned it’s worth putting the @fixaudio tag also.

I don’t have any G4 cameras but I also seem to remember others having issues with the 4k stream and Monocle and had to enable a lower resolution stream also (1080p?) which Monocle attached to so this would be worth a shot to if you are currently using the 4k stream.

[RS]

@cincyitguy

Sorry found the thread, it’s actually the other way around, the medium resolution stream is not working, but high and low are:-

@RS,
In my case, similar to what you experienced … using a G4 Pro, the Medium (1280x720) resolution does not seem to be working. However the “High (3840x2160)” and “Low (640x360)” stream are working with Alexa.

Not really sure what going wrong with this one. I’ll dig deeper as I have time but at least we have a workaround for now.

Thanks, Robert

[cincyitguy]

@Toto @RS thank you for the responses/suggestions.

Turns out it was the @fixaudio tag that fixed this issue. Fired right up.

FYI, all three resolutions work as well so not sure there is still an issue with mid level on Ubiquiti but it’s working fine for me.

There is one outstanding issue. The Show 5, gen 3 devices do not display any camera feeds. No issues on the Show 8, gen 2 and gen 3 devices. It appears to be a different type of issue b/c I get no output on the monocle gateway when attempting to establish the RTP stream so not much to go on. Just curious if there are any known issues with the latest version on Monocle and the Show 5, gen 3 devices. I have tried the lowest resolution possible for the RTP steam as well (640 x 360) but that didn’t fix the issue. Thx!

[RS]

@cincyitguy

That’s good news!

With the G3 cameras on the show 5 when you say you get no output, do you see the request coming into monocle gateway at all?

If not it might be a DNS issue, I think there may have been some device that hard code the DNS servers despite being on DHCP, there is a way to manually set dns server on Show devices, sorry I can’t remember how but a google should turn it up.

[RS]

@cincyitguy

Basically if the request is not hitting the gateway the show device is not resolving the mproxy.io address correctly.

[cincyitguy]

@RS this seems logical to me. Yes, on the monocle gateway, I see absolutely no output when the Show 5 devices are asked to connect to a camera.

I found an article that talks about how to update DNS on Show devices - basically delete your wireless network, rejoin but used advanced options to hard code DNS server. I’ll give that a try I suppose. Just odd that the Show 8 devices work fine but the Show 5 are not.

Appreciate the help!

[cincyitguy]

Unfortunately, going through the wireless setup process again and specifying a different DNS did not solve the problem. Odd - I wonder what the differences in architecture/code between the Show5 and Show 8 would cause this difference. Any other suggestions anyone?

[m1k3allan]

@cincyitguy @toto was kind enough to point me at this post. Just to completely agree I cannot get this to work either. Like you certain the streams are there and there are no network issues but the same dreaded cannot connect to the camera…so no help but at least you know your not alone.