ATTENTION The equipment listed on this forum are for discussion and general information and do not represent a definitive listing of supported hardware. Additional information can be found here: https://monoclecam.com/supported
i use the monocle gateway for Grandstream GX3500-Encoder und a Reolink MP420 5MP . But now i got Problems with a Hosafe Dome Cam 1080P using the Sub-Stream with resolution 640x352 and no audio.
The Echo 5, Echo 8 and also the fireTV is closing the connection after receiving the SDP-Setup.
I can see this in my log-file.
SDP-Setup see below, could you give me any information what’s the reason for hanging up ?
What part of the SDP was not liked by the Echo’s ?
Thank you in advance
RTSP/1.0 200 OK«
CSeq: 2 «
Server: Hipcam RealServer/V1.0«
o=- 38990265062388 38990265062388 IN IP4 192.168.1.178«
c=IN IP4 0.0.0.0«
m=video 0 RTP/AVP 96«
Hmm… it only works for the P3245-LVE if I switch to Basic Authentication, the default of the camera (DIGEST) does not work with the Monocle app.
Which means I can’t use the camera in my recording system anymore (Axis Camera Station)…
Tried it with an M1145-L, which only has Basic Authentication, works fine with that camera.
Let’s see if I can motivate the Monocle developers to investigate…
Hi Robert … mystery of the password solved.
In fact the password was blank (null).
Why onvif said it was ‘tlJwpbo6’ I have no idea or why it worked with that.
I reset password to ‘admin’ and used that and all is well (without the gateway and without the audio)
LOREX 16-Channel 4K PoE 2TB NVR (NR9163)
This NVR series (NR900) has been confirmed to work with Monocle and Alexa.
Buy LOREX NR9163 on Amazon
4K Resolution (3840×2160)
16 Port 10/100 Ethernet Switch with PoE
3 TB Hard Drive (expandable up to 13TB)
30 fps recording rate @ 4K (8MP)
H.264 & H.265 Encoding Support
Camera TCP/IP address on your local network
Camera’s RTSP port (default: 554)
Camera channel (1=channel 1; 2=channel 2; 3=channel 3; …)
Camera stream (0=main-stream; 1-sub-stream)
This NVR has been confirmed to work without the Monocle Gateway service for certain Alexa devices. Please see: Supported Alexa Devices and the configuration notes below.
LHV/LNR Series NVR login password for the RTSP stream can only be six digits or characters in length.
If your password is more than 6 characters try entering the first six digits of your password when logging in or change your password to limit it to a maximum of 6 characters. (https://help.lorextechnology.com/link/portal/57356/57366/Article/1400/Error-Message-Password-Error)
Attached cameras must be configured to use the H.264 video codec. Alexa devices do not support H.265 or MJPEG and thus users must configure the stream to use H.264 to be compatible with Alexa device.
If an attached camera supports audio and the audio channel is DISABLED in the NVR camera configuration the Alexa devices will not play the stream, but rather a constant buffering message on screen.
If an attached camera supports audio and the audio channel is ENABLED in the NVR camera configuration the Alexa devices will play the stream; however certain Alexa devices such as the FireTV devices may incur some extreme latency and constant re-buffering messages on the Alexa devices. You can use the Monocle Gateway and tag your camera stream with the @noaudio tag to remove the audio channel from the stream to help improve the stream latency.
Quick Connection Guide
Quick Networking Guide
Did you manage to figure this out? It does seem very odd to work in VLC and then fail to work in VLC after changing the camera’s resolution. Some ReoLinks are now shipping using the H.265 video codec by default. You may want to check that and make sure you are using the H.264 video codec.
Just got my Echo Show 8, and already had a Swann DVR8-4980. I had some success after many trials, so I thought it may help others to briefly describe.
I couldn’t get a direct connection to work at all, so I have installed Monocle Gateway to a Raspberry Pi (a version 2 model B Rev 1.1). Aside: In doing so I found that it was still on Raspbian Wheezy, which being well out of date was lacking quite a few necessaries, so I had to burn an image of Raspbian Buster to get the Monocle Gateway install to work for me.
I tried the Tunnel tag first, but couldn’t get that to work.
With the Proxy tag, I have the substreams working ok at 704x480. This is as high as the DVR will set the substream.
I haven’t yet managed to get a mainstream working; I’ve set the DVR mainstream to 1920x1080 (lower resolution than my cameras), and can’t get the Echo Show to show it. Mainstream works fine in VLC.
For this Swann device, the RTSP urls are:
Where N is 1 to 8 for the camera number, and M is 0 for the mainstream or 1 for the substream
I noted that the Echo Show was disconnecting after the client response for the describe, and the significant difference appeared to be the profile-level-id.
Modifying the mainstream compression level and bit rate on the DVR did not change the profile-level-id. So I added the fakefmtp tag for the mainstream. This overrides the profile-level-id with 420029.
This now has the mainstream working at fullHD.
Hi there! I am using a mix of SV3C SV-B01 & SV3C SV-D02POE. I am unable to make it work , with and without the gateway. I have tried the @noaudio tag since those cams have no audio, along with the others tags: @proxy, @tunnel, etc… No luck.
I got some unifi cams running, the rtsp stream looks good, gateway installed. skill enabled but the cam wont load on the fire tv. I’m not sure. I tried all tags… I did get it to work using a vlc player thats why I can say the stream is working.
The wansview cameras do not work with the Echo Show 8 no matter what you install, tag or do. It’s a shame as I can see the log entries when I attempt the make the connection so I know it is close. But it does not display the video. Works in VLC and everywhere else.