hmm, not sure if the door source is also in the event log, i think only who opened it …
but lets wait for this evening…
os.system("echo Unlocked by: " + str(list(alarminfo_upload_video_intercom_event.uEventInfo.struUnlockRecord.byControlSrc)))
1 Like
ok when come back i test it
but how i can create button in HA with this service:
service: hassio.addon_stdin
data:
addon: a53439b8_hikvision_sdk
input: unlock1
create a templae switch, with the turn_on service
but what for turn_off ?
nothing 
Hi
On my VideoIntercom 1 generation model DS-KH8102IM with FW 1.5.1 all works perfect. Door 1 unlocked OK and Door2 (gateway) also unlocked OK.
Status door open works ok but the same for door1 and door2 , but should be two other sensors.
Sensor motion in my model no working.
Also Call status no working for me. Still show OFF.
Logs when open first DOOR1 and then DOOR2:
Hikvision SDK Add-on started! Listening for events...
loop[2] find 8 mac and 16 ip
Trying to unlock door 1... Stdin message: unlock1
Door: 1 unlocked by SDK!
Door unlocked, trying to update: sensor.hikvision_door
Unlocked by: [97, 98, 99, 100, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
Trying to unlock door 2... Stdin message: unlock2
Door: 2 unlocked by SDK!
Door unlocked, trying to update: sensor.hikvision_door
Unlocked by: [97, 98, 99, 100, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
Logs for call status i dont find… only for door.
Unlock door works faster then by cloud integration. And by cloud status call works ok.
In addon good will be if you can add changelog version…
Also on version 2,4 no working callstatus.
I see that you add still image but how use it from your addon ?
yeah, dont think callstatus is possible with your model and the SDK
that unlocked by … thats somekind of keycode/badge, i will use that info in the attribute now of the doorsensor, could be usefull, so you can see in HA who opened the door
will try to get the doorid lock also later
And no any chance to run callststus for me…? 
i have no idea how, seems your device is just not sending the state of the call
then offource it cant be intercepted …there is not even an unhandled call in your log
But in integration by cloud from Thomas i have callstatus.
Yes, that’s a totally different protocol , it’s not based on ISAPi/SDK… It’s based on hikconnect api
ehhhh no good for me 
can you try upgrading to 2.7 , and open the door, have a look at the log, do you see the doorID there?
you should see : , hopefully we see the other door id also
its already present now as an attribute on the sensor, have fun with it
Ok try
Hikvision SDK Add-on started! Listening for events...
loop[2] find 8 mac and 16 ip
Trying to unlock door 1... Stdin message: unlock1
Door: 1 unlocked by SDK!
Door unlocked, trying to update: sensor.hikvision_door
DoorID : 8963
Unlocked by: [97, 98, 99, 100, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
Trying to unlock door 2... Stdin message: unlock2
Door: 2 unlocked by SDK!
Door unlocked, trying to update: sensor.hikvision_door
DoorID : 9219
Unlocked by: [97, 98, 99, 100, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
Trying to unlock door 2... Stdin message: unlock2
Door: 2 unlocked by SDK!
Door unlocked, trying to update: sensor.hikvision_door
DoorID : 9475
Unlocked by: [97, 98, 99, 100, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
verry strange
i get always doorid : 0
works for me
no idea where those numbers are coming from
Ok thanks for your works.
no problem, hopefully you can do something with it
too bad you need the cloud for the callstatus
maybe firmware update on your outdoor station? what type and firmware do you have?