@Spider03 It has bitten me before…

@cory_booth

Thanks for the guide and here is the link for future readers:

@chadducote I don’t know if support is monitoring this forum but it would be nice. I would like to use Monocle but since I can’t find out if they support the latest Firecube 4K (available from Amazon April 2020) I guess this product is not going to be mainstream. I don’t want to buy an old generation of a product just to use this service. Duh…

IS ANYBODY HOME?

@dotcommer

Apologies for the delay. Thanks for posting the pictures illustrating this issue. There have been a couple of users point this out and I have experienced it myself on my FireTVs – it seems that we inherited this behavior in some FireTV update because I don’t remember this originally. To my knowledge this is no way to disable this behavior. We don’t touch the video stream data in any way so this is entirely the FireTV device adding this border. It is annoying and I hope they make it go away in some future update.

Thanks, Robert

Hi, did you get this working? I have the same issue

If you have port forwards for each remote cam at the public IP address, you should be able to do this via RTSP links to that IP with appropriate port for each camera. Verify/Troubleshoot the links with VLC or such first to keep your sanity.

@garethb Just Rebooted and all working!

@andacious said in Echo Show 8 "Hmmm Camera not responding":

Ensure port 443 is open on the Pi to other machines on your network
Ensure you are using the @tunnel tag on each of your cameras
Ensure you are using the 1080p RTSP (not RTSPS) stream from UniFi Protect for each separate camera
Ensure that the gateway service is running, even after the Pi restarts
If the camera/gateway/pi are on separate VLANs, ensure that they are allowed to communicate across VLANs.
Verify (using VLC or something) that the RTSP stream is accessible on your network

Thanks for the reply,
Sorry for the ignorance below on not know how to do certain things below due to learning.

1: not quite sure how to ensure 443 is open
2:I do have the @tunnel tag for the camera
3: I did ensure I’m using the RTSP stream and not the RTSPS stream
4:Gateway service is running and sees when I try and get it to pull up on the echo show.
5: Not sure how to make sure they are allowed to communicate across VLANS. I’m running everything through a Ubiquiti switch.
6: I did verify with a VLC and it worked fine
Thanks

I found this handy from the ubiquiti forums

https://community.ui.com/questions/RTSPS-on-VLC-player-or-what-exactly/ace5d757-75a4-499f-a809-093ceb728203

@Monocle Thank YOU Robert - we really appreciate it.

D

@chunsanger said in Separate VLANs Issue:

I am running into some issues with my Alexa devices (on a dedicated IoT VLAN) communicating to my Monocle Gateway/Unifi Protect cameras.

If I move the Alexa Device (Echo Show 5) to my main LAN then I can connect and view the RTSP stream without issue. But if I am on my dedicated IoT LAN, then I can see the camera listed, but cannot stream.

I have enabled communication on the firewall on port 443 using a LAN IN rule from my Echos to the Monocle Gateway without any luck. I also tried adding a LAN IN rule from my Echos to my Unifi Protect IP and RTSP stream port without luck.

Any suggestions would be appreciated.

I have my UI cams and NVR on my main network, no reason to put them on the IoT Vlan. If I were using some odd ball name IP cams, I would. But I’m trusting all of the UI hardware with my network, so why move the cams?? I have my Alexa stuff on the IoT lan as well as my RPi running monocle. There are some firewall rules to make sure your “admin” (main Vlan network) can talk to all of the Vlans. And then yes open up the port for the monocle on the monocle IP. IIRC, that’s all I did. With all the Alexa stuff on the same IoT network as the monocle PI, makes it a bit easier IIRC.

Did you have any issue getting unifi-os shell to run. I am not able to get this to run once ssh in.