Fire TV Stick 4K [SOLVED]

vmsman

@cmjanus and yet other cameras are working through Monocle, but not this one?

cmjanus

@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.

vmsman

@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.

cmjanus

@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?

Monocle

@cmjanus

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-properties

Thanks, Robert

Monocle

@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 @tunnel tag 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.

@proxy on 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, @proxy uses 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 @tunnel or @proxy implementation.

We typically suggest using @tunnel first since its lighter-weight and only use @proxy if that’s the only option your camera will work with.

cmjanus

This post is deleted!

Monocle

@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_1

to

rtsp://10.0.1.113:554/Streaming/Channels/101

You 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.

cmjanus

@Monocle i already tried changing it to 101 and no go.

Monocle

@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

@Monocle

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.

vmsman

@cmjanus If you are still broken, we can voice call if interested. I am on CST and you?

cmjanus

@Monocle changed the stream and still not working.

vmsman

@cmjanus Do you want to voice call?

cmjanus

@vmsman still not working. Interested in call but can’t tonight. I am est zone. Maybe tomorrow. Thanks.

vmsman

@cmjanus ok. Let me know. My email is [email protected] – Scott

cmjanus

@vmsman @Monocle
I finally got it working!!! And of course it was something really stupid. It was the resolution. It was too high 2688x1520. Not having a 4K Fire stick must of been what was messing it up. I tried stream 2 (640x340) and it worked. I then created a third stream (1280x720) and still works. Also I did not need the Gateway.

I sincerely appreciate all the help and support this forum provides. Thanks!!!

vmsman

@cmjanus Excellent to hear. I just got a new Amcrest IP4M-1051. It’s a pretty good camera but not performing at even partway reasonable resolution through the Monocle Gateway. The native resolution is 2688x1520, however the result on the show is a 4x3 display lacking resolution. I’m scratching my head on that one.

Monocle

@cmjanus

Glad to hear it!

Monocle

@vmsman said in Fire TV Stick 4K:

@cmjanus Excellent to hear. I just got a new Amcrest IP4M-1051. It’s a pretty good camera but not performing at even partway reasonable resolution through the Monocle Gateway. The native resolution is 2688x1520, however the result on the show is a 4x3 display lacking resolution. I’m scratching my head on that one.

I’m running an Amcrest IP4M-1051W here without issues through the Monocle Gateway. I even have the camera on WiFI for the moment — planned to move to ethernet soon. Here are my camera’s settings:

I also have P2P networking disabled. I try to disable P2P on all cameras an my network :-)

And here are the Monocle camera settings:

Thanks, Robert