Fire TV Stick 4K [SOLVED]
-
@cmjanus said in Fire TV Stick 4K:
Glad to hear everyone is getting their cameras working. I do have about a 10 second lag. Any ideas how to Make it stream quicker? Thanks.
See my comment in this thread:
https://forum.monoclecam.com/topic/121/10-second-delay -
Hi… New here… So I got all of my cameras setup and everything works internally but this Alexa psycho keeps saying hmm… The camera isnt responding. I have tried with and without the gateway I am racking my brain here. HELP!
I have followed all of the directions and instructions in this thread as well on the website. I dont know what I am doing wrong. I have the following…
Amazon Firestick 4k…
IP8M-2496EBThey are all PoE they work fine with VLC and my Amcrest NVR. I really wanna be lazy and tell Alexa to show the camera on my TV’s… HELP PLEASE!
Brian
-
Also does this mean anything?
INITIALIZE RTSP STREAM: Porch
- NAME : Porch
- LABEL : PRIMARY
- URL : rtsp://192.168.3.39:554/cam/realmonitor?channel=1&subtype=0
- UUID : STREAM:8d8a51ca-bac7-4b72-9f04-7e9b23903711
- SESS : 93ace2f7-174a-4ad7-88c0-99f5a168c61e
- MODIF : Sat Apr 06 2019 22:32:50 GMT-0400 (Eastern Daylight Time)
- TAGS : @tunnel
RTSP STREAM MODIFIED: Porch
Any existing RTSP steams will be shut down
and a new stream instance will be registered.2019-04-07T02:33:05.532Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [DEREGISTER] rtsp://192.168.3.39:554/cam/realmonitor?channel=1&subtype=0
2019-04-07T02:33:05.532Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] {
“cseq”: “1”,
“transport”: “reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suffix=STREAM:8d8a51ca-bac7-4b72-9f04-7e9b23903711”
}
2019-04-07T02:33:05.534Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [451 (Invalid parameter)] <cseq=1> (session=undefined)
2019-04-07T02:33:05.534Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“date”: “Sun, Apr 07 2019 02:33:05 GMT”
} -
I am using this same camera with no issues. You must use the Monocle Gateway when using the FireTV 4K Stick. So don’t bother testing without it, it definitely won’t work without it.
Here is what my camera settings look like:
Also, on the camera’s own web configuration pages, make sure you have configured the stream to use H.264. I can’t remember, but this camera may ship using H.265 by default.
The log info you attached is suggesting that at one point you were using the “@proxy” tag and then made a change to the camera settings via the Monocle Gateway. The 451 error is suggesting that there is something wrong – but lets try using “@tunnel” instead since we know that is working for this camera.
Thanks, Robert
-
@Monocle thanks for the info. I have all of that in place. Question though. I see you are using a sub stream. Were you able to set the cameras sub stream to 1080P? Mine will not allow me to change from 640x480 when I click the drop down in the camera’s video settings.
Brian
-
Yes, I was able to use the primary stream as well. (I typically have it set to use the primary stream, but I must have switched this to the secondary stream during some testing.)
Try to capture the log from Monocle Gateway as you ask Alexa to show the camera stream. You should see “INITIALIZE RTSP STREAM: Porch” messages immediately followed by log info about the Alexa device connecting to the RTSP server of the gateway. If you don’t see any inbound RTSP connections after the “INITIALIZE RTSP STREAM: Porch” then it could be an issue related to network access of the Monocle Gateway. Similar issue reported on this thread: https://forum.monoclecam.com/topic/153/reolink-camera-wont-show-on-alexa-tv/3
Thanks, Robert
-
Thanks I will look at this. Also here is the debug… This shows then that psycho says hmm… camera isnt responding…
INITIALIZE RTSP STREAM: Porch
- NAME : Porch
- LABEL : PRIMARY
- URL : rtsp://192.168.3.39:554/cam/realmonitor?channel=1&subtype=1
- UUID : STREAM:8d8a51ca-bac7-4b72-9f04-7e9b23903711
- SESS : cfc9769a-1983-4fe4-8a72-535270e7206e
- MODIF : Mon Apr 08 2019 08:51:48 GMT-0400 (Eastern Daylight Time)
- TAGS : @tunnel
RTSP STREAM MODIFIED: Porch
Any existing RTSP steams will be shut down
and a new stream instance will be registered.2019-04-08T13:08:30.264Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [DEREGISTER] rtsp://192.168.3.39:554/cam/realmonitor?channel=1&subtype=1
2019-04-08T13:08:30.264Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] {
“cseq”: “1”,
“transport”: “reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suffix=STREAM:8d8a51ca-bac7-4b72-9f04-7e9b23903711”
}
2019-04-08T13:08:30.265Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [451 (Invalid parameter)] <cseq=1> (session=undefined)
2019-04-08T13:08:30.265Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“date”: “Mon, Apr 08 2019 13:08:30 GMT”
}
INITIALIZE RTSP STREAM: Porch
- NAME : Porch
- LABEL : PRIMARY
- URL : rtsp://192.168.3.39:554/cam/realmonitor?channel=1&subtype=1
- UUID : STREAM:8d8a51ca-bac7-4b72-9f04-7e9b23903711
- SESS : 93aed62f-9123-4655-a9cb-33a19f0a60f7
- MODIF : Mon Apr 08 2019 08:51:48 GMT-0400 (Eastern Daylight Time)
- TAGS : @tunnel
INITIALIZE RTSP STREAM: Porch
- NAME : Porch
- LABEL : PRIMARY
- URL : rtsp://192.168.3.39:554/cam/realmonitor?channel=1&subtype=1
- UUID : STREAM:8d8a51ca-bac7-4b72-9f04-7e9b23903711
- SESS : 9e2df77b-ddd3-42b8-956d-a1553a08444c
- MODIF : Mon Apr 08 2019 08:51:48 GMT-0400 (Eastern Daylight Time)
- TAGS : @tunnel
-
@Monocle hey were good. So turns out pfSense’s DNS server sucks… It was having issues resolving your hostname. I changed it to google’s DNS and its working perfectly.
-
It may be that PFSense has DNS REBINDING protection enabled by default.
I had to add a special exclusion in my PFSense router to allow the domain*.mproxy.ioto work.See: https://monoclecam.com/monocle-gateway/troubleshooting/dns-rebinding
In PFSense under :: Services > DNS Forwarder, I added this custom config option:
-
Good deal. I have been in IT for over 20 years and have never heard of this. Ive never experienced it in my career. If you ever need any help with the project let me know. I have extensive knowledge of AWS and programming in general. I would be happy to help.
brian
