Unable to Get Doorbell working Nellys NDB313-W
-
I can NOT get this to bridge into Alexa.
This unit I thought was really a Hikvision DB2 - I’m probably wrong.
- I can see this unit in its native app. (Guarding Vision on Android)
- It’s on my local network and playing nicely with my Net Mgmt software (responds to pings etc).
- I can access it via ONVIF Device Manager perfectly. (interesting to play with the resolutions).
- I can access this in Blue Iris (and do - BI 5 is running the camera for me).
- I can access this via any computer in the house hold using VLC - my URL is very straightforward.
Other cameras in my network are showing on Alexa perfectly via Monocle service. (a ptz and a dome).
I loaded the Monocle Gateway on the same server as the Blue Iris Server. I tried adding Tags of @FakeFMTP and @tunnel.
I get interaction with the Gateway CMD window when I tell Alexa to show the Doorbell. just after about 30 seconds it says ‘can’t connect to Doorbell’ coming from the Alexa Show (8").
I’ve tried Both Basic and Digest auth’s. I’ve disabled Audio on the Monocle (I believe this is an AAC audio stream and I read that only g711 is supported on Alexa).Not to jerk tears, but I’m hearing impaired. If I get a delivery I want the camera to be able to show on my Echo Show (I trigger from a motion detector). The Trigger part works great from Hubitat to BlueIris. Everything works but the damn stream!!!
Microsoft Windows [Version 6.3.9600]
© 2013 Microsoft Corporation. All rights reserved.C:\Windows\system32>cd\program files\monocle-gateway
C:\Program Files\monocle-gateway>monocle-gateway
-
__ __ ___ _ _ ___ ___ _ ___ * -
| \/ |/ _ \| \| |/ _ \ / __| | | __| * -
| |\/| | (_) | .` | (_) | (__| |__| _| * -
|_| |_|\___/|_|\_|\___/ \___|____|___| * -
*
MONOCLE RUNTIME ENVIRONMENT
VERSION = 0.0.4
OS/ARCH = win32\x64
PROCESS = monocle-gateway (PID=4392)
TIMESTAMP = 2020-11-05T21:28:37.673Z
MONOCLE GATEWAY SERVICE (Version: 0.0.4)
[Monocle Starting]
[Monocle Connecting]
[Monocle Started]
[RTSP Server Starting]
[RTSP Server Listening] 0.0.0.0:8555 (RTSP)
[RTSP Server Listening] 0.0.0.0:443 (RTSP-TLS)
[RTSP Proxy Started] (PID=3376)
[RTSP Server Listening] 0.0.0.0:8554 (PROXY)
[RTSP Server Started]
[Monocle Connected]
[RTSP Server Registered]
MONOCLE RTSP SERVICE - INITIALIZED
FQDN = c2cd7182-0a7b-4f9f-8c5a-29376c3f33d2.mproxy.io
HOST = 192.168.1.125
PORT = 443
INITIALIZE RTSP STREAM: Doorbell
- NAME : Doorbell
- LABEL : PRIMARY
- URL : rtsp://192.168.1.47:554/Streaming/Channels/1
- UUID : STREAM:831f53b2-208a-41a7-b33b-221dbc54dfc4
- SESS : 475dca9a-de0e-4195-a68a-d82041c2b3e9
- MODIF : Thu Nov 05 2020 13:18:24 GMT-0800 (Pacific Standard Time)
- TAGS : @fakefmtp,@tunnel
INITIALIZE RTSP STREAM: Doorbell
- NAME : Doorbell
- LABEL : PRIMARY
- URL : rtsp://192.168.1.47:554/Streaming/Channels/1
- UUID : STREAM:831f53b2-208a-41a7-b33b-221dbc54dfc4
- SESS : 69a79cbe-c0e5-452e-8c8d-bed521081f15
- MODIF : Thu Nov 05 2020 13:37:29 GMT-0800 (Pacific Standard Time)
- TAGS : @tunnel
RTSP STREAM MODIFIED: Doorbell
Any existing RTSP steams will be shut down
and a new stream instance will be registered.2020-11-05T21:38:57.164Z [DEBUG] <RTSP-PROXY> [REQUEST] --> [DEREGISTER] rtsp:/
/192.168.1.47:554/Streaming/Channels/1
2020-11-05T21:38:57.164Z [TRACE] <RTSP-PROXY> [REQUEST] --> [HEADERS] {
“cseq”: “1”,
“transport”: “reuse_connection=0;preferred_delivery_protocol=udp;proxy_url_suf
fix=STREAM:831f53b2-208a-41a7-b33b-221dbc54dfc4”
}
2020-11-05T21:38:57.203Z [DEBUG] <RTSP-PROXY> [RESPONSE] <-- [451 (Invalid param
eter)] <cseq=1> (session=undefined)
2020-11-05T21:38:57.216Z [TRACE] <RTSP-PROXY> [RESPONSE] <-- [HEADERS] {
“cseq”: “1”,
“date”: “Thu, Nov 05 2020 21:38:57 GMT”
}