Hikvision Doorbell / Videointercom integration

i removed the old indoor and put the new one with same IP

my question
does the DS-KH9510 compatible with this addon ?

thanks

yes, i have the same indoor station :slight_smile: , also revision B

1 Like

:smiling_face_with_three_hearts:

i will try today
my new indoor V2.2.36_build240115 and i hope it will work

thanks

Thank you. Now I have a working notification that the door is open. Please tell me, is it possible to receive a signal from the door that it is closed?

This is what the log shows when you open the door and then close it.

You asked this already lots of times, if it’s not there , then there is no event to be logged

1 Like

Hi, i’m trying to use a DS-KD8003-IME1 in a standalone configuration (no indoor station) using SIP. I do not understand if i’m doing this right:

Registration password has the same in the [auth-kd8003] section of pjsip_custom.conf file in asterisk server, but it fails to autenticate:

[Nov  9 18:36:33] NOTICE[11072]: res_pjsip/pjsip_distributor.c:673 log_failed_request: Request 'REGISTER' from '"kd8003" <sip:[email protected]>' failed for '192.168.18.9:5060' (callid: [email protected]:5060) - Failed to authenticate

What i’m missing out?

Try for username something simple, all lowercase, no special character…

Still not working… I saw another configuration menu in iVMS.

The previous post was done with basic settings, and this one uses advanced settings, it’s a bit different. I can’t find the SIP settings under network setup, there is a “group network settings” not sharing the parameters specified in the basic SIP menu:

Why there are 2 different configuration ways? why does not share all the settings regarding SIP configuration? I can’t find any of the parameters that I specified in the Basic menu.

Those advanced settings are for indoor stations, they also use sip, you don’t need to touch those…

The basic settings are enough

Did you try also an easy password?

There is new Hikvision firmware for DS KV9503 available:
https://www.hikvisioneurope.com/eu/portal/?dir=portal/Technical%20Materials/07%20%20Video%20Intercom/00%20%20Product%20Firmware/01%20Door%20Station%20(KD%20KV%20KB)/KV%20Series/KV9503/V2.3.13_build240814

(or the latest one: https://assets.hikvision.com/prd/public/all/files/202411/releasenote\KV9_Villa_Door_Station_V2.3.13_build241026_Release_Note.pdf )

and new feature is available:

New Features
1.
Support call hik-connect app person mode directly or call hik-connect team mode.

Default Channel: Call according to room No. quantity in device, if only one room, device will call Hik-Connect Person mode (same as KV6/KV8 series villa door station), if more than one room in device, it will call Hik-Connect team mode
ISAPI Transparent Transmission Channel: Call Hik-Connect team mode only
Hik-Connect Alarm Channel: Call Hik-Connect person mode only

Do you think this would affect the issue with call status polling manually for DS KV9503?

No idea :slight_smile:

Ok, will check that later and let you know :slight_smile:

Hi friend!
Thanks for all the efford you put in the project.
My question:
I own a DS-KD8003-IME1(B) without indoor station. MQTT is set up and seems to work.

2024-11-12 20:32:48.574 | INFO     | mqtt_input:_hangup_call_callback:331 - Received hangup command for doorbell: Eingang
2024-11-12 20:32:48.581 | ERROR    | mqtt_input:_hangup_call_callback:344 - Error while Hanging up the call with ISAPI: ('Error while calling ISAPI /ISAPI/VideoIntercom/callSignal?format=json', 11, 'The data sent to the device is illegal, or the data received from the device error.  E.g. The input data is not supported by the device for remote configuration.')
2024-11-12 20:32:49.187 | INFO     | mqtt_input:_hangup_call_callback:331 - Received hangup command for doorbell: Eingang
2024-11-12 20:32:49.197 | ERROR    | mqtt_input:_hangup_call_callback:344 - Error while Hanging up the call with ISAPI: ('Error while calling ISAPI /ISAPI/VideoIntercom/callSignal?format=json', 11, 'The data sent to the device is illegal, or the data received from the device error.  E.g. The input data is not supported by the device for remote configuration.')
2024-11-12 20:32:50.734 | INFO     | mqtt_input:_reject_call_callback:308 - Received reject command for doorbell: Eingang
2024-11-12 20:32:50.741 | ERROR    | mqtt_input:_reject_call_callback:321 - Error while rejecting the call with ISAPI: ('Error while calling ISAPI /ISAPI/VideoIntercom/callSignal?format=json', 11, 'The data sent to the device is illegal, or the data received from the device error.  E.g. The input data is not supported by the device for remote configuration.')
2024-11-12 20:32:51.588 | INFO     | mqtt_input:_unmute_audio_output_callback:497 - Received unmute audio output command for doorbell: Eingang

At least i can mute and unmute. But how do i get a notification when someone presses the bell outside? It seems not to work and i cant see any activity in the log when pressing the button.

Many thanks :slight_smile:

8003 doesn’t work without indoor station, unless you setup a sip server

Ok. Thanks for the fast reply :slight_smile:
an indoor station it will be then…

1 Like

I have a DS-KV6113-WPE1(C) in standalone mode registered against an Asterisk and using 2way audio integration with Frigate. So far so good, seems to be working fine, at least around the tests I could do in 2 days checking it.
… the only weird thing is that microphone light is always power on in the device, only when pressing the button to make a call it power off for a few seconds. Is this a normal behavior? is there any way to power off the light?.

Dear Fabio,

first of all, thank you for the integration!

I integrated a Metzler VDM10 1.0 (rebranded german product)

Everything works perfectly fine, except the motion sensor.
I can see it’s activity on the MQTT explorer, as a device automation, which will not be created as an entity.
Could you give me a lift if it is even possible to integrate that motion sensor?

Thank you in advance!

correct, the motion event is not an sensor, but indeed an device automation… we decided to not create sensors for each type of event like zone, motion, …
the only exception was the call/door sensor…
but you can build automations too on the device automations

that was fast :smiley:
completely overseen the automations section and got it.
Thank you!

1 Like