DS-KD8003-IME1 with DS-KD-KP code support #204
Comments
|
Entering the wrong Keypad pin code got me these events: 2024-05-06 21:26:58.951 | DEBUG | event:_handle_callback:220 - Callback invoked from SDK
2024-05-06 21:26:58.952 | DEBUG | event:_invoke_handlers:192 - Invoking 2 handlers
2024-05-06 21:26:58.952 | DEBUG | mqtt:isapi_alarm:279 - Isapi alarm from Gate
2024-05-06 21:26:58.953 | INFO | event:isapi_alarm:131 - Isapi alarm from GateEntering the right code, got me these events (with the door being opened): 2024-05-06 21:25:32.635 | DEBUG | event:_handle_callback:220 - Callback invoked from SDK
2024-05-06 21:25:32.636 | DEBUG | event:_invoke_handlers:192 - Invoking 2 handlers
2024-05-06 21:25:32.637 | INFO | mqtt:update_door_entities:295 - Door 1 unlocked by 112117981081059900 , updating sensor and device trigger
2024-05-06 21:25:32.637 | DEBUG | sdk.utils:call_ISAPI:125 - Call ISAPI request method url body: GET /ISAPI/System/deviceInfo
2024-05-06 21:25:32.742 | DEBUG | sdk.utils:call_ISAPI:165 - Response output: <DeviceInfo version="2.0" xmlns="http://www.isapi.org/ver20/XMLSchema">
<deviceName>OUTDOOR STATION</deviceName>
<deviceID>DELETED</deviceID>
<deviceDescription> Vis</deviceDescription>
<deviceLocation>STD-CGI</deviceLocation>
<systemContact>STD-CGI</systemContact>
<model>DS-KD8003-IME1</model>
<serialNumber>DELETED</serialNumber>
<macAddress>DELETED</macAddress>
<firmwareVersion>V2.2.45</firmwareVersion>
<firmwareReleasedDate>build 210430</firmwareReleasedDate>
<bootVersion>33685549</bootVersion>
<bootReleasedDate>1377310</bootReleasedDate>
<hardwareVersion>0x0</hardwareVersion>
<encoderVersion>V4.0</encoderVersion>
<encoderReleasedDate>build 181206</encoderReleasedDate>
<deviceType> Vis</deviceType>
<telecontrolID>88</telecontrolID>
<supportBeep>true</supportBeep>
<supportVideoLoss>true</supportVideoLoss>
<alarmOutNum>2</alarmOutNum>
<alarmInNum>4</alarmInNum>
<RS485Num>1</RS485Num>
<customizedInfo></customizedInfo>
</DeviceInfo>
2024-05-06 21:25:32.746 | INFO | mqtt:handle_device_trigger:456 - Invoking device trigger automation{'name': 'Door unlocked', 'type': 'door open', 'subtype': 'door 0', 'payload': {'control_source': '112117981081059900'}}
2024-05-06 21:25:32.748 | INFO | event:video_intercom_event:109 - Video intercom event from Gate |
|
Hm, it should be an intercom event, not an isapi one... |
|
Here is the isapi event SDK, not much usefull info... https://open.hikvision.com/hardware/structures/NET_DVR_ALARM_ISAPI_INFO.html |
|
Here is the event SDK, only card access is logged, not keypad :-( |
|
Nope, no badge reader, only keypad.
This is the only events that happened when i used the keypad.
I didn't see it on the SDK, i saw that control4 was able to integrate it
somehow.
…On Mon, May 6, 2024, 21:47 Pergola Fabio ***@***.***> wrote:
Hm, it should be an intercom event, not an isapi one...
Do you also have a badge reader? I added an illegal swipe event, there is
one in the SDK for that...
But I don't think there is an illegal keypad entry
—
Reply to this email directly, view it on GitHub
<#204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPRV3R2XKESSKQGQ4MB2NDZA7F3RAVCNFSM6AAAAABHJORXICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWGY4DKOBWGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
https://automatednow.com/index.php?dispatch=attachments.getfile&attachment_id=1145 "The driver will fire the Keypad - Valid Password or Keypad - Invalid Password Event when a code is entered. " Now I know it doesn't really help, just shows that it is possible. |
|
do you know if that is based on SDK or ISAPI directly to port 80 ? |
|
if you use ivms, do you see the event there? |
|
Since I'm using an NVR I need to connect the PC to the internal network of the NVR, I will try tomorrow to verify. Also from the NET_DVR_ALARM_ISAPI_INFO: Not sure that I understand it correctly but it seems like there is more data there to be obtained, even though it is weird that it is ISPAI event. |
|
yeah, that isapi alarm is more for cameras, not intercoms |
No Idea, never had control4 system or tried it. |
"If PIN entered does not even show up in iVMS-4200 but card scan does, it is likely due to PIN format being accidentally toggled. Follow instructions in the sheet manual, power cycle the reader, and scan the Data Mode card once to toggle it back to 4-bit burst and try again." from the manual it seems like maybe Hikvision is using cards and keypad as the same integration? |
|
hmm, i dont think those setting are for 8003 ? i also have an ds-kd8003 btw |
Ok, Using the IVMS I can see the event when I press the wrong key - Authentication error. |
|
Hm, strange that it doesn't create that event using the SDK :-( |
I think we get it an ISAPI with a payload that we need to read. |
|
So as you can see in the attached file: |
|
hmm, your previous reply seems empty about the isapi ? can you pots that again? do you always see the isapi event with unknnown key code? then its indeed worth investigating! |
|
Everytime i pinch the wrong pin code, i get: event:isapi_alarm:131 - Isapi alarm from Gate |
|
Hmm, i tried it on mine ds-kd8003, and i receive below |
|
I just pushed beta 62, added some more isapi data in debug , can you test? i have no idea what it will show... |
DS-KD8003-IME1 |
Do I need to uninstall the stable version first? |
|
no need to uninstall, but just stop the addon , thats enough, then install beta addon, copy/paste the config |
thats indeed an old firmware, i'm running : V2.2.62 build 230204 |
|
also setup both to DEBUG:: |
2024-05-08 21:52:41.664 | DEBUG | mqtt:isapi_alarm:277 - Isapi alarm from Gate with Alarmdata: b'0'
2024-05-08 21:52:41.664 | INFO | event:isapi_alarm:131 - Isapi alarm from Gate |
|
hmm , not really helpfull :-) |
|
Been browsing the ClientDemo code,
|
|
i checked mine DS-KD8003 , its giving an NET_DVR_VIDEO_INTERCOM_ALARM and not an COMM_ISAPI_ALARM one on invalid keypad entry the alarmtype in my case is 0 instead of the ones listed https://open.hikvision.com/hardware/structures/NET_DVR_VIDEO_INTERCOM_ALARM.html |
|
and those screenshots they send you is the alertstream, you can see an example here: but that alertstream i have never seen it working on Intercoms, its for cameras |
|
I think i have some progress on this. Attached screenshot of invalid card on KD8003-B |
|
ah, thats interesting? what did you do ? |
|
And here is the JSON I get if I try to enter an invalid code on the DS-KD-KP module |
I think |
|
do you have the code running, can you share it? |
|
or can you submit a PR ? |
|
Changed class NET_DVR_ALARM_ISAPI_INFO(Structure):
fields = [
("pAlarmData", POINTER(char)),
("dwAlarmDataLen", DWORD),
("byDataType", BYTE),
("byPicturesNumber", BYTE),
("byRes", BYTE * 2),
("pPicPackData", NET_DVR_ALARM_ISAPI_PICDATA),
("byRes2", BYTE * 32),
]And then we can read data string at pAlarmData location via async def isapi_alarm(
self,
doorbell: Doorbell,
command: int,
device: NET_DVR_ALARMER,
alarm_info: NET_DVR_ALARM_ISAPI_INFO,
buffer_length,
user_pointer: c_void_p):
pAlarmData = alarm_info.pAlarmData
alarmDataLen = alarm_info.dwAlarmDataLen
byDataType = alarm_info.byDataType
alarmDataBuffer = ctypes.string_at(pAlarmData, alarmDataLen) |
|
Still, need to check if data type is xml, since |
|
I hope these events are documented somewhere, dont think they are the same as below: https://open.hikvision.com/hardware/structures/NET_DVR_ACS_ALARM_INFO.html |
|
Im not sure. Just checked their SDK client demo and docs for it, not found anything really |
|
MINOR_INVALID_CARD | 0x09 This one is in my SDK, but the event 150 is not , i can just add it, those docs are not always up to date |
|
hey @Khyonox , what firmware do you have on your 8003 ? Probably an older one? mine doesnt give the ISAPI alarm :-( |
Interesting, im using V2.2.76 build 240226 |
|
2.2.72 ? where did you download it? i'm on 2.2.62 , and i see its the latest one here? |
|
Just did a firmware update, now using V2.2.76 build 240515. Still sends the ISAPI alarm 🤔 |
https://www.hikvision.com/en/support/download/firmware/
|
|
the ISAPI alarm is good but mine sends an EVENT alarm with type 0 ... , seems it was working on 2.2.45 according to @AYahoo , but he also upgraded to 2.2.62 , and receives the same EVENT as me we are using rev A models, 2.2.62 is the latest :-( , maybe a bug in our firmware |
|
i have build : V2.2.62 build 230204 and it seems its the latest one |
|
If you can make it work with the ISAPI I'm willing to degrade to 2.2.45. |
|
we should move upwards, you guys had contact with Hikvision right? Can you ask if this is a known bug in 2.2.62 (rev A) ? since it was working an previous release 2.2.45... Also tell it works in 2.2.72 (rev B) |
|
Just did, this is the ticket:
"Hi, We are facing a problem with the module of DS-KD-KP, and DS-KD8003-IME1, Since upgrading from version 2.2.45 to version 2.2.62.
With the old firmware, we got an ISAPI event on bad pin code enter. but with the new version, 2.2.62 we get a response of alarm type 0 which is not supported according to the SDK (https://open.hikvision.com/hardware/structures/NET_DVR_VIDEO_INTERCOM_ALARM.html).
From other users we got that on DS-KD8003-IME1 REV B they have a newer firmware 2.2.72 and the behavior is fixed and they get ISAPI event.
Is it a BUG in the firmware? are we doing something wrong? "
…On Wed, Jun 5, 2024, 10:08 Pergola Fabio ***@***.***> wrote:
we should move upwards, you guys had contact with Hikvision right? Can you
ask if this is a known bug in 2.2.62 (rev A) ? since it was working an
previous release 2.2.45...
Also tell it works in 2.2.72 (rev B)
—
Reply to this email directly, view it on GitHub
<#204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPRV3SPYITHCSCDFOAW2ILZF22P3AVCNFSM6AAAAABHJORXICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBZGA2DCMRYGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
This i the replay, Do you use ISAPI to get the event from KD8003, but get the alarm type 0? @pergolafabio Could you please help with the response? |
|
Hey, you can say we are using SDK and listining for lCommand https://open.hikvision.com/hardware/definitions/NET_DVR_StartListen_V30.html For the invalid key code, we are receiving this:
With : byAlarmType => 0 We should receive this instead:
For the unknown badge , in my case i dont receive any event at all , while @Khyonox does receive the event |
|
Do you have some updates? |
|
Yeah, just got a response: Hello, I think it is a bug as you described. |
|
Ok, that's good news, if they confirm it as a bug ;-) Hopefully you can get them going to create a new firmware |
|
Got some updates? |
Is there an existing feature request for this?
Add-on
None
Your feature request
DS-KD-KP, is a numeric pad with a access control code to open relays on the KD8003, I would love to have the ability to know which user entered and if the wrong password has been pressed to know if someone is trying to mess with the code, guess it, or just playing with it. I'm sure I saw it on the SDK in the past.
The text was updated successfully, but these errors were encountered: