Unfortunately, {‘control_source’: ‘xxxxxxxxxxxxxxxxxxxxxxx’} is not an ID to identify the device… any suggestions to get intercom ID? 
What exactly do you want to identify? Control source is somekind of id of the person who opened the lock…
Hello, thank you very much for your work on Hikvision videophones. Maybe I didn’t search well enough, but do you know of a way to make an indoor unit ring, in a way that simulates pressing the outdoor button?
so “controll source” is a fixed value tied to the intercom that sent the door open command to the doorbell? correct?
no, its a variable command, like the keycode or the badge that swiped
when you open from indoor panel, its indeed the same
no, dont think thats possible, why you want todo that?
I would like to use the indoor station as a chime for a store door. The “basic” videointercom should work during night shift but as a door chime during the day.
hmm, there is no isapi command for, however you can use SIP, register the indoor device to asterisk , and use SIP to send a call signal
Thanks for these ideas, I will look into this.
Yeah!!! 
I was able to create the automation using the ‘controll_source’ attribute to forward or not, the opening command to another doorbell by diversifying the intercom that sent the command… Thanks a lot!
1 Like
Dears,
I’m making my first steps with this integration, running as container on Synology. After configuration I see both devices in MQTT, however the problem is that door station looks like generating false calls: call state switches idle/ringing, door 1 relay switches on/off.
2024-11-03 12:02:46.995 | INFO | event:video_intercom_event:109 - Video intercom event from Bramka
2024-11-03 12:02:46.995 | INFO | mqtt:update_door_entities:300 - Door 1 unlocked by 4856555752485457545100 , updating sensor and device trigger
2024-11-03 12:02:46.996 | INFO | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '4856555752485457545100'}}
2024-11-03 12:02:47.886 | INFO | event:video_intercom_event:109 - Video intercom event from Bramka
2024-11-03 12:02:47.886 | INFO | mqtt:update_door_entities:300 - Door 1 unlocked by 4856555752485457545100 , updating sensor and device trigger
2024-11-03 12:02:47.887 | INFO | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '4856555752485457545100'}}
2024-11-03 12:02:51.454 | INFO | event:video_intercom_event:109 - Video intercom event from Bramka
2024-11-03 12:02:51.455 | INFO | mqtt:update_door_entities:300 - Door 1 unlocked by 5054575149525356535700 , updating sensor and device trigger
2024-11-03 12:02:51.455 | INFO | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '5054575149525356535700'}}
2024-11-03 12:02:53.234 | INFO | event:video_intercom_event:109 - Video intercom event from Bramka
2024-11-03 12:02:53.235 | INFO | mqtt:update_door_entities:300 - Door 1 unlocked by 5150535255525352495200 , updating sensor and device trigger
2024-11-03 12:02:53.235 | INFO | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '5150535255525352495200'}}
2024-11-03 12:02:56.805 | INFO | event:video_intercom_event:109 - Video intercom event from Bramka
2024-11-03 12:02:56.805 | INFO | mqtt:update_door_entities:300 - Door 1 unlocked by 5054575149525356535700 , updating sensor and device trigger
2024-11-03 12:02:56.805 | INFO | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '5054575149525356535700'}}
2024-11-03 12:02:57.590 | INFO | event:video_intercom_event:109 - Video intercom event from Bramka
2024-11-03 12:02:57.590 | INFO | mqtt:update_door_entities:300 - Door 1 unlocked by 4856555752485457545100 , updating sensor and device trigger
2024-11-03 12:02:57.590 | INFO | mqtt:handle_device_trigger:487 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '4856555752485457545100'}}
2024-11-03 12:03:01.164 | INFO | event:video_intercom_alarm:120 - Video intercom alarm from Bramka
2024-11-03 12:03:01.164 | INFO | mqtt:video_intercom_alarm:392 - Call dismissed, updating sensor
settings: mqtt=MQTT(host='192.168.20.10', port=1883, username='***', password='***', 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-KV8113-WME1(C)', manufacturer='Hikvision', sw_version='V2.2.65', hw_version='0x0', identifiers='688345758656494951458777694940674148495048505148574856828265715056555355555', 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='688345758656494951458777694940674148495048505148574856828265715056555355555-call_state', unit_of_measurement=None, state_class=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
It’s hard to say if it reacts to real events, because even if I call door station, answer at indoor, there is no state change at indoor station log.
Any ideas what I do wrong?
That’s the backlog, give it a while, once downloaded, it should be stable
When you say “valid sip number” without being connected to a sip server like asterisk, you mean, totally invented it? like [email protected]. If I don’t register it against a PBX, mine never receive call status notifications
Good day. I found triggers for an open and closed door in your integration (I’m attaching them in the photo below). But for some reason they don’t work. Please tell me if this can be fixed? Thank you.
hi, check the addon logs, not all door open/closed events are possible with the SDK
if you see the event in the addon, then it will work for your doorbell
thanks , pergola.fabio
everything working good with me until yesterday i bought new indoor 9510 (b) and its not working any idea
regards
What do you mean? What is not working? The addon or your doorbell?
yes , only after i change the indoor monitor to 9510 Android
2024-11-06 09:53:17.968 | ERROR | main:main_loop:100 - Error while logging into Indoor Extension: Failed to connect to the device. The device is off-line, or connection timeout caused by network. Error code: 7
2024-11-06 09:53:17.968 | INFO | main:main_loop:102 - Failed to connect to the device, retrying again in 15 seconds…
ip not the same?
Thank you, I’ll take a look a bit later, I went into the logs and saw that my time was out of sync. I’m struggling to fix it.