Hey, ok you confirm that 8003 Devices works with ISAPI?
“DS-KD-KK Video Intercom Nametag Module for DS-KD8003”
So we can use this in the next time to/with commands forwarding to SmartHome contracts/Shelly usw…iobroker when the 7 ring buttons pressed seperatly on the 8003 Device…
that would be great
edit: and this system 8003 works with only 4 Lines of the 8 POE…really?!
Hey @Davimas , ISAPI already works on 8003, just not everything is supported …
Remote open door works for instance…
Yes, 2 pairs or 4 wires is enough for POE and data… so you can use other 4 for your Shelly’s…
Offcourse limited to 100mb , but more then enough for a doorbell
I have an ESP hooked up, so I can intercept a doorbell press for my automations … But normally not needed anymore next month
I’ve just reset password and I’m back to version 2.0.8
Here is a screen capture of the intercom main menu on this version. Version 2.2.3 and later had less menu items and no menus for Dial, Ring Import, Motion Detection, Intercom Protocol; Or, if they exist, they are very well hidden.
I got stuck with this situation too (downgraded firmware but had already activated the device and hence couldn’t login).
The way I fixed this was to revert back to the firmware I was last able to login with, use the ISAPI command to factory reset the device, then load the other firmware
Using ISAPI to factory reset/de-activate:
curl -i --digest -u admin:<password> -X PUT http://192.168.0.xxx/ISAPI/System/factoryReset?mode=full
Small hint for those like me that are happy with a simple camera doorbell (and not necassarily the ability to do 2-way voice).
If your firmware supports ISAPI detection of call status, I have found that by simply changing the configuration under Network > SIP > Enable VoIP Gateway (and populate some random values for server, etc), then when you press the button on the device (6113 in my case), the ISAPI request to callStatus does change, even though the doorbell just outputs a call-failed tone.
This is enough to detect the button press in Home Assistant and then perform some action; play audio on a speaker, flash a light, send a notification, etc.
If I haven’t enabled the VoIP gateway and haven’t registered with HikConnect, when I press the doorbell I get a ‘Call Failed’ audio message on the doorbell and the callStatus does not change. It is always idle.
This weekend, I configured a FreePBX instance, for fun. I noticed that when I have the VoIP Gateway checkbox checked and the SIP details entered into the doorbell but the FreePBX server is shutdown, I get the above mentioned error-dial-tone but the callStatus does change.
ok, interesting
and what if you enable the SIP gateway, but still call the normal indoor station or too hikconnect, does the callstatus still change then?
I don’t have an internal door station so can’t test that case.
I also don’t intend to use Hik-Connect (I am put off since I can’t install from the Google Play Store and have to ‘trust’ them) so can’t readily test that case either.
Hey - has anybody found a way to deactivate the Voice? I think that dont Work. I use the german Language with this China Voice - and it sounds teribble when says/speak: “call failed” :-)))
Hi.
Since the post is so long, maybe a simple summary can be put at the top. As far as I understand, except for the 8003 that does not change the status during ring under ISAPI, all other models work fine.
Furthermore, from the documentation of HA, the camera integration requires (mandatory) still image definition. I did not see one for any of the models. How can I define my doorbell HIK camera?