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
Category to discuss other camera manufacturers/models not otherwise listed.
Please see this thread.
Some users have has success using certain special tags. I have the older Uniden DB1 version of this camera and I have not had any success.
@travisb1 In general, the Amcrest cameras and NVRs work well with Alexa. The Monocle Gateway is required for some Alexa devices; it may not be for all.
1920x1080 is known to work. Higher resolutions may not work; I haven’t tried.
For Axis cameras, past users have reported similar issues. In those cases most often it was related to an audio stream. Please take a look at the tips on this page to try and resolve the audio channel issues:
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)
@nofuse1 said in Hikvision DB1 (WiFi Video Doorbell):
Only thing here not working is the audio. will tinker today with it.
I just purchased a DS-KB6003 as a second camera here. I will give that one a try today. I have it configured inside of the home with a 24VAC transformer. I did have some issues pairing it up with my Ruckus WAP so went to using an older Asus WAP.
BTW which firmware is recommended for use with the DS-KB6003. Here have updated it via the EU portal except that the newest (from 2018) will not work on the camera using the Batch Configuration program.
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
@Monocle … It is a Reolink RNL8-410. I use the string “rtsp://admin:firstname.lastname@example.org:554/h264Preview_02_sub”. This allowed me to stream in VLC, then I changed the resolution in NVR and now it does not. Not sure if maybe a resolution problem. When I ask Alexa she tries and flashes for a bit and says “the camera is not responding”. Kinda frustrated that I had it in VLC then not
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.
@Spider03 Keep in mind I’m using a SV3C camear. And the Gateway is on a Raspberry PI.
The Gateway is running. And when I try to access the camera with my Alexa device I see logging in the Gateway. It shows the camera IP, Alexa IP etc. so it is trying.
So I’m thinking it’s just not gonna work with this brand camera.
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.