Yes, thanks, I installed this integration, but it does not pull up these sensors and relays.
Alarm inputs, are device triggers, you can see them with mqtt, see a few posts back how to integrate a device trigger…alltough aa discussed on GitHub, they always send id 0
Alarm outputs, they are not possible with sdk,for some reason, they don’t give status
Door relays, are no issie
A new firmware has appeared, if I throw off the magazine, take a look, is there any progress there, maybe changes have appeared?
1 Like
Do you know if they’ll release a firmware to fix the snapshot support on the DS-KV6113-WPE1(B)?
1 Like
i have no idea, i’m just a user as you , i only have the ds-kd8003 
1 Like
Somewhere they wrote that it seems to be in the latest firmware, play around with the settings.
There, it seems, they even added arming in the hik connect application.
By the way, arming and disarming for kv6113 and kh6320 appeared in the application. Maybe now it is possible to identify alarm outputs?
Just check the addon log if it’s exposed now
I have exhausted every single menu and sub menu on the web interface and the hikconenct app. and have not found anything about it.
I wonder if its geolocked?
I tried all Snapshot URL formats mentioned before and all of them give me 403 bad request.
im currently analyzing the ha add-on code to see how can I get motion events from the device on my own, because I can’t use the add-on until it can’t connect to other MQTT brokers.
For now you can use it as standalone container, that gives the possibilities to connect to another mqtt server
1 Like
I believe 8003 model is the only model with a firmware release to capture snapshots… But in HA there are possibilities to make snapshot using ffmpeg and the rtsp stream, it was posted before
Hey guys, something complete off topic, but I’m having on my DS-KV6113-WPE1(B) and my indoor unit DS-KH6320-WTE1.
If I try to unlock a door using the NFC key, sometimes, it took a boring time to definitely unlock the door. The same happen with indoor unit, where I need to press and wait few seconds until the doorbell indeed unlock door.
The weird part is unlocking using Fabio’s add on is immediate!
I already made an hard reset on my doorbell, changed my NFC tags and even hardwired my indoor panel, but the problem continue. I’m using V2.2.2 build 221129 on indoor panel with V2.2.53 build 220816 with outside unit (6113)
Anyone experienced it? If so, how you fix that?
I have seen this before on other forums:
1 Like
Yes, thats correct, all events are logged as a device trigger, not seperate sensors anymore
The trigger is already there, everything is a device trigger now, everything exposed by SDK, is exposed in device trigger
Here is an example, you already asked before
hi all - just installed the addon and have configured an automation to stop the doorbell ringing when the door opens as i already had a zigbee contact sensor on the door! well done to the developer and thank you!
i’m using DS-KD8003 as the outdoor station and two DS-KH6320 for indoor stations.
2 Likes
Great! Glad to hear that everything is working! 
Maybe we can provide some example uses cases as blueprint templates for the most common scenarios, so a user can have an idea of the possible automations that could be achieved… 
Hold on you to your excitement because the beta is graduating to stable very soon 
!
2 Likes