Hi, yeah, i published a few hours ago, version .14 , it inlclude more events for DS-KV9503-WBE1
You need to setup indeed first an MQTT broker, i dont ise OpenHab myself 
, cant help you with that , but probably quite common
Afterwards you need to setup the env file and point indeed to the mqtt broker with IP/user/Pass
See here for instructions and examples
maybe helpfull to setup an mqtt broker in Openhab?
MQTT broker created.
It looks better now:
2024-01-23 16:25:12.880 | INFO | sdk.utils:loadSDK:44 - Using OS: Linux with architecture: x86_64
loop[2] find 2 mac and 0 ip
2024-01-23 16:25:13.066 | INFO | doorbell:authenticate:79 - Connected to doorbell: Street
2024-01-23 16:25:13.067 | INFO | event:init:87 - Setting up event handler: Console stdout
2024-01-23 16:25:13.067 | INFO | mqtt:init:117 - Setting up event handler: MQTT
Exception in callback BaseSelectorEventLoop._add_reader(0, >)
handle: <Handle BaseSelectorEventLoop._add_reader(0, >)>
Traceback (most recent call last):
I have created broker in anonymous mode, why I got Permission error?
Where to check i got last docker image? I have pulled one, but not sure.
Thanks once more.
Where did you pull docker from? Don’t use anonymous, use credentials
Pulled using portained GUI:
There is still the error with permissions, even the events are logged sucesfully (I have tried to unlock using my face and ulock doors using hik-connect, see below):
2024-01-23 17:07:03.851 | INFO | sdk.utils:loadSDK:44 - Using OS: Linux with architecture: x86_64
loop[2] find 2 mac and 0 ip
2024-01-23 17:07:04.038 | INFO | doorbell:authenticate:79 - Connected to doorbell: Street
2024-01-23 17:07:04.038 | INFO | event:init:87 - Setting up event handler: Console stdout
2024-01-23 17:07:04.038 | INFO | mqtt:init:117 - Setting up event handler: MQTT
Exception in callback BaseSelectorEventLoop._add_reader(0, >)
handle: <Handle BaseSelectorEventLoop._add_reader(0, >)>
Traceback (most recent call last):
I do not have internal intercom device installed yet and pushing the call button invokes no events in the log but error voice message (Call not sucesfull)…
Hmm, not sure where that error comes from, do you see it everytime…
For the call , you first need to call someone, like hikconnect or indoor station… It needs to ring… Then it makes an event… Although not all devices create ringing events… So make sure you hikvision device is setup correct, so it can make calls, then have a look again if it creates an event
I have added the person and it unlocks and logs the event:
2024-01-23 17:42:06.091 | INFO | event:motion_detection:98 - Motion detected from Street
2024-01-23 17:42:06.849 | INFO | mqtt:video_intercom_event:344 - Video intercom event magnetic_door_status detected on Street
2024-01-23 17:42:06.849 | INFO | mqtt:handle_device_trigger:456 - Invoking device trigger automation{‘name’: ‘magnetic_door_status’, ‘type’: ‘event’, ‘subtype’: ‘magnetic door status’}
2024-01-23 17:42:06.850 | INFO | event:video_intercom_event:109 - Video intercom event from Street
2024-01-23 17:42:07.387 | INFO | mqtt:video_intercom_event:344 - Video intercom event authentication_log detected on Street
2024-01-23 17:42:07.387 | INFO | mqtt:handle_device_trigger:456 - Invoking device trigger automation{‘name’: ‘authentication_log’, ‘type’: ‘event’, ‘subtype’: ‘authentication log’}
2024-01-23 17:42:07.388 | INFO | event:video_intercom_event:109 - Video intercom event from Street
2024-01-23 17:42:07.902 | INFO | mqtt:update_door_entities:295 - Door 1 unlocked by 779711410110700 , updating sensor and device trigger
2024-01-23 17:42:07.903 | INFO | mqtt:handle_device_trigger:456 - Invoking device trigger automation{‘name’: ‘Door unlocked’, ‘type’: ‘door open’, ‘subtype’: ‘door 0’, ‘payload’: {‘control_source’: ‘779711410110700’}}
2024-01-23 17:42:07.904 | INFO | event:video_intercom_event:109 - Video intercom event from Street
2024-01-23 17:42:10.895 | INFO | mqtt:handle_device_trigger:456 - Invoking device trigger automation{‘name’: ‘motion_detection’, ‘type’: ‘Motion detected’, ‘subtype’: ‘’}
2024-01-23 17:42:10.896 | INFO | event:motion_detection:98 - Motion detected from Street
2024-01-23 17:42:16.783 | INFO | mqtt:video_intercom_alarm:417 - Video intercom alarm door_open_by_external_force detected on Street
2024-01-23 17:42:16.784 | INFO | mqtt:handle_device_trigger:456 - Invoking device trigger automation{‘name’: ‘door_open_by_external_force’, ‘type’: ‘force’, ‘subtype’: ‘door open by external force’}
2024-01-23 17:42:16.784 | INFO | event:video_intercom_alarm:120 - Video intercom alarm from Street
It looks I need intercom device installed first to test the call. I couldn’t manage to call to hik-connect directly without one. I think the representative noticed something like this before. Will report later.
Anyway how can I check the docker image version? To avoid to deply and configure from scratch…
Thanks a lot.
Looks promising till now.
Are you using dockerhub, with latest tag? I see in log you are running .14, that’s good…
Yeah , first setup hikconnect, and report later, I may have an alternative to poll the ring event
About that error? Do you see that every time? Can you enable DEBUG for info and SDK?
Like this:
log_level: DEBUG
sdk_log_level: DEBUG
And report only that error you see in beginning
Managed to install indoor station and set the debug levels.
Unfortunatelly I couldn’t see ring button event in the logs:
[2024-01-23 18:33:36.790][DBG] SimpleSTDCommandToDvr with out cmd[GET /ISAPI/System/IO/outputs], input size[0], max segment length[262144]
[2024-01-23 18:33:36.800][INF] Private connect 192.168.1.60:8000 sock=136 this=0xb58abce4 cmd=0x117000 port=41604
2024-01-23 18:33:36.812 | DEBUG | sdk.utils:call_ISAPI:165 - Response output:
2024-01-23 18:33:36.813 | DEBUG | mqtt:init:166 - Configuring 2 door switches
[2024-01-23 18:33:36.812][DBG] SimpleSTDCommandToDvr with out cmd[GET /ISAPI/AccessControl/RemoteControl/door/capabilities], input size[0], max segment length[262144]
2024-01-23 18:33:36.821 | DEBUG | event:register_handler:234 - Adding event handler MQTT
2024-01-23 18:33:36.821 | DEBUG | mqtt_input:init:21 - Setting up MQTTInput
*2024-01-23 18:33:36.823 | DEBUG | sdk.utils:call_ISAPI:125 - Call ISAPI request method url body: GET /ISAPI/System/deviceInfo *
2024-01-23 18:33:36.835 | DEBUG | sdk.utils:call_ISAPI:165 - Response output:
OUTDOOR STATION
xxxxxxxxxxxxxxxxx
VIS
STD-CGI
STD-CGI
DS-KV9503-WBE1
DS-KV9503-xxxxxxxxxxxxxx
xxxxxxxx
V2.3.5
build 230328
33751045
1508124
0x10101
VIS
doorStation
88
true
true
0
1
baseline
1
4
e255
[2024-01-23 18:33:36.831][INF] Private connect 192.168.1.60:8000 sock=142 this=0xb58abce4 cmd=0x117000 port=41620
[2024-01-23 18:33:36.835][DBG] SimpleSTDCommandToDvr with out cmd[GET /ISAPI/System/deviceInfo], input size[0], max segment length[262144]
2024-01-23 18:33:36.860 | DEBUG | event:start:255 - Registering callback function using SDK
2024-01-23 18:33:36.861 | DEBUG | doorbell:setup_alarm:90 - Arming the device via SDK
Exception in callback BaseSelectorEventLoop._add_reader(0, >)
handle: <Handle BaseSelectorEventLoop._add_reader(0, >)>
Traceback (most recent call last):
Hmm, that error can be ignored, I think it’s error because of reading the past events… Are you using the admin account to login?
Was your indoor station ringing and still no event?? That’s not good 
… But there is alternative, in this version, I have added an “call info” button, press on it, it should give you the status, like , idle, ring, on call …
If that works, you can maybe make a polling in openhab , to press that button every x seconds
What do you mean? How can I obtain status from “call info” button?
You can send a payload to mqtt to press that button, the same way you open the door with mqtt
Will have to deep dive into MQTT now 
you can start with mqtt explorer, you can publish topics there to see whats going on, as example, for button, the command = PRESS, if succes, you can see it in the attributes
Thanks, will check that later. Installed Doorbell at the street wall in the meantime.
Will let you know, quite busy these days…
I had to upgrade OH to v4 becasue of another binding not compatib le with v3.
There are several errors now:
At OH side:
2024-02-26 21:04:46.037 [WARN ] [core.thing.internal.ThingManagerImpl] - Failed to normalize configuration for thing ‘mqtt:homeassista nt_6883457586575348514587666949484850485051485749566978657156495251545351:d76dbc40b0:6883457586575348514587666949484850485051485749566 978657156495251545351’: {thing/channel=Type description mqtt:6883457586575348514587666949484850485051485749566978657156495251545351_2D door_5Frelay_5F0_switch for mqtt:homeassistant_6883457586575348514587666949484850485051485749566978657156495251545351:d76dbc40b0:68834 57586575348514587666949484850485051485749566978657156495251545351:68834575865753485145876669494848504850514857495669786571564952515453 51_2Ddoor_5Frelay_5F0#switch not found, although we checked the presence before.}
2024-02-26 21:04:46.037 [INFO ] [.transport.mqtt.MqttBrokerConnection] - Starting MQTT broker connection to ‘192.168.1.163’ with clien tid 18adc3c0-8aa7-4661-8448-ec86fb572010
2024-02-26 21:04:48.136 [WARN ] [ssistant.internal.DiscoverComponents] - HomeAssistant discover error: UID segment ‘688345758657534851 4587666949484850485051485749566978657156495251545351_2Ddoor_5Fnot_5Fclosed_5F0#not closed’ contains invalid characters. The last segme nt of the channel UID must match the pattern '[\w-]|[\w-]#[\w-]‘.*
2024-02-26 21:04:48.136 [WARN ] [ssistant.internal.DiscoverComponents] - HomeAssistant discover error: thing ISAPI-request component t ype is unsupported: text
2024-02-26 21:04:48.137 [WARN ] [ssistant.internal.DiscoverComponents] - HomeAssistant discover error: UID segment ‘688345758657534851 4587666949484850485051485749566978657156495251545351_2DDoor_20unlocked#door open’ contains invalid characters. The last segment of the channel UID must match the pattern '[\w-]|[\w-]#[\w-]’.*
and at docker side:
2024-02-26 19:23:52.063 | INFO | sdk.utils:loadSDK:44 - Using OS: Linux with architecture: x86_64
loop[2] find 2 mac and 0 ip
2024-02-26 19:23:52.216 | INFO | doorbell:authenticate:79 - Connected to doorbell: Street
2024-02-26 19:23:52.216 | INFO | event:init:87 - Setting up event handler: Console stdout
2024-02-26 19:23:52.216 | INFO | mqtt:init:117 - Setting up event handler: MQTT
Exception in callback BaseSelectorEventLoop._add_reader(0, >)
handle: <Handle BaseSelectorEventLoop._add_reader(0, >)>
Traceback (most recent call last):
File “/usr/local/lib/python3.10/asyncio/selector_events.py”, line 256, in _add_reader*
key = self._selector.get_key(fd)*
File “/usr/local/lib/python3.10/selectors.py”, line 193, in get_key*
raise KeyError(“{!r} is not registered”.format(fileobj)) from None*
KeyError: ‘0 is not registered’
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/usr/local/lib/python3.10/asyncio/events.py”, line 80, in _run*
self._context.run(self._callback, self._args)
File “/usr/local/lib/python3.10/asyncio/selector_events.py”, line 258, in _add_reader*
self._selector.register(fd, selectors.EVENT_READ,*
File “/usr/local/lib/python3.10/selectors.py”, line 360, in register*
self._selector.register(key.fd, poller_events)*
PermissionError: [Errno 1] Operation not permitted
Any hint please?
does it continue? i think you can ignore that message, i have seen if before , but it continues right?
Yest, it seems it is working. I can see events in container logs and item reflects the doorlock state.
I will have to check call status later then.
Hi Fabio,
Sorry for a delay, I was busy till know.
Anyway, I tried checking call state but it seems it is not working. To avoid any misunderstanding, I have installed HA as well and used directly your Add-on. The Call state is idle even when I push the call button, check the history in HA:
Any hints?
Should i switch logging to debug, or?
Thanks.
