DS-KD8003-IME1(B) / DS-KV6113 / DS-KV8113 ... Not reciving door ringing state.... since firmware 3.7.x

[MarcoCITA]

What happened?

Hi, after updating to V3.7.1 build 250317 (DS-KD8003-IME1(B)) the state of the sensor "Call state" remains to idle. In the addon logs i don't see any doorbell ringing entry. My indoor unit is a DS-KH6320-WTE1 version V2.2.100 build 250114.

Add-on

Hikvision Doorbell

What version of the add-on are you running?

3.0.21

Installation type

Home Assistant add-on

Relevant log output

2025-04-10 13:33:37.374 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:33:37.375 | INFO     | mqtt:video_intercom_event:364 - Video intercom event authentication_log detected on Citofono cancello
2025-04-10 13:33:37.375 | INFO     | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'authentication_log', 'type': 'event', 'subtype': 'authentication log'}
2025-04-10 13:33:37.375 | INFO     | event:video_intercom_event:109 - Video intercom event from Citofono cancello
2025-04-10 13:33:37.688 | DEBUG    | event:_handle_callback:220 - Callback invoked from SDK
2025-04-10 13:33:37.689 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:33:37.689 | INFO     | mqtt:update_door_entities:300 - Door 1 unlocked by 494848494849494848484900 , updating sensor and device trigger
2025-04-10 13:33:37.689 | INFO     | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '494848494849494848484900'}}
2025-04-10 13:33:37.689 | INFO     | event:video_intercom_event:109 - Video intercom event from Citofono cancello
2025-04-10 13:33:37.995 | DEBUG    | event:_handle_callback:220 - Callback invoked from SDK
2025-04-10 13:33:37.996 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:33:37.996 | WARNING  | mqtt:video_intercom_alarm:384 - Received unknown alarm type: 0
2025-04-10 13:33:37.996 | INFO     | event:video_intercom_alarm:120 - Video intercom alarm from Citofono cancello
2025-04-10 13:33:38.303 | DEBUG    | event:_handle_callback:220 - Callback invoked from SDK
2025-04-10 13:33:38.303 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:33:38.303 | INFO     | mqtt:video_intercom_event:354 - Magnetic door event detected on door 1
2025-04-10 13:33:38.303 | INFO     | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'magnetic door status', 'type': 'event', 'subtype': 'magnetic_door_status', 'payload': {'door_id': 1}}
2025-04-10 13:33:38.304 | INFO     | event:video_intercom_event:109 - Video intercom event from Citofono cancello
2025-04-10 13:33:38.635 | DEBUG    | event:_handle_callback:220 - Callback invoked from SDK
2025-04-10 13:33:38.636 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:33:38.636 | WARNING  | mqtt:video_intercom_alarm:384 - Received unknown alarm type: 0
2025-04-10 13:33:38.636 | INFO     | event:video_intercom_alarm:120 - Video intercom alarm from Citofono cancello
2025-04-10 13:33:39.051 | DEBUG    | event:_handle_callback:220 - Callback invoked from SDK
2025-04-10 13:33:39.052 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:33:39.052 | INFO     | mqtt:video_intercom_event:354 - Magnetic door event detected on door 1
2025-04-10 13:33:39.052 | INFO     | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'magnetic door status', 'type': 'event', 'subtype': 'magnetic_door_status', 'payload': {'door_id': 1}}
2025-04-10 13:33:39.052 | INFO     | event:video_intercom_event:109 - Video intercom event from Citofono cancello
2025-04-10 13:33:39.868 | DEBUG    | event:_handle_callback:220 - Callback invoked from SDK
2025-04-10 13:33:39.869 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:33:39.874 | INFO     | mqtt:video_intercom_alarm:448 - Video intercom alarm sos_cancelled detected on Unità interna
2025-04-10 13:33:39.877 | INFO     | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'sos_cancelled', 'type': 'alarm', 'subtype': 'sos cancelled'}
2025-04-10 13:33:39.877 | INFO     | event:video_intercom_alarm:120 - Video intercom alarm from Unità interna
2025-04-10 13:35:14.472 | DEBUG    | event:_handle_callback:220 - Callback invoked from SDK
2025-04-10 13:35:14.473 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:35:14.473 | INFO     | mqtt:video_intercom_event:354 - Magnetic door event detected on door 1
2025-04-10 13:35:14.473 | INFO     | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'magnetic door status', 'type': 'event', 'subtype': 'magnetic_door_status', 'payload': {'door_id': 1}}
2025-04-10 13:35:14.473 | INFO     | event:video_intercom_event:109 - Video intercom event from Citofono cancello
2025-04-10 13:35:15.602 | DEBUG    | event:_handle_callback:220 - Callback invoked from SDK
2025-04-10 13:35:15.602 | DEBUG    | event:_invoke_handlers:192 - Invoking 2 handlers
2025-04-10 13:35:15.602 | INFO     | mqtt:video_intercom_alarm:438 - External force detected on door 1
2025-04-10 13:35:15.603 | INFO     | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'door open by external force', 'type': 'event', 'subtype': 'door_open_by_external_force', 'payload': {'door_id': 1}}
2025-04-10 13:35:15.603 | INFO     | event:video_intercom_alarm:120 - Video intercom alarm from Citofono cancello

Relevant configuration

Anything else?

No response

[pergolafabio]

Hmm , strange, not sure if I can do anything about it :-(

I see this:

2025-04-10 13:33:37.996 | WARNING | mqtt:video_intercom_alarm:384 - Received unknown alarm type: 0

Is that the call event maybe?

[MarcoCITA]

No, tried again now and no events logged. I'll wait for a hikvision update.

[pergolafabio]

ok, you can report it indeed to hikvision

[MiguelCosta]

hi

I have the samne issue. :(

I'm using a DS-KD8003-IME1(B) and after upgrade to V3.7.1 build 250317, the door ringing state doesn't change :(

[MiguelCosta]

I rang the doorbell around 15:53 but it seems like nothing special happened in the logs:

2025-04-19 15:50:44.071 | DEBUG    | mqtt:__init__:163 - Configuring 0 door switches
2025-04-19 15:50:44.071 | DEBUG    | sdk.utils:call_ISAPI:125 - Call ISAPI request method url body: GET /ISAPI/System/deviceInfo  
2025-04-19 15:50:44.078 | DEBUG    | sdk.utils:call_ISAPI:165 - Response output: <DeviceInfo version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<deviceName>Campainha</deviceName>
<deviceID>48513235-3837-3134-3933-bc5e335d9dcc</deviceID>
<model>DS-KH6320-WTE1</model>
<serialNumber>DS-KH6320-WTE10120230518WRQ25871493U</serialNumber>
<macAddress>bc:5e:33:5d:9d:cc</macAddress>
<firmwareVersion>V2.2.100</firmwareVersion>
<firmwareReleasedDate>build 250114</firmwareReleasedDate>
<encoderVersion>V1.0</encoderVersion>
<encoderReleasedDate>build 000000</encoderReleasedDate>
<deviceType>VIS</deviceType>
<subDeviceType>indoor</subDeviceType>
<RS485Num>1</RS485Num>
<telecontrolID>255</telecontrolID>
<alarmOutNum>2</alarmOutNum>
<alarmInNum>8</alarmInNum>
<customizedInfo></customizedInfo>
<OEMCode>1</OEMCode>
</DeviceInfo>
2025-04-19 15:50:44.079 | DEBUG    | doorbell:isapi_device_info:349 - We have found 2 com ports for the indoor device
2025-04-19 15:50:44.079 | DEBUG    | mqtt:__init__:183 - Configuring 2 door switches
[2025-04-19 15:50:44.074][INF] Private connect 192.168.31.160:8000 sock=142 this=0x575c82f4 cmd=0x117000 port=60320
[2025-04-19 15:50:44.078][DBG] SimpleSTDCommandToDvr with out cmd[GET /ISAPI/System/deviceInfo], input size[0], max segment length[262144]
2025-04-19 15:50:44.083 | DEBUG    | event:register_handler:234 - Adding event handler MQTT
2025-04-19 15:50:44.084 | DEBUG    | mqtt_input:__init__:21 - Setting up MQTTInput
2025-04-19 15:50:44.085 | DEBUG    | sdk.utils:call_ISAPI:125 - Call ISAPI request method url body: GET /ISAPI/System/deviceInfo  
[2025-04-19 15:50:44.090][INF] Private connect 192.168.31.161:8000 sock=148 this=0x575c82f4 cmd=0x117000 port=49418
2025-04-19 15:50:44.099 | DEBUG    | sdk.utils:call_ISAPI:165 - Response output: <?xml version="1.0" encoding="UTF-8"?>
<DeviceInfo version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<deviceName>OUTDOOR STATION</deviceName>
<deviceID>7d49925b-4fc7-406b-a0ec-e0baad984d63</deviceID>
<deviceDescription>VIS</deviceDescription>
<deviceLocation>STD-CGI</deviceLocation>
<systemContact>STD-CGI</systemContact>
<model>DS-KD8003-IME1(B)</model>
<serialNumber>DS-KD8003-IME1(B)0120230310ENL38693235</serialNumber>
<macAddress>e0:ba:ad:98:4d:63</macAddress>
<firmwareVersion>V3.7.1</firmwareVersion>
<firmwareReleasedDate>build 250317</firmwareReleasedDate>
<bootVersion>50790401</bootVersion>
<bootReleasedDate>1639185</bootReleasedDate>
<hardwareVersion>1-1-0</hardwareVersion>
<deviceType>VIS</deviceType>
<subDeviceType>doorStation</subDeviceType>
<telecontrolID>88</telecontrolID>
<supportBeep>true</supportBeep>
<supportVideoLoss>true</supportVideoLoss>
<alarmOutNum>2</alarmOutNum>
<alarmInNum>4</alarmInNum>
<RS485Num>1</RS485Num>
<OEMCode>1</OEMCode>
<bspVersion>V1.4.0.790168</bspVersion>
<dspVersion>V2.9.20 build 20250306</dspVersion>
<encryptionModel>e23c</encryptionModel>
<productionDate>2023-03-10</productionDate>
<displayInterfaceSize>0</displayInterfaceSize>
<releaseRegion>abroad</releaseRegion>
</DeviceInfo>
[2025-04-19 15:50:44.099][DBG] SimpleSTDCommandToDvr with out cmd[GET /ISAPI/System/deviceInfo], input size[0], max segment length[262144]
2025-04-19 15:50:44.122 | DEBUG    | sdk.utils:call_ISAPI:125 - Call ISAPI request method url body: GET /ISAPI/System/deviceInfo  
2025-04-19 15:50:44.130 | DEBUG    | sdk.utils:call_ISAPI:165 - Response output: <DeviceInfo version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<deviceName>Campainha</deviceName>
<deviceID>48513235-3837-3134-3933-bc5e335d9dcc</deviceID>
<model>DS-KH6320-WTE1</model>
<serialNumber>DS-KH6320-WTE10120230518WRQ25871493U</serialNumber>
<macAddress>bc:5e:33:5d:9d:cc</macAddress>
<firmwareVersion>V2.2.100</firmwareVersion>
<firmwareReleasedDate>build 250114</firmwareReleasedDate>
<encoderVersion>V1.0</encoderVersion>
<encoderReleasedDate>build 000000</encoderReleasedDate>
<deviceType>VIS</deviceType>
<subDeviceType>indoor</subDeviceType>
<RS485Num>1</RS485Num>
<telecontrolID>255</telecontrolID>
<alarmOutNum>2</alarmOutNum>
<alarmInNum>8</alarmInNum>
<customizedInfo></customizedInfo>
<OEMCode>1</OEMCode>
</DeviceInfo>
[2025-04-19 15:50:44.126][INF] Private connect 192.168.31.160:8000 sock=175 this=0x575c82f4 cmd=0x117000 port=60336
[2025-04-19 15:50:44.130][DBG] SimpleSTDCommandToDvr with out cmd[GET /ISAPI/System/deviceInfo], input size[0], max segment length[262144]
2025-04-19 15:50:44.151 | DEBUG    | event:start:255 - Registering callback function using SDK
2025-04-19 15:50:44.154 | DEBUG    | doorbell:setup_alarm:95 - Arming the device via SDK
[2025-04-19 15:50:44.157][INF] Private connect 192.168.31.161:8000 sock=202 this=0x575c82f4 cmd=0x111020 port=49430
2025-04-19 15:50:44.164 | DEBUG    | doorbell:setup_alarm:95 - Arming the device via SDK
2025-04-19 15:50:44.171 | DEBUG    | input:loop_forever:29 - Waiting for input command
[2025-04-19 15:50:44.168][INF] Private connect 192.168.31.160:8000 sock=205 this=0x575c88d8 cmd=0x111020 port=60340
[2025-04-19 15:51:14.229][DBG] Alarm chan [0] recv timeout[2]!
[2025-04-19 15:51:44.258][DBG] Alarm chan [0] recv timeout[2]!
[2025-04-19 15:52:14.303][DBG] Alarm chan [0] recv timeout[2]!
[2025-04-19 15:52:44.326][DBG] Alarm chan [0] recv timeout[2]!
[2025-04-19 15:53:19.372][DBG] Alarm chan [0] recv timeout[2]!
[2025-04-19 15:53:44.404][DBG] Alarm chan [0] recv timeout[2]!
[2025-04-19 15:54:14.441][DBG] Alarm chan [0] recv timeout[2]!
[2025-04-19 15:54:44.469][DBG] Alarm chan [0] recv timeout[2]!

[pergolafabio]

Someone on forum linked the call event to a relay, and then capture the relay state...

There is also an call status button, it you press that when it's ringing, is it in idle or ringing state? It shows the state on the attributes

[MarcoCITA]

I tried via ISAPI request GET /ISAPI/VideoIntercom/callStatus?format=jsonn and i get ringing

[pergolafabio]

Ah, that's good, so you can use a polling automation using the call status button

[MiguelCosta]

Someone on forum linked the call event to a relay, and then capture the relay state...

There is also an call status button, it you press that when it's ringing, is it in idle or ringing state? It shows the state on the attributes

sorry but I'm trying to find where I can configure to link the call event to a relay but I can't find it... any ideas?

[MiguelCosta]

I think hikvision removed the frimware V3.7.1 build 250317 🤔

• Direct link that I have but it is not available on the website: https://assets.hikvision.com/prd/public/all/files/202503/releasenote%5CKD8(-B)_Main_Module_Release_Note_V3.7.1_build250317.pdf

Now I only see the version V2.2.78_241012

• https://www.hikvisioneurope.com/eu/portal/?dir=portal%2FTechnical%20Materials%2F07%20%20Video%20Intercom%2F00%20%20Product%20Firmware%2F01%20Door%20Station%20%28KD%20KV%20KB%29%2FKD%20Series%2FKD8003%28B%29

• https://www.hikvision.com/pt/products/Video-Intercom-Products/IP-Series/Pro-Series/ds-kd8003-ime1-b-----surface-eu/

• https://www.hikvision.com/en/support/download/firmware/

[luigixx73]

I have the same issue with DS-KV8113-WME1(C) and firmware V3.7.0 build 250317
Just using ISAP polling with "/ISAPI/VideoIntercom/callStatus?format=json" as workaround

[LucasTor]

+1 for the callStatus endpoint, when doing the API call I receive this response back

{
  "CallStatus": {
    "status": "ring"
  }
}

which should be enough to create a restful sensor inside Home Assistant, I'll get to it when I have a few minutes and I can post the complete sensor code here