Hikvision Doorbell / Videointercom integration

VCTGomes · March 18, 2023, 2:32pm

v2.2.53 build 220108

TokarevSergey · March 18, 2023, 2:56pm

Странно я проверил у меня работат. Попробуйте переустановить интеграцию может поможет.
Strange, I checked, it works for me. Try reinstalling the integration, it might help.

pergola.fabio · March 18, 2023, 2:59pm

Hmm, dont think your device is sending the Callsensor with SDK, you can only poll it with ISAPI i think
The alarm you see is probably something else

VCTGomes · March 18, 2023, 3:23pm

Ok. I’ll try

But does it work with my doorbell version?

pergola.fabio · March 18, 2023, 3:37pm

Well, if there is no RING event in de SDK log, then probably your device is not supported? Maybe try updating firmware on it? If still not work, please make an issue on Github

If you see the callsensor changing by ISAPI method, maybe we can add this polling method too in the Addon, for older devices , what command do you do for the ring ?

VCTGomes · March 18, 2023, 4:08pm

Thanks. I’ll do that.

I tried to reinstall everything, but it continues with no status (Idle). Door is unlocking over SKD and I’m able to reject calls too

2023-03-18 12:58:59.626 | INFO     | doorbell:authenticate:68 - Connected to doorbell: doorbell
2023-03-18 12:58:59.627 | INFO     | event:__init__:76 - Setting up event handler: Console stdout
2023-03-18 12:58:59.628 | INFO     | mqtt:__init__:91 - Setting up event handler: MQTT
2023-03-18 12:59:25.811 | INFO     | doorbell:unlock_door:113 -  Door 1 unlocked by SDK
2023-03-18 13:02:04.014 | INFO     | doorbell:unlock_door:113 -  Door 1 unlocked by SDK
2023-03-18 13:02:43.103 | INFO     | mqtt_input:_reject_call_callback:98 - Received reject command for doorbell: doorbell
2023-03-18 13:02:57.419 | INFO     | mqtt_input:_reject_call_callback:98 - Received reject command for doorbell: doorbell
2023-03-18 13:03:01.660 | INFO     | doorbell:unlock_door:113 -  Door 1 unlocked by SDK

The only problem is the Call Status not working, but I’ll open an issue on GitHub as you said.

I can see Ringing status when I open ISAP through Json page 192.168.2.62/ISAPI/VideoIntercom/callStatus?format=json

pergola.fabio · March 18, 2023, 4:09pm

Ok, maybe we can indeed add an optional mode for polling callstatus based on older devices… But have you tried updating firmware?

VCTGomes · March 18, 2023, 4:43pm

Yeah. I checked it on HikConnect and it says doorbell up to date. I’m at v2.2.53 build 220108

eyeffect · March 18, 2023, 5:49pm

I am despairing. I installed the Hikvision add-on with the Asterisk add-on exactly according to the instructions and i use the sipjs-card. How do I recognize with the DS-KV8213 whether a call is parked. For me, the bell works completely normally during the test for some time and then a few hours later there is only a busy character when ringing. I don’t quite understand how to set this up with parked calls and use it with home assistant?

pergola.fabio · March 18, 2023, 6:10pm

Yeah, sip is not easy to configure, it’s trial and error, anyway , the addon has no relationship with asterisk, so for SIP questions, best to join discord, leave this thread related to addon questions please

markus2504 · March 18, 2023, 7:16pm

Has anyone tried the MQTT addon with DS-KB8113-IM? For me, the addon opens the door every 5 minutes.

pergola.fabio · March 18, 2023, 7:29pm

That’s not possible, then you have somewhere an automation that’s doing this in HA itself, there is no 5 min timer in this addon … Or maybe an Easter egg

markus2504 · March 18, 2023, 8:58pm

I don’t know why, but in my integration, the Hikvision Doorbell (Beta) add-on opens the door and rings itself.

pergola.fabio · March 18, 2023, 9:11pm

Show me the log of the addon

pergola.fabio · March 18, 2023, 9:22pm

github.com

pergolafabio/Hikvision-Addons/blob/7f3f6d709f2ac7d4ae3f37498da647e940718284/hikvision-doorbell/src/mqtt.py#L151

    
      
                          door_switch = Switch(settings, self.door_switch_callback, (doorbell, door_id))
                          door_switch.off()
                          door_switch.set_availability(True)
                          self._sensors[doorbell][f'door_{door_id}'] = door_switch
          
          
def door_switch_callback(self, client, user_data: tuple[Doorbell, int], message: MQTTMessage):
              doorbell, door_id = user_data
              command = message.payload.decode("utf-8")
              logger.debug("Received command: {}, door_id: {}, doorbell: {}", command, door_id, doorbell._config.name)
              match command:
                  case "ON":
                      doorbell.unlock_door(door_id)
          
          
@override
          async def motion_detection(
                  self,
                  doorbell: Doorbell,
                  command: int,
                  device: NET_DVR_ALARMER,
                  alarm_info: NET_DVR_ALARMINFO_V30,
                  buffer_length,

Look in the source code, opening door can only be triggered when you put the output relay to “on” , that’s the only way to open a door, so you must be triggering this somewhere in some kind of automation, check your HA logs and addon logs, you have something screwed up

markus2504 · March 18, 2023, 9:32pm

Thank you, so I have an error.

markus2504 · March 18, 2023, 9:41pm

Logs:
2023-03-18 22:36:32.335 | INFO | event:video_intercom_alarm:109 - Video intercom alarm from bramka
2023-03-18 22:36:38.956 | INFO | mqtt:video_intercom_event:199 - Door 1 unlocked by , updating sensor Door 1 relay
2023-03-18 22:36:38.960 | INFO | event:video_intercom_event:98 - Video intercom event from bramka
2023-03-18 22:36:45.824 | INFO | mqtt:video_intercom_alarm:236 - Doorbell ringing, updating sensor
settings: mqtt=MQTT(host=‘core-mosquitto’, username=‘addons’, password=‘eish3’, client_name=None, tls_key=None, tls_certfile=None, tls_ca_cert=None, discovery_prefix=‘homeassistant’, state_prefix=‘hmd’) entity=SensorInfo(component=‘sensor’, device=DeviceInfo(name=‘bramka’, model=‘DS-KB8113-IME1’, manufacturer=‘Hikvision’, sw_version=‘V2.2.51’, hw_version=‘0x0’, identifiers=‘6883457566564949514573776949484950485049485649508282715349525248565355’, connections=None, configuration_url=None), device_class=None, enabled_by_default=None, entity_category=None, expire_after=None, force_update=None, icon=‘mdi:bell’, name=‘Call state’, object_id=‘bramka_call_state’, qos=None, unique_id=‘6883457566564949514573776949484950485049485649508282715349525248565355-call_state’, unit_of_measurement=None) debug=False manual_availability=True
topic_prefix: sensor/bramka/Call-state
config_topic: homeassistant/sensor/bramka/Call-state/config
state_topic: hmd/sensor/bramka/Call-state/state
wrote_configuration: True

2023-03-18 22:36:45.829 | INFO | event:video_intercom_alarm:109 - Video intercom alarm from bramka
2023-03-18 22:36:52.592 | INFO | mqtt:video_intercom_alarm:239 - Call dismissed, updating sensor

pergola.fabio · March 18, 2023, 9:46pm

I don’t see any error there? The addon on first start just downloads a backlog of past events, just give it a while

markus2504 · March 18, 2023, 9:54pm

Now I have Connection 2023-03-18 22:51:44.637 | INFO 2023-03-18 22:51:51.194 | INFO 2023-03-18 22:51:57.780 | INFO 2023-03-18 22:52:04.358 | INFO 2023-03-18 22:52:10.933 | INFO 2023-03-18 22:52:17.518 | INFO 2023-03-18 22:52:24.100 | INFO 2023-03-18 22:52:30.716 | INFO 2023-03-18 22:52:37.316 | INFO 2023-03-18 22:52:43.924 | INFO 2023-03-18 22:52:50.528 | INFO 2023-03-18 22:52:57.113 | INFO 2023-03-18 22:53:03.694 | INFO 2023-03-18 22:53:10.316 | INFO 2023-03-18 22:53:16.872 | INFO 2023-03-18 22:53:23.444 | INFO 2023-03-18 22:53:29.963 | INFO 2023-03-18 22:53:36.539 | INFO 2023-03-18 22:53:43.157 | INFO 2023-03-18 22:53:49.724 | INFO status: keeps ringing. Logs:
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka
| event:motion_detection:87 - Motion detected from bramka

pergola.fabio · March 18, 2023, 9:57pm

Yes , that’s the motion sensor , that’s normal if there is motion, turn off motion if not needed on your doorbell or just lower the sensitivity