-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for additional devices and functions #14
Comments
Would be interesting. Lot of potential..
I will get later in to it and implement those |
I added endpoints to hikaxpro (fork) waiting for some pull requests |
Thanks will wait for pull :) |
I have the following products already installed in addition to the repeater. sirens: tag readers: wireless keyfob: I also installed the 2 magnetic contacts wired coupled with the radio contacts of the doors |
You can test if devices which I and Peter don't have to test ... Does sensos which are connected over repeater in HA show "Is via repeater" True? You can compare and check in HIK Connect which sensor use repeater... I can't test this so not sure if work correctly... |
It is just about time and priorities. I am working on this in my spare time. Currently I have done some research but I’m waiting on the pull request. As @DejanBukovec said you can test stuff. But because you request it then obviously you are going to test it anyway. |
HI,
I'm available if you need debug just tell me |
@DejanBukovec Today with version v0.8.0 i added mutliple detector types including @leciuk81 for you for your "door sensors" and additional wired contacts. Do you mean "wired sensors" or in some sensor are contact to wire ? Can you provide log ? enable debugging and find part of the log with the "name" matching the one which is missing those contacts. |
But does not it need to be included also inside detector_model_to_name function? Or in latest versions this in not mantadory anymore? Best will be if he provide full log file with Zone details it can be any of not complete implemented attribute... But without debug log from HA is only guessing... |
@DejanBukovec Most of the attributes converted to enums are in |
@DejanBukovec - I updated to the latest version and I confirm what you said that all detectors are in HA except for the trigger. @petrleocompel - by wired contacts I mean these: below part of the debug log:
|
Strange that is not even in documentation.
|
I think the trigger will not be present in attributes. It is same as #2. It is more "event". Not a attribute or in app you can see in device detail (in hikConnect) that contact is triggered? |
@petrleocompel I think you are right, I don't see the trigger in hikConnect either |
I think but Im not test this yet when some sensor trigger when alarm panel is armed value of "Alarm" under diagnostic of sensor will change from Off to On ... When you confirm alarm(Disarm or confirm) or maybe also after some time it will automaticly reset to Off(Im not sure about this timer reset but if remember correct there under sensor is some option to enable/disable this)... |
@DejanBukovec behaviour should be:
Problem is.. Since we are pulling the data the alarm we don't see instantly. It is in "pull interval" (default 30s). And then we can find out what sensor it was if you did not disarm the system yet. This can be changed but it requires configuration on AX Pro to sent the events to the HA. It would be amazing.
|
Hi @petrleocompel, Would you be able to make visible also the wired magnets of the "Wireless External Magnet Detector DS-PDMCX-E-WE" which as you see from the screenshots below is visible but the magnet is not activated. You are doing a great job congratulations and thanks |
Can you provide debug log ? On integration enable debug logging wait 2 minutes, end debugging and provide the log. I will add support for this magnet initializiation |
Are you on latest version?
But it should not affect magnet. Can you check your version ? |
This works correctly:
But this doesn't work:
|
I understand. But as you see {
"id": 19,
"name": "Cassettina sali-scendi serranda (zona 20)",
"status": "online",
"sensorStatus": "normal",
"tamperEvident": false,
"shielded": false,
"bypassed": false,
"armed": true,
"isArming": false,
"alarm": false,
"subSystemNo": 2,
"linkageSubSystem": [2],
"detectorType": "other",
"stayAway": false,
"zoneType": "Instant",
"accessModuleType": "inputMainZone",
"relatedAccessModuleID": 15,
"moduleChannel": 1,
"zoneAttrib": "wired",
"deviceNo": 39,
"abnormalOrNot": false
} The system is not providing |
If understand what is happening now. If it is a wired detector. there is no more info provided. |
I understand but I'll give you more information. Debug home-assistant_hikvision_axpro_2023-03-12T13-53-46.320Z.log |
You can check on your own. In debug log I see the device. But no extra attributes. And they are wired. So they act as "cable interruptions" for alarm and not providing any information to alarm system. It is not a data cable. It is just a "contact cable" for alarm. I have serval wired sensors like this. And it is not possible to get anything on them. |
Sorry but perhaps the use of the translator prevents me from expressing the clear concept. |
I am getting totally lost @leciuk81. So
So this info is not sent to any app. Only in configuration of that sensor you can set If you mean something else please try to describe from scratch full story, fully documented, (app screenshots) where you see info what you miss in HA. |
So DS-PDMCK-EG2-WE has 2 wired inputs extension. According to documentation they act as alarm triggers. You can add two external inputs (each input can be set as NO\NC\TAMPER\Pulse) via the AX PRO client. So this info is not sent to any app. Only in configuration of that sensor you can set NO\NC\TAMPER\Pulse. All of this is correct These are the 2 contacts wired with the 3 wires zone 1, zone 2 and com This is an example by wiring zone 1 only In home assistant the wired contact is seen like this: The contact in home assistant looks like this: This all works great. If you see in the screenshot of zone 2, nothing is displayed in home assistant even though it is enabled. |
In your log I think the |
@DejanBukovec I took over pypi package of hikaxpro, released update version 2.0.0 and now I am maintainer of that repository. My work can finally start. Since we have full control over the package.
Now I can focus on more stuff which we can implement. First I guess will be end point with Sirens, then relay control. And etc. Everybody is welcome to say what things are important and we can try prioritise. |
Hi, |
I didn't try URL's but it must look like: Afcourse before this I think you need estabilish session... |
@NickCDevel Just warning that basic API connection should be done via hikaxpro library and this (repo) integration should just do the binding for HA. The document matches the current ISAPI so far always. You are welcome to make a pull request. |
Hi, |
Thank you very much for these clarifications. I will think about pulling a request. |
hi @petrleocompel, first of all, congrats on the nice work! everything is working correctly but my PIR sensors "Wireless Dual-Tech Detector" (DS-PDD12P-EG2-WE(B)) are giving a "wrong" name: '0x00002'. can you change this please? thanks in advance! |
@Joerivanrokeghem fixed in v2.0.0-beta17 |
I've recently added the DS-PM1-I1-WE input transmitter (to add external contact sensor) https://www.hikvision.com/en/products/Alarm-Products/wireless-intrusion-alarm/ax-pro/ds-pm1-i1-we/ but once added the integration would fail to reload giving this error. Can it be added (or at least ignored) so that the integration would load correctly?
|
@r0bb10 fixed |
Perfect, tested and works! quick debug just to clean up things:
Btw great work as usual! |
Normally we get {
"id": 0,
"zoneName": "Contatto Porta",
"detectorType": "magneticContact",
"zoneType": "Delay",
"subSystemNo": 1,
"linkageSubSystem": [1],
"supportLinkageSubSystemList": [1],
"enterDelay": 30,
"exitDelay": 1,
"stayArmDelayTime": 1,
"sirenDelayTime": 0,
"stayAwayEnabled": false,
"chimeEnabled": false,
"silentEnabled": false,
"chimeWarningType": "single",
"timeoutType": "recover",
"timeout": 30,
"relateDetector": true,
"RelatedChanList": [{
"RelatedChan": {
"relator": "app",
"cameraSeq": "",
"relatedChan": 0,
"linkageCameraName": ""
}
}],
"doubleKnockEnabled": false,
"doubleKnockTime": 5,
"CrossZoneCfg": {
"isAssociated": false,
"supportAssociatedZone": [1, 2],
"alreadyAssociatedZone": [],
"supportLinkageChannelID": [],
"alreadyLinkageChannelID": [],
"associateTime": 1800
},
"newKeyZoneTriggerTypeCfg": "zoneStatus",
"zoneStatusCfg": "triggerArm",
"armNoBypassEnabled": false,
"RelatedPIRCAM": {
"supportLinkageZones": [],
"linkageZone": [],
"linkagePIRCAMName": ""
},
"finalDoorExitEnabled": false,
"timeRestartEnabled": false,
"armMode": "and",
"swingerLimitActivation": 3,
"detectorWiringMode": "SEOL",
"detectorAccessMode": "NC",
"antiMaskingEnabled": true,
"AMMode": "arm",
"AMDelayTime": 60,
"pulseSensitivity": 250,
"alarmResistence": 2.2,
"tamperResistence": 2.2,
"moduleChannel": 1,
"doubleZoneCfgEnable": false,
"accessModuleType": "localTransmitter",
"zoneAttrib": "wired"
} So I do not think it is possible. Also for wired sensors it is not real to report anything. You can wire anything to these contact. Custom made stuff, different brands wired sensors, magnetic, PIR, etc... The naming scheme with "zone / channel" maybe. But you have the name and reality is .. that the sensor is unknown. |
can u add 0x00031 to the integration please? it is the DS-PDCO-E-WE Wireless CO Detector. |
@Joerivanrokeghem I quickly added the model to be recognized but I kinda do not know how to get info from that device. I do not know what happens when it would be triggered. |
hi petr, I updated to v2.0.2 and restarted the integration/ HA but the model is still displayed as 0x00031. when I have the time I will test what attribute will change. but I think it will be the same attributes as by the smoke detectors. |
@Joerivanrokeghem - fixed it in release v2.0.3 I overlooked the number |
We can make this integration very close to what HIK connect offer and what API allow us to do...
For example for PIRCAM sensor we can get picture from it:
GET /ISAPI/SecurityCP/pircam/picture/channels/?format=json
One good feature will be AC status of panel:
GET /ISAPI/SecurityCP/status/acPowerStatus?format=json
And battery status:
GET /ISAPI/SecurityCP/status/batteries?format=json
Or maybe using next call to get more info(Also network...)
GET /ISAPI/SecurityCP/status/host?format=json
There are availible also next Sensors which are currently not implemented(I don't have model ID for them):
glassBreakDetector - PIR (Passive Infrared) glass-break detector
indoorDualTechnologyDetector - Indoor dual-technology detector
panicButton - Panic button
wiredDetector - Wired detector
If you can implement support also for other(non sensor/detector) devices to change some settings it will be awesome:
wirelessSiren - For example change volume, show temperature, battery, signal, bypass, tamper status
GET /ISAPI/SecurityCP/status/sirenStatus?format=json
repeaters - Show if is ONLINE/OFFLINE
GET /ISAPI/SecurityCP/status/repeaterStatus?format=json
keypadStatus - Show temperature, battery, signal, bypass, tamper status
GET /ISAPI/SecurityCP/status/keypadStatus?format=json
For siren(Internal siren) and keypad(DS-PK1-LT-WE) I can be tester because I have them installed.
Let me know if you don't have access to Hikvision documentation that I provide more info...
The text was updated successfully, but these errors were encountered: