according to SDK info :
*wLockID*
(For VTO, 0-represents the lock connected to the local controller, 1-represents the lock connected to the external controller)
that should be the one, so no idea why its always a different nr for you
according to SDK info :
*wLockID*
(For VTO, 0-represents the lock connected to the local controller, 1-represents the lock connected to the external controller)
that should be the one, so no idea why its always a different nr for you
Ehh first generation is very very bad…
yeah, lets hope or more succes for the callsensor
btw, do you see the lockID when you use the cloud integration?
hey @pepeEL
good and bad news
bad news, @grimpy tested also his device => no call state either in the SDK
But i think how ivms is doing it, my guess is using the SDK to send isapi directly to the device, so ivms is polling it also… that ivms is build with the SDK too… so creating a command to inject an ISAPI should be possible, so we can poll it from the add-on
i’m quite sure how ivms is doing that…
When you have ivms open, and you press the doorbutton, do you see the state instant changing in ivms? or is with a small delay like 1-2-3 sec? probably some polling setting
By cloud not show this door sensor.
Today i install IVMS-4200 and now i dont see to talk by IVMS from PC and show statuc call… Hmmmm Maybe it was removed in some new version ? I check it yesterday in my work because i have there other version and it works on this version.
Yeah, every version is always different
I never noticed it in ivms
Ok i dont know , now in latest version IVMS when door ringing it no show status ring in IVMS. I can talk by IVMS but no show call status.
About one year ago in IVMS show call status. Maybe good option will be ask HikVision to tell us how it is in SDK ?
ANd @grimpy also dont have any solution how get callstatus in old model ? Maybe you can write to Hikvision maybe he can help you…?
Indeed… Writing to hikvision is not going to help, the devices are EOL , they are not going to make new firmwares, … Especially not for feature request…
But we have an option left, we try the SDK to send ISAPi stuff to your device, that should work, then you will have you callsensor
ok i am waiting for update and instruction how to test and get you logs
it will take some time, i cant find any good example in python code how to send an ISAPI trough SDK
Ok no problem i believe in you
ty
i’m quite sure it will work
i think ivms is doing it the same way, i have no other clue otherwise
script is ready, for me it works, lets hope for your device too…
download this a zip file , you can use windows, i included also new lib
there is a file : hik_isapy.py , change line 13 with your correct IP / password of your door intercom device
then just run it like i do :
lets hope you see like this:
ok when come back to hom e i try it and give you and info.
lets hope you dont see nr “23”, instead of “1”
if you see “23” , then its game over for you
i tested it in my work with the same model:
J:\Hikvision-SDK-Addon-main\hikvison-sdk>python hik_isapi.py
0
b''
b''
23
J:\Hikvision-SDK-Addon-main\hikvison-sdk>
ok, game over
23 means > not supported
oh no fu… ehhhh fu… hikvision