i have 2 different pir devices from them … from version ‚a‘ i have 2
fun thing the version a has both device/type ids from below. version b shares the identical device/type id of one of the a devices
, strange…That’s definitely a bit sad and really quite poor of the supplier to do this. The ZWave certification requires -:
The Product Type ID and Product ID numbers are assigned by the
manufacturer and are intended for use in identifying and differentiating various
products from the same manufacturer. These numbers should be unique for
each device.
So, we have to work around their issue…
One option is to add the smoke notification channel into the PIR device - it will be a bit confusing though and there might be issues with configuration…
Another option is to try and use the firmware version to differentiate the two. So long as this doesn’t change, this will work for now. If they update the firmware, then we will have to revisit the problem.
I will set the version on the PIR to minimum version of 6 which should still match both the sensors from @shorty707, and the smoke sensor as only 1.36, and hopefully this will work!
@chris_me please can you update the smoke sensor database entry to correctly reflect the configuration? I’ve edited the names and versions already…
Well I would like to do that, but I have really no clue how to do it 
Please see the database guide -:
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide
@chris_me
Debug Logs of all eventy would help
However I made an educated guess and added SMOKE and TAMPER channels for the Alarms.
You must wait until the next DB update to the binding by chris. Then you should have a working smoke detector.
Please make sure to test the smoke alarm to see if it works and report here in any case.
thanks
well I deleted all things by switching to the dev/security binding
after readding my PIR sensor it is now incorrectly recognized as DP-32Z
which is not even in the database?
@chris why are devices that are (probably) deleted or overwritten in the DB still in the binding?
the DB shows only 4 different kaipulekt devices. the binding has 7
In general the database for the master and the dev version should be the same. It is possible for devices to be removed from the database but to still be in the binding though as I don’t always perform a full export. I’ll check this device when I get a chance - at the moment my internet connectivity is not so great but I’m home in a day or so (u fortunately! 
).
Hello guys, I’m trying to get working the Smoke Sensor from Kaipule. I’ve woken up the device several times, but still not recognized. Did you get it working eventually?
I just checked in the database, and it should work ok. I see you removed some device IDs - are you REALLY sure this is correct? I suspect that this should not be removed as it is quite likely to break someone elses system.
Please confirm that you know that 0004:0001 is not valid type/id for this device, and also how you confirm this.
Also, what version of OH are you using? It’s possible that this device is simply not in your version of the binding.
I just checked in the database, and it should work ok. I see you removed some device IDs - are you REALLY sure this is correct? I suspect that this should not be removed as it is quite likely to break someone elses system.
Please confirm that you know that 0004:0001 is not valid type/id for this device, and also how you confirm this.
Also, what version of OH are you using? It’s possible that this device is simply not in your version of the binding.
I confirm that 0004:0001 isn’t valid ID as it was added by me when I didn’t understand the logic of the z-wave DB. I’m using snapshot 1143 with zwave binding version 2.3.0.201804022210. In the logs I see that binding is checking it against es61_0_0 twice and once against es61_1_36
When I compare your screenshot from HABmin and mine, I see that you have SMOKE_ALARM_SENSOR in Z-Wave Plus Node type and I have NODE_TYPE_ZWAVE_PLUS_NODE. Could it be the reason why it isn’t matched?
No - this information is not used. It’s just in the database for completeness, but it’s not part of the exported files and the binding is not using it.
I’m still fighting with adding the Smoke Sensor. Using your latest binding version (2.3.0.201804222113). I have done also OH cleaning by deleting cache and tmp folders contents as it resolves some issues. Tried adding the device using HABmin and PaperUI. Woke up the device several times, let the device for a couple of days to let wake up automatically…
I’ve got a full log here, I’ve done some cleaning to get a better reading. If anyone could give some clue it would be highly appreciated.
The log starts with inclusion mode being turned on. The discovered node 41 is the smoke sensor.
You have a more recent version than is in the database. I’ll update the database to include your version - hopefully it’s fundimentally the same otherwise we’ll have to look at adding a new DB entry.
I was checking the version of the FW, but you mean some “other” version? Is there anything I should do now? Or wait for the new version with updated DB and will let know the results back.
No - I mean the firmware version. If I remember correctly, yours was 5.36 where the database was set to a maximum of 5.9).
I will update the binding in the next day or two so hopefully it will solve the problem.
1 Like
When the database was set to “All up to 5.9” it should accept the 5.36 version, or is my understanding incorrect? The database is now set to “All up to 5.255” which is wrong if my above understanding is correct.
A value of 9 is less than 36, so it is not set. You can’t use a decimal comparison - the major and minor values are handled separately in ZWave.
I’m not completely sure what your understanding is, but 255 is the highest value for the minor value - it looks ok to me.