DS-KD8003 - DS-KV8113 - DS-KV8213 - DS-KV6113 - DS-KV8413 and .... integration Hikvision HikConnect Video intercom doorbell

Share your Projects!
324

I got the same output

325

Also an ds8003?

326

Maybe the request is only valid from the indoor panel, gonna try later to read the state from cloudā€¦ Would be usefulll for automationsā€¦

So if i open the door , i can already turn on music and lights :wink:

1 Like
327

My model: DS-KD8003-IME1 / EU

328

Model 6113:

ISAPI/System/IO/outputs:

<IOOutputPortList version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<IOOutputPort version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<id>1</id>
<name>COM</name>
<IOUseType>electricLock</IOUseType>
</IOOutputPort>
</IOOutputPortList>

/ISAPI/System/IO/outputs/1:

<?xml version="1.0" encoding="UTF-8"?>
<ResponseStatus version="1.0" xmlns="http://www.std-cgi.com/ver10/XMLSchema">
<requestURL>/ISAPI/System/IO/outputs/1</requestURL>
<statusCode>4</statusCode>
<statusString>Invalid Operation</statusString>
<subStatusCode>notSupport</subStatusCode>
<errorCode>1073741825</errorCode>
<errorMsg>The device does not support this resource</errorMsg>
</ResponseStatus>

ISAPI/System/IO/outputs/1/status:

<?xml version="1.0" encoding="UTF-8"?>
<ResponseStatus version="1.0" xmlns="http://www.std-cgi.com/ver10/XMLSchema">
<requestURL>/ISAPI/System/IO/outputs/1/status</requestURL>
<statusCode>4</statusCode>
<statusString>Invalid Operation</statusString>
<subStatusCode>notSupport</subStatusCode>
<errorCode>1073741825</errorCode>
<errorMsg>The device does not support this resource</errorMsg>
</ResponseStatus>
329

crap, doesnt work also on 61xx device :frowning:

i was hoping to capture the state of a door relay
too bad :frowning:
i am also trying to capture it from the cloud, still no luck
there must be a a way to , i just dont know how :slight_smile: ā€œyetā€

330

Hi. Sorry for not answering for a long time, vacation.

  • Now the firmware on my device is V2.2.43 build 210407
  • Yes, I have full access to the settings via the web interface.
  • Yes, I poll the device status every second using curl (ubuntu server 20.04).
331

@pavoroby I think you also have the same device I haveā€¦which API do you poll every second? And can you send my the syntax you use using curl?

332 
curl --digest -u admin:Pa$$w0rd http://10.1.1.245/ISAPI/VideoIntercom/callStatus?format=json

10.1.1.245 ā€“ IP address of my intercom on my local network

333

do you poll every 1 sec? there is no hammering?
i have the 8003 , that doesnt support that command yet, i am now polling it from cloud from hikconnect , i have it now for testing at 3 sec

334

Not sure you saw my results for this, but I was polling my 6113 on the local at 0.2 second intervals with success.

335

@pavoroby thanks for the response. Where did you get your 2.2.43 firmware from, that is very recent. Have you noticed any differences with it? Did you see any release notes for that version?

Further, I assume your device was delivered with an older version of the firmware. Could you confirm, which versions you had to install to get to 2.2.43 with the web UI. I believe you canā€™t just jump from one firmware to another, you have to go through all interim releases, also.

Thanks.

336

Cool, thatā€™s verry fast polling :wink:

We 8003 owners need to wait a little more, a new firmware is coming this month with more ISAPI commands

337

Can you share the code for the sensor (HA) ?

338

its a command line sensor, have a loo k at first post, i have created there some command line sensors, just change the command offcourse to the isapi url

you can then use somekind of autimation, if the callstatus = 2 => doorpress , the fire an action

- alias: Hikconnect Doorbell
  initial_state: 'on'
  trigger:
  - platform: state
    entity_id: sensor.hikconnect_callstatus
  condition:
  - condition: template    
    value_template: >
      {% if (state_attr('sensor.hikconnect_callstatus', 'data')|from_json).callStatus == 2 %}True{% endif %}
  action:
  - service: input_boolean.toggle
    entity_id: input_boolean.test1
1 Like
339

Ah thank you! I see! you are basically polling to see when someone presses the doorbell.

Iā€™m still looking for the right API syntax for motion detection and separately the API being used for 2 way voice intercom. I think you mentioned in an earlier post that your are using some sort of SIP server but I am trying to understand how that interacts? Can 2 way voice be leveraged via API call or only through SIP integration?

BTW I am on the same firmware version

340

Two audio should be possible by ISAPI too, not that easy thoughā€¦ why you need it? You donā€™t want to make use of Hikconnect? If not, then setting up a PBX server is indeed another road for SIP callsā€¦ I tested it before, it workedā€¦ But early video I couldnā€™t get to work, i had only video when I pickup the call afterwards

Have al look hereā€¦

Based on older isapi , i have updated all ISAPI in thread start

341

Hi @ishalem . Since I am doing local polling, this is what I currently have:

- platform: rest
  name: Doorbell Status
  authentication: digest
  username: admin
  password: <password>
  scan_interval: 1
  resource: http://192.168.0.XXX/ISAPI/VideoIntercom/callStatus?format=json
  value_template: "{{ value_json.CallStatus.status }}"

Cheers,
Whytey

2 Likes
342

Hi Fabio!

Thank you so much l! Very helpful indeed! Re: Hikconnectā€¦app is less than ideal. Would love to build some HomeKit integration and still fumbling around w HA right now. So all very new! Had experimented with an old Ring doorbell with a home bridge plugin and really liked how that worked so thinking of building a similar Homekit-type of integration.

I currently have an ffmpeg stream flowing to HK using the rtsp url but need to layer in doorbell alerts, motion alerts and 2 way audio. Just Not sure of the best way to do it! Iā€™m open to suggestions!

343

I think the best way is to use ISAPI, two way audio should be possible, but i never tried itā€¦

Sip is another road , but then you need offcourse an extra server, like free PBX, quite overkill