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

pergola.fabio · April 30, 2021, 11:59am

Yes, will do that later…
You need fiddler also, to get some header stuff
And also an emulator if you have android… Newer android os, doesn’t allow to trace https

jmnovak · May 1, 2021, 2:30pm

Hi all,

Some really interesting threads here. I actually just bought a 6113 and simply trying to use a doorbell. No need for a remote unlock/lock function. Really liking homekit’s native support surrounding video doorbells and have tried using camera ffmpeg under homebridge. But some limitations as you can probably imagine to that approach. So hopped in the HA and noticed this thread. Were trying to move away from the native HK App as its less than ideal and replicate the doorbell functionality under homekit…e.g. view live video stream (w audio) at anytime, notified on doorbell press, notified on motion detection, and engage in 2-way conversation.

Ive was able to see some of the apis…e.g.

curl -i digest http ://user:[email protected]/ISAPI/VideoIntercom/callStatus
curl -i digest http : // user:[email protected]/ISAPI/VideoIntercom/capabilities

As far as firmware, I’m on V2.2.13 build 201222 and its not proving to have any limitations from an api pov…at least right now. I just have no clue right now how to get from here to there. Any general directional suggestions would be greatly welcome!

pergola.fabio · May 2, 2021, 6:54pm

guys, need some help, i am testing with the Hikconnect integration, i created a login sensor, thats sensor gives me a sessionId like in the app… With that sessionId we can create other rest commands/sensor like open door, callstatus, callhistory, for example like below

The sessionId offcourse changes, after an amount of time, the below command works, but i cant use it like below, its not allowed to template the headers, its only possible for a value template
any idea how to workaround this? any tips?

if it put it as a static hardcoded string it works offcourse

{{ state_attr('sensor.hikconnect_login', 'loginSession').sessionId }}

  - platform: rest
    name: hikconnect_last_calltime
    scan_interval: 5
    resource: "https://apiieu.hik-connect.com/v3/calling/listByUser?leastTime=&msgStatus=-1&pageSize=1"
    headers:
      #sessionId: "{{ state_attr('sensor.hikconnect_login', 'loginSession').sessionId }}"
      sessionId: eyJhbGciOiJIUzM4NCJ9.eyJhdWQiOixxxxxxxxxxx
    method: GET
    value_template: "Hikvision Last Calltime"
    json_attributes_path: "$.data[0]"    
    json_attributes:
      - callingTime

@mihalich1988 from fiddler , how did you obtain the reauth url? maybe i can use that one

Whytey · May 3, 2021, 10:21am

I haven’t ever done anything like that. Is it possible to use a template sensor to store the session ID and then use that in the headers??

pergola.fabio · May 3, 2021, 10:35am

the problem is that the header doesnt support templating, so we can only use a fixed value or a secret

seems a lot of users have the same issue on this forum, there are maybe some customs out

pergola.fabio · May 3, 2021, 1:30pm

got it too work, when using a command line sensor, instead of a rest sensor
With a command line, i can use templating

  - platform: command_line
    command: >
      curl
      --header "sessionId: {{ state_attr('sensor.hikconnect_login', 'loginSession').sessionId }}"
      "https://apiieu.hik-connect.com/v3/devconfig/v1/call/Qxxxxx/status"
    name: hikconnect_callstatus
    scan_interval: 5
    value_template: "Callstatus"
    json_attributes:
      - data

gives me :

so afterwards we can use this template, that gives 1 , 2 , or 3 , regarding call status
{{ (state_attr('sensor.hikconnect_callstatus', 'data')|from_json).callStatus }}

pergola.fabio · May 3, 2021, 6:17pm

Guys, i edited first post, some Tracing stuff from the HikConnect app, it finally works now for my DS8003 , so now i also have CallStatus, that was not working before with ISAPI

the only command/state i am trying to find, is the actually state of an door, if relay is open or not…

pergola.fabio · May 4, 2021, 8:07pm

Guys , can anyone try an ISAPI command? i have 400 or 404 bad request/not found on below ISAPI:

i should give me the state of the input/outputs, for example also the doorlock:
the yellow comamnd, works, but the status , the one with red circle doesnt

ishalem · May 5, 2021, 5:30am

I got the same output

pergola.fabio · May 5, 2021, 6:03am

Also an ds8003?

pergola.fabio · May 5, 2021, 6:38am

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

ishalem · May 5, 2021, 10:31am

My model: DS-KD8003-IME1 / EU

Whytey · May 5, 2021, 12:13pm

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>

pergola.fabio · May 5, 2021, 12:40pm

crap, doesnt work also on 61xx device

i was hoping to capture the state of a door relay
too bad
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 “yet”

pavoroby · May 5, 2021, 6:35pm

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).

jmnovak · May 5, 2021, 10:40pm

@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?

pavoroby · May 6, 2021, 7:50am

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

pergola.fabio · May 6, 2021, 8:27am

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

Whytey · May 6, 2021, 11:41am

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

Whytey · May 6, 2021, 11:43am

@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.