Hikvision Doorbell / Videointercom integration

Check the addon log if you make a call to see if you see an event… Not all doorbells provide the call state in the SDK

OK,

at 12:53 I pressed the bell, but only the movement was detected and the door opened due to facial recognition.

So this means, for the DS-KV9503 Hik Vision does not provide the information when somebody pressed the doorbell button at the device?

If so, can you @pergola.fabio think of another way for me to get the information in HA with my Hikvision DS-KV9503.

Can anyone else confirm this behavior with Hikvision DS-KV9503 or is there something wrong with my setup?
I’m new to Home Assistant.

I have tried

curl -i --digest -u admin:franca1hik http://192.168.178.113/ISAPI/VideoIntercom/callStatus?format=json

and got this response when pressing the button.

image

only when I am changing in the Web UI to ISAPI the CallStatus is showing ring.

image

Maybe this is bug in the implementation at Hik Vision for my device?

Don’t think it’s a bug, it’s just not supported… You can maybe use the hikconnect integration in HACS? Or you can indeed make an automation to poll the callstatus button, that’s just sending the same Isapi command

Or maybe you need to use the hikconnect setting?

Ciao Fabio, i have DS-KV6113-WPE1(C) and DS-KH9510-WTE1(B) and I’m trying to use automation

“- alias: Reject call when door is opened manually
initial_state: ‘on’
trigger:
- platform: state
entity_id: binary_sensor.openclose
from: ‘off’
to: ‘on’
condition:
- condition: template
value_template: “{{ (as_timestamp(now()) - as_timestamp(states.sensor.hikvision_callstatus.last_changed)) < 30 }}”
action:
service: hassio.addon_stdin
data:
addon: aff2db71_hikvision_sdk
input: reject”

but the template does not work.

Then the reject command doesn’t work on the internal unit.
I use Hik Connect
Thanks for the support and for the excellent work!

It should work, I have the same 9510 model, what in your log? Reject should work on a real call

2024-12-07 11:54:13.449 | ERROR | mqtt_input:_reject_call_callback:321 - Error while rejecting the call with ISAPI: (‘Error while calling ISAPI /ISAPI/VideoIntercom/callSignal?format=json’, 29, ‘Device operation failed.’)

Parli italiano?
La chiamata su hikconnet si chiude, il posto interno continua a suonare…
Per l’automazione sai indicarmi qualcosa?

No Italiano :slight_smile:

Make sure there is a real incoming call on the device, otherwise you see indeed error 29, that’s normal

Seeing your name, I thought you were Italian. :grinning:

Actually it doesn’t give any more errors but it doesn’t close the call on the internal station. It continues to ring. :dizzy_face:

This is the automation:

alias: aaa Chiudi chiamata se apri cancello
description: ""
triggers:
  - entity_id:
      - binary_sensor.cancello
    from: "off"
    to: "on"
    trigger: state
conditions:
  - condition: template
    value_template: >-
      {{ (as_timestamp(now()) -
      as_timestamp(states.sensor.posto_esterno_call_state.last_changed)) < 30 }}
actions:
  - action: hassio.addon_stdin
    data:
      addon: aff2db71_hikvision_doorbell
      input: reject posto_esterno
  - action: hassio.addon_stdin
    data:
      addon: aff2db71_hikvision_doorbell
      input: reject posto_interno
initial_state: "on"

@pergola.fabio fyi.

now able to monitor door_relay event triggered by a passcode entry

1 Like

Thanks for the help,

with the hikconnect integration in HACS I get not a state “ringing”.

Where/how can all the possible “control_source” attributes be identified?

you want to know upfront the id? dont think thats possible, its somekind of unique value, you need to open the door to see it, then make note of it :slight_smile:

1 Like

got it, tnx.

Hello @pergola.fabio, thank you for your work on this. I too am trying to trigger the relays on the KH6350 indoor station. I’m trying to test these commands using Postman, but I get ECONNREFUSED. For authentication, I have it set to Digest. Must an api key be used? If so, where could it be found?

thats normal, indoor stations dont have port 80 open, you cant connect to them, you need to use my SDK addon, those buttons are integrated for indoor stations:

image

@pergola.fabio can you help me with this?
Thanks :grinning:

Not sure how? Is the binary sensor correct? Is the template correct? What do you see in log? Is the automation actually fired? Can be lots of things… What are you using the stdin service ? Why not using the buttons?

I explained myself badly. The automation starts correctly and does everything it is supposed to. What doesn’t work is the internal station reject. Both from “stdin” and “button”.
With a call in progress, it closes the call on hikconnect but not on the internal station.
I have “DS-KH9510-WTE1(B)”.

I see. I’m trying to get this to work with Homebridge by utilizing virtual http buttons. Will this not work without creating an SDK environment?