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
Sadly, I’m unable to find hardly anything about this topic,
therefore I feel compelled to adress this here.
(please correct me if I’m just uncapable of using the search feature)
I was trying to get the following to work:
Raspberry Pi + Rasperry Pi Camera
Monocle Gateway on same Pi
-> streaming via raspivif-> cVLC -> RTSP / H264 ->-> Monocle Gateway ->-> Echo device
Thus far I was able to get to the point of the gateway being able to connect all sides - yet,sadly, the Echo is not able to show any video.
(VLC hasslefree does!)
If anyone has any infos on this, please contribute.Thanks!
I have the same camera and can’t get it work.
I can get the rtsp work on VLC, using this guide https://support.amcrest.com/hc/en-us/articles/206813947-RTSP-Stream-URLs-for-HD-CVI-DVRs-1080P-HD-CVI-
But I can’t get it work on my alexa using the monocle skill. I haven’t tried Monocle Gateway.
Have you solved this?
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…
I have three dahua K35 cam and i wish to see them onto an echo show 8 second gen. i’ve tried a lot of configuration but i have always the same answer “the camera is not responding”. i’ve tried with the rtsp address only, with rtsp and @tunnel, and @proxy… butit won’t work. someone can help me?
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)
Bought this off of Amazon as I wanted Home Assistant / Zoneminder support - both we have working. Now need to be able to view this on the Echo Show 5 that we have in the living room. Came across this application which seemed to be the most promising. Have it installed along with gateway running on Ubuntu 18.04. The gateway received the command just fine and is not having issues with DNS rebinding per the test.
The settings I have for the camera in the configuration are
resolution: 1920*1080 (16:9) [FHD] <1080P>
video codec: H264
audio codec: NONE. (also tried G711, per VLC report)
Have tried what I would believe is EVERY combination of @tunnel / @proxy, BASIC / DIGEST along with the @fakefmtp, @noaudio and @fixaudio tags. Have not bee able to get this to display at all on the Show.
Have it working just fine in Zoneminder / VLC with the following URI:
The hardware is running firmware V1.4.62 build 171219, encoding version V1.0 build 170623. This is really the last piece to having this doorbell fully automated in our home network. Willing to provide any sort of needed access, packet capturing and/or logging to assist…
Hoping we can get this to work and thanks for this much needed integration product for Alexa!
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
@vijaypatil Not a monocle guy, but one thing I noticed is that you have @proxy tag but no @tunnel tag. As far as I understand it, you should tag the camera as @tunnel on the web app. (And remove @proxy)
Also, I think it seems as though the skill may be abandoned. Loads of unanswered questions withing the past year. It is unfortunate as it could be a fantastic skill.
It would also help to post a log of your output when attempting to connect.
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.
After much trial & error, I got 2 of them working as follows:
Set camera to 1080P, H264, disabled audio (didn’t try with it on)
Added cameras to Monocle:
video/audio same as camera settings
tags: @proxy, @hangup
Installed Monocle Gateway on Win10 PC (also runs Blue Iris with these cams) following step-by-step instructions
There is some occasional flakiness getting connected, but @hangup seems to have solved most of it.
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.