Fire TV Stick 4K [SOLVED]
-
@vmsman if I disable ONVIF I can only see the stream in vlc by the up address only. What do you mean define it explicitly in Monocle? Do you know how to turn off the stream encryption? This is the rtsp url I’m using with digest and @tunnel.
rtsp://10.0.1.xxx:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1Do I need to do anything with ports? Thanks for the help.
-
@vmsman said in Fire TV Stick 4K:
rtsp://admin:[email protected]:554/Streaming/Channels/101/
Try defining it like this without @tunnel and then with @tunnel if that does not work>
-
@vmsman I already tried that and it didn’t work. Any other ideas. Thanks.
-
@cmjanus Do you get any errors? Are you trying to display on an Echo Show or a Fire TV?
-
@vmsman On a firetv (non 4K). I ask to see camera, the home screen changes and says waiting for camera… and after a about 15 seconds reverts to the home screen again. Nothing happens and no errors on fire tv
-
@cmjanus What is the difference in behavior with @tunnel and without @tunnel for this camera when you “show on the Fire TV”?
-
@vmsman absolutely nothing on fire tv same thing for both
-
@cmjanus and yet other cameras are working through Monocle, but not this one?
-
@vmsman I have three hikvision and three trendnet cameras older 2015ish work with no gateway. A D link that I have since took down but needed to Gateway. I was also having problems with a reo link But return it thinking the hikvision would work. But the new one doesn’t.
-
@cmjanus I have three reolink cameras and one GW Security camera. They are all configured thru the gateway and work on echo show and fire tv 4k for me.
-
@vmsman I see on the gateway the IP of 10.0.1.70. That is not the computer IP nor the camera. I see the camera has IP filtering to allow or block. Wondering if I allow it to the specific addresses? Did u need to do anything to the router for ports?
-
The Monocle Gateway on startup will auto-detect the IP address of the host machine its running on. However it can get this wrong on some computers that may have more complex networking configs.
On startup, you should see something like this:
------------------------------------------------- MONOCLE RTSP SERVICE - INITIALIZED ------------------------------------------------- FQDN = f065fdn6-2e66-433d-axa8-6g3aau7132aae.mproxy.io HOST = 10.1.1.56 PORT = 443 -------------------------------------------------If that IP address is wrong, then the Monocle Gateway won’t work. The FQDN is also a DNS entry that points to this IP, if that is resolving incorrectly or to the wrong IP address, then the Monocle Gateway won’t work.
Please see this post for details on how to override the auto-detection settings:
https://forum.monoclecam.com/topic/99/monocle-gateway-custom-propertiesThanks, Robert
-
@vmsman said in Fire TV Stick 4K:
@cmjanus What is the difference in behavior with @tunnel and without @tunnel for this camera when you “show on the Fire TV”?
Technically speaking the
@tunneltag handles the stream between the IP camera and Alexa devices in a lightweight network tunneling approach where the stream is mostly just passed thru unmodified between the Alexa device and IP camera.@proxyon the other hand uses the Live555 RTSP proxy server under the hood to actually proxy the camera stream. Proxying the stream helps some incompatible cameras get past some of the Alexa issues and allows them to work. Especially cameras that may only support UDP connectivity and not TCP interleaved communication which Alexa devices require. By default,@proxyuses UDP connectivity to the camera’s streaming.As for the FireTV, that really does not matter – the Monocle Gateway handles the Amazon security requirements before the RTSP layer is ever handed off to the
@tunnelor@proxyimplementation.We typically suggest using
@tunnelfirst since its lighter-weight and only use@proxyif that’s the only option your camera will work with. -
This post is deleted! -
@cmjanus said in Fire TV Stick 4K:
rtsp://10.0.1.113:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1
Based on the log, the Monocle Gateway looks like its working correctly.
Try changing
rtsp://10.0.1.113:554/Streaming/Channels/101?transportmode=unicast&profile=Profile_1to
rtsp://10.0.1.113:554/Streaming/Channels/101You don’t want to specify the transport mode, you want to allow the RTSP layer to determine the appropriate transport and protocol to use.
No, you do not need to open up any ports thru your firewall to the Internet.
Post 443 must be accessible to the Alexa devices on your network, but based on the log data, that is working. -
@Monocle i already tried changing it to 101 and no go.
-
@cmjanus ,
Have you tried changing the various H.264 Profiles (High, Standard, Baseline) and/or tried changing H.264+ plus settings? Some users have reported needing to change these to get some Hikvision cameras working.
Monocle: https://monoclecam.com
Getting Started | Troubleshooting Guide | FAQ | Contact Support -
Based on the log, the Alexa device is fully negotiating the RTSP layer and the stream starts playing from the camera but the Alexa device immediately disconnects after the stream is started. This suggests there is something about the stream itself that the Alexa device does not like.
-
@cmjanus If you are still broken, we can voice call if interested. I am on CST and you?
-
@Monocle changed the stream and still not working.
