@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…
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.
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.
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
@chunsanger did you ever get to the bottom of this? It appears reading the logs that the communication via Port 443 is not actually how the echo communicates with gateway. The port seems to change after every use. As a stop gap I’ve allowed the IP address’s of the echo access to the IP of the gateway, but that’s less than ideal!