@cmjanus

Some users have reported having to change the H.264 profile settings (High, Baseline, etc) or the H.264+ settings to get their Hikvision cameras working.

Here are the setting I am using on a Hikvision DS-2CD2042WD-I. (No Monocle Gateway required for Echo Show or Echo Spot.)

c32c7b86-96a1-475e-8110-1f23fa5a32d1-image.png

@gargary

ISSUE RESOLVED
SEE https://forum.monoclecam.com/topic/132/unable-so-far-to-echo-show-connect-hikvision-nvr/14

@lansa

Won’t show up where? The stream won’t show on your Alexa device or the camera is not available in your Alexa app under smart home devices?

{{ PANEL(warning, ATTENTION): I have posted an update on these requirements and our additional findings about the ECHO SHOW 5 here: http://monoclecam.com/echo-show-5. }}

@leewilko

@mon749 is correct, the Echo Show 5 (similar to the Echo Spot) is limited to streams of 1080P and less. You can adjust the resolution of your camera within the camera’s own settings or use the camera’s secondary stream which is typically a lower resolution feed.

If you primary feed is something like:
rtsp://{ip-address}:554/Streaming/Channels/101
then the secondary feed may be:
rtsp://{ip-address}:554/Streaming/Channels/102

Thanks, Robert

@frysky

Does this Synology NAS support Docker instances? We do have instructions on getting the gateway working on Synology using Docker. It can be a bit complicated, but it does work.

Buying a Raspberry Pi or similar device can also work if you find the service useful.

Here is the older model 3B which works fine:
https://amzn.to/2OzhALU

or the 3B+
https://amzn.to/2DyHfxW

or the latest version 4B:
https://amzn.to/2P34t4D

You can probably get it cheaper if you have some of the parts like power supplies and microSD cards and don’t have to buy a full kit.

Thanks, Robert

Thank you. Just started trying tags but saw that doesn’t help. The configuration on my spot is just using the RTSP per monocle directions. Works on the spot. Not on the 8. Not happy. Wanted the 8 for bigger view like the spot. Thought it would work the same. No such luck.

@chrisb306 check any firewalls and disable to test, see my post as got another hik working now with gateway.
Also ensure substream is set to lowest res.

Hi - I had the same problem.

The show 8 can show a max of 1080p and only works with H264 codec (not H264+ or H265 codec)

when I set up the third stream to H264 and 1280x720p and set up the monocle tag with @tunnel it worked perfectly.

I have set up the main stream to 4K so the synology surveillance station can record that - but I point the show 8 to the third-stream and it works great. (I have not used the “sub-stream” as it has a max resolution of 640x480)

Im no techie so forgive the general statements - hope they help.

Yes it’s the matrix view.

I’ll check… Not 100% sure.

@Danilo
Ho lo stesso problema, sei riuscito a risolvere in qualche modo ? Grazie, ciao. Marco
I have the same problem, did you manage to solve in any way? Thanks bye. Marco

Hi Robert,

Thanks for your replies.

The following rtsp address works on VLC and shows the 4 cameras for my Channel Zero feed. .57 is the IP of my NVR on my LAN.
rtsp://192.168.1.57:554/Streaming/Channels/001/

According to VLC my Channel Zero feed is H264. VLC codec info tab shows:-
Stream 0
Type: Video
Codec: H264 - MPEG-4 AVC (part 10) (h264)
Resolution: 704x578
Decoded format: Planar 4:2:0 YUV

I tried to use the @fake-fmtp parameter as a Monocle tag in the settings but Alexa says “Hmm, the camera isnt respodning”.

For additional info, I know Monocle on my Echo show can access my camera feeds in two different ways:-

By accessing each of my cameras directly on my LAN. By connecting to my Hikvision NVR then showing the camera feed via that IP (.57).

For example, the local IP for my front camera is:-
rtsp://192.168.1.101:554/Streaming/Channels/101/
101 is the camera IP address and /101 is ch1 feed 1 (its a coincidence they are both “101”.

The IP for my NVR is .57 and my front camera os No 1 (101)
rtsp://192.168.1.57:554/Streaming/Channels/101/

Both of these addresses work in VLC and both work in Monocle.

So I know Monocle can access all 4 cams either directly or via my NVR. This is why I think it should be possible to view my channel zero feed by connecting to my NVR on rtsp://192.168.1**.57**:554/Streaming/Channels/001/
The 001 being channel zero feed 1 (primary feed).

Robert, you mentioned getting captures of the Monocle Gateway log file and inspecting that to see where Alexa seems to be failing on the stream.

How can I provide you with the Monocle Gateway log file?

Thank you very much for your help, I much appreciate it!! :-)

@Paulcf007

In your log, we are missing any TCP/RTSP connection attempts from the Alexa device after an “INITIALIZE” camera request. This is almost always a networking related issue. It could be a firewall blocking inbound connections on port 443 on the machine running the Monocle Gateway. Make sure your Alexa devices and Monocle Gateway are on the same network and not on a GUEST or isolated VLAN where they can’t communicate.

The most likely issue is DNS REBINDING. This is where your router won’t allow the DNS entry bd93ddd2-0d85-49bd-9e35-96753575xxxx.mproxy.io resolve back to your gateway instance at 192.168.1.3. Some routers block this to prevent attacks, but in this case, the Alexa devices must connect to a DNS hostname and we want to resolve to the Monocle Gateway running inside your network so that all your camera streaming data is kept private and local to your network and not streamed over the Internet.

Thanks, Robert

I can create the rtsp feed via vlc but when i add it to monocle and try viewing via echo show 8 i just get " im not quite sure what went wrong " frustrating