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

where did you find this firmware? Am confused…

The custom one? You can’t find it anywhere , only here…

The other builds are just on hikvision portal

am sorry, am lost
I can’t understand what you are saying.

the firmware I have is DS-KD8003-IME2 v2.0.8build191023
the stream works, but not the open command.

Yes , probably not supported on your firmware… Just update to 2.2.45 an try again…

I’d you update to the custom firmware, then there are more ISAPi command possible

Hey @jpet , do you have that script ready to send commands trough cloud? Can you share it, I think it can be verry usefull for people, the hikconnect integration doesn’t support yet custom commands…

I have also found a way to send ISAPi trough the cloud, so verry interesting for people that don’t have access to outdoor station ( living in appointment)

@pergola.fabio in these weeks I have very little time to spend on the intercoms unfortunately, but is the documentation really so laking? I seem to have read that you have quite good relations with your suppliers, could you attempt asking them if hikvision can provide more up-to-date docs with extensive commands also for the kd8003 series?

And btw anyone here who has the villa stations (which afaik are the kv***) with multiple users? Just to understand if they work with a simple command without specifying all the additional specifications needed for the 8003.

no, i think my firmware is a beta , done in a hurry and full of bugs.

I think it would work to put the firmware for version B on it as well, but I’m afraid I won’t break it, if I succeed in this part with the closing of the call, I have everything I need.

take a look here, the new interface (which also includes protocol 2.0) is much better imo, remember to upgrade both outdoor station and indoor monitors. Search for DVSLTD on youtube in case, he has a guide on how to pair indoor monitors in the outer station with protocol 2.0.
Firmware here, go in the appropriate folder https://www.hikvisioneurope.com/eu/portal/?dir=portal/Technical%20Materials/07%20%20Video%20Intercom/00%20%20Product%20Firmware

No problem, I already asked for new firmware for 8003 :+)

All the docs I have are up to date, but the hardware isn’t :wink:

The UK portal is better, more recent

crap, did they give you any sort of eta? They released them back in 2019/2020 and we are still fighting for fw issues :sweat_smile:

Nah, it takes a while, I have done 2 approaches, we will see :slight_smile:

But SDK is always better, working quite good for me… But killing callsignal is not supported with SDK, only with ISAPi, or the unofficial cloud api

Can you give me more info about how can i set the cloud rest sensor?

offcourse, setup this as a sensor :

  - platform: rest
    name: hikconnect_login
    scan_interval: 7200
    resource: "https://apiieu.hik-connect.com/v3/users/login/v2"
    headers:
      customno: 1000002
      appChannel: "hikvision"
      Content-Type: "application/x-www-form-urlencoded"
      featureCode: "xxxx"
      lang: "en-US"
      clientVersion: "4.14.1.0407"
      appId: "HikConnect"
      sessionId: ""
      clientType: 55
      clientNo: "google_play"
      areaId: 111
      netType: "WIFI"
      osVersion: "5.1.1"   
    method: POST
    payload: !secret hikvision_payload
    value_template: "Hikconnect Login"    
    json_attributes:
    - loginSession

The payload is the difficult part, i have got it from proxying the hikconnect app and tracing the https traffic

i use this in my secret, the long string here:

But, since android 7 since the new api, android doesnt allow anymore to capture HTTPS traffic, so you need to download the .apk file from hikconnect, remove the security and install again with this tool :

then use fiddler on your desktop, and setup your android device,setup the wifi setting your notebook as a proxy, so all traffic is going to your desktop

see here for more info

then just simulate any action like login, reject call , open door, whatever command, and you can see the actually payload :slight_smile:

i use it for a lot of apps i have on my android, to actually see what the app is doing when you press a button, most of the time its an https command, so i can simulate those events, and bring them in HA also if there is no integration yet

that sensor above will give you an sessioID, thats the most important one, i have setup the scan interval to some hours, because the sessionId doesnt last forever, its actually you login sesion
But once you have it, you can use it in your shellcommand like below, that command will do a reject of the call, the XXXX part is the serial of your indoor device, starts with Q … you can also see it in fiddler

hikconnect_callsignal_3: >
  curl -X PUT
  --header "sessionId: {{ state_attr('sensor.hikconnect_login', 'loginSession').sessionId }}"
  "https://apiieu.hik-connect.com/v3/devconfig/v1/call/xxxxxx/operation?cmdId=3&handler=xxxxx"

Damn, i have only iOS devices :frowning:

ow ok, well maybe it just works , just setup your ios device, with your dekstop as a proxy in the wifi settings… maybe ios doesnt have any security protocol in https
https://www.charlesproxy.com/
that one also works

acording to this, dont think you need to modify the ios app! seems no security present as like in android, even easier :slight_smile:

Great, but i need to find a wifi dongle or a laptop :slight_smile:
I have only a desktop without wifi connection.