Openhab 2.1 is running and all devices are working with exception of Kaipule Smoke Sensor.
I’ve uploaded already the .xml on cd-jackson database, but there seems to be a problem, openhab problem?
The admin said not to start a conversation there, but to ask on this forum.
Here’s the Link of the device with all the comments below.
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/559
Anyone an idea how to get it working?
The issue with these devices seems to be confusion about the device type/IDs. From teh various discussions, it seems like there could be reuse of device type/id in different devices, and if this is the case, it means devices can not be differentiated.
It would be good to try and work out what the different device IDs are for the different devices and we can then then look at the changes in the database.
I have couple of Kaipule devices. They basically seem to use the same board in different housings and versions.
Can you post the XML here?
They should have different IDs though (I hope)? If not, that is a big problem and I’d be surprised if they do this (I’m pretty sure it’s against the ZWave specification which requires each device to have different IDs).
for the PIR I have some with different housings which have the same type/id … that manufacturer is a pain…
I bought the PIR because they run on standard AA batts; the devices work well.
when the link from above is really for a smoke sensor
they even use the same Type/ID for PIR and SMOKE 
however the device from @chris_me should be resolved to device I added in the DB then
the general kaipule device 
http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/667
Well strange thing, I changed my server a few days ago, I just took a look to download the nodeXX.XML and the smoke sensor wasn’t there.
So I did a new inclusion, paperUI says node16, but when I look under /var/lib/openhab2/zwave there’s no node16.XML.
However paperUI and Habmin say that the Z-wave node 16 is there and online, obviously as unknown device as it is not in the database.
Right now I can’t upload the .XML
I checked on my old server and found it there:
<node>
<deviceClass>
<basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>SENSOR_NOTIFICATION</genericDeviceClass>
<specificDeviceClass>NOTIFICATION_SENSOR</specificDeviceClass>
</deviceClass>
<homeId>0xd477a917</homeId>
<nodeId>10</nodeId>
<version>4</version>
<manufacturer>0x214</manufacturer>
<deviceId>0x2</deviceId>
<deviceType>0x2</deviceType>
<listening>false</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<nodeInformationFrame>
<commandClass>ZWAVE_PLUS_INFO</commandClass>
<commandClass>SENSOR_BINARY</commandClass>
<commandClass>WAKE_UP</commandClass>
<commandClass>BATTERY</commandClass>
<commandClass>VERSION</commandClass>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<commandClass>ALARM</commandClass>
<commandClass>ASSOCIATION</commandClass>
<commandClass>ASSOCIATION_GROUP_INFO</commandClass>
<commandClass>POWERLEVEL</commandClass>
<commandClass>DEVICE_RESET_LOCALLY</commandClass>
</nodeInformationFrame>
<supportedCommandClasses>
<entry>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<manufacturerSpecificCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>532</deviceManufacturer>
<deviceType>2</deviceType>
<deviceId>2</deviceId>
</manufacturerSpecificCommandClass>
</entry>
<entry>
<commandClass>ASSOCIATION</commandClass>
<associationCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<maxGroups>2</maxGroups>
</associationCommandClass>
</entry>
<entry>
<commandClass>BATTERY</commandClass>
<batteryCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<batteryLevel>96</batteryLevel>
<batteryLow>false</batteryLow>
<isGetSupported>true</isGetSupported>
</batteryCommandClass>
</entry>
<entry>
<commandClass>POWERLEVEL</commandClass>
<powerLevelCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<powerLevel>0</powerLevel>
<powerTimeout>0</powerTimeout>
</powerLevelCommandClass>
</entry>
<entry>
<commandClass>ASSOCIATION_GROUP_INFO</commandClass>
<associationGroupInfoCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<autoSubscribeGroups>
<int>1</int>
</autoSubscribeGroups>
</associationGroupInfoCommandClass>
</entry>
<entry>
<commandClass>DEVICE_RESET_LOCALLY</commandClass>
<deviceResetLocallyCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</deviceResetLocallyCommandClass>
</entry>
<entry>
<commandClass>ALARM</commandClass>
<alarmCommandClass>
<version>4</version>
<instances>1</instances>
<versionSupported>4</versionSupported>
<alarms>
<entry>
<alarmType>SMOKE</alarmType>
<alarmState>
<alarmType>SMOKE</alarmType>
<reportedEvents>
<int>1</int>
</reportedEvents>
<outer-class reference="../../../.."/>
</alarmState>
</entry>
<entry>
<alarmType>BURGLAR</alarmType>
<alarmState>
<alarmType>BURGLAR</alarmType>
<reportedEvents>
<int>3</int>
</reportedEvents>
<outer-class reference="../../../.."/>
</alarmState>
</entry>
</alarms>
<v1Supported>true</v1Supported>
<isGetSupported>true</isGetSupported>
</alarmCommandClass>
</entry>
<entry>
<commandClass>SENSOR_MULTILEVEL</commandClass>
<multiLevelSensorCommandClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
<sensors>
<entry>
<multilevelSensorType>LUMINANCE</multilevelSensorType>
<multilevelSensor>
<sensorType>LUMINANCE</sensorType>
<initialised>true</initialised>
</multilevelSensor>
</entry>
</sensors>
<isGetSupported>true</isGetSupported>
</multiLevelSensorCommandClass>
</entry>
<entry>
<commandClass>ZWAVE_PLUS_INFO</commandClass>
<zwavePlusCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<zwPlusVersion>1</zwPlusVersion>
<zwPlusRole>6</zwPlusRole>
<zwPlusNodeType>0</zwPlusNodeType>
<zwPlusDeviceType>0xc01</zwPlusDeviceType>
<zwPlusInstallerIcon>0xc01</zwPlusInstallerIcon>
<isGetSupported>true</isGetSupported>
</zwavePlusCommandClass>
</entry>
<entry>
<commandClass>VERSION</commandClass>
<versionCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<libraryType>LIB_SLAVE_ROUTING</libraryType>
<protocolVersion>4.5</protocolVersion>
<applicationVersion>1.36</applicationVersion>
<hardwareVersion>255</hardwareVersion>
</versionCommandClass>
</entry>
<entry>
<commandClass>WAKE_UP</commandClass>
<WakeUpCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<targetNodeId>1</targetNodeId>
<interval>43200</interval>
<minInterval>1800</minInterval>
<maxInterval>432000</maxInterval>
<defaultInterval>43200</defaultInterval>
<intervalStep>60</intervalStep>
<lastWakeup>2017-11-26 10:08:55.300 UTC</lastWakeup>
<isGetSupported>true</isGetSupported>
</WakeUpCommandClass>
</entry>
<entry>
<commandClass>NO_OPERATION</commandClass>
<noOperationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</noOperationCommandClass>
</entry>
<entry>
<commandClass>SENSOR_BINARY</commandClass>
<binarySensorCommandClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
<isGetSupported>true</isGetSupported>
<types/>
</binarySensorCommandClass>
</entry>
<entry>
<commandClass>BASIC</commandClass>
<basicCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</basicCommandClass>
</entry>
<entry>
<commandClass>APPLICATION_STATUS</commandClass>
<ZWaveApplicationStatusClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
</ZWaveApplicationStatusClass>
</entry>
</supportedCommandClasses>
<securedCommandClasses/>
<associationGroups>
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<name>Lifeline</name>
<profile1>0x0</profile1>
<profile2>0x1</profile2>
<commands>
<commandClass>BATTERY</commandClass>
<commandClass>ALARM</commandClass>
<commandClass>SENSOR_BINARY</commandClass>
<commandClass>BASIC</commandClass>
</commands>
<associations/>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<name>Sensor Basic Set</name>
<profile1>0x20</profile1>
<profile2>0x1</profile2>
<commands>
<commandClass>BASIC</commandClass>
</commands>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<nodeNeighbors/>
<lastSent>2017-11-26 10:08:56.303 UTC</lastSent>
<lastReceived>2017-11-26 10:08:56.364 UTC</lastReceived>
</node>
The lack of a node XX file is not related to the database - the file will be generated even if the device is not in the database. Given that the database entries are created from these XML files, this is a necessity.
The most likely reason is that the device has not been woken up for the binding to complete the initialisation.
it should be discovered as for this manufacturer + device + type there is an entry in the DB
however it is a PIR …
I can assure you that it is a smoke sensor, not a PIR ;).
But why can’t I find it as node16.xml? On my old server it was discovered as node10.xml, however it was not recognized by the database, it was an unkown device.
I see what I can do to wake it up, but I don’t think that openhab will suddenly recognize it then.
It should be detected as the DP-32 / IX-30 / IX-32 as @shorty707 said.
What version of the binding are you using? Is it the snapshot or another version?
Openhab 2.1.0-1 (release build). I installed it 5 days ago on my new server via openhabian.
Ok, that’s why it’s not detected then. The device is only in newer versions of the binding (it was added in August).
So when I install openhab 2 unstable via openhabian, the device will be detected? Or do I need an other version?
I guess that “unstable” means “snapshot”, but I don’t know what environment you’re running to be 100% sure. But yes, if you run the snapshot branch, then it will be detected…
Of course, it will be detected incorrectly at the moment as the device IDs that are used to identify a device are inked to the IX32 device.
yes that will be openhab 2.2 snapshot, I just checked.
You were absolutely right, I’m runnung now 2.2 snapshot, it is detected as DP-32/ IX-30/IX-32 PIR sensor.
And the node16.xml is also present now.
So now back to the begining, what can I do to make it work as a smoke sensor ? 
Or how can I “provide a debug log of an smoke alarm to see if the correct TYPE of alarm is triggered” as @shorty707 suggested?
Here’s the actual xml file:
<node>
<deviceClass>
<basicDeviceClass>ROUTING_SLAVE</basicDeviceClass>
<genericDeviceClass>SENSOR_NOTIFICATION</genericDeviceClass>
<specificDeviceClass>NOTIFICATION_SENSOR</specificDeviceClass>
</deviceClass>
<homeId>0xd477a917</homeId>
<nodeId>16</nodeId>
<version>4</version>
<manufacturer>0x214</manufacturer>
<deviceId>0x2</deviceId>
<deviceType>0x2</deviceType>
<listening>false</listening>
<frequentlyListening>false</frequentlyListening>
<routing>true</routing>
<security>false</security>
<beaming>true</beaming>
<maxBaudRate>40000</maxBaudRate>
<nodeInformationFrame>
<commandClass>ZWAVE_PLUS_INFO</commandClass>
<commandClass>SENSOR_BINARY</commandClass>
<commandClass>WAKE_UP</commandClass>
<commandClass>BATTERY</commandClass>
<commandClass>VERSION</commandClass>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<commandClass>ALARM</commandClass>
<commandClass>ASSOCIATION</commandClass>
<commandClass>ASSOCIATION_GROUP_INFO</commandClass>
<commandClass>POWERLEVEL</commandClass>
<commandClass>DEVICE_RESET_LOCALLY</commandClass>
</nodeInformationFrame>
<supportedCommandClasses>
<entry>
<commandClass>ASSOCIATION</commandClass>
<associationCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<maxGroups>2</maxGroups>
</associationCommandClass>
</entry>
<entry>
<commandClass>BATTERY</commandClass>
<batteryCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<batteryLevel>96</batteryLevel>
<batteryLow>false</batteryLow>
<isGetSupported>true</isGetSupported>
</batteryCommandClass>
</entry>
<entry>
<commandClass>VERSION</commandClass>
<versionCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<libraryType>LIB_SLAVE_ROUTING</libraryType>
<protocolVersion>4.5</protocolVersion>
<applicationVersion>1.36</applicationVersion>
<hardwareVersion>255</hardwareVersion>
</versionCommandClass>
</entry>
<entry>
<commandClass>MANUFACTURER_SPECIFIC</commandClass>
<manufacturerSpecificCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<initSerialNumber>false</initSerialNumber>
<deviceManufacturer>532</deviceManufacturer>
<deviceType>2</deviceType>
<deviceId>2</deviceId>
</manufacturerSpecificCommandClass>
</entry>
<entry>
<commandClass>WAKE_UP</commandClass>
<WakeUpCommandClass>
<version>2</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<targetNodeId>1</targetNodeId>
<interval>43200</interval>
<minInterval>1800</minInterval>
<maxInterval>432000</maxInterval>
<defaultInterval>43200</defaultInterval>
<intervalStep>60</intervalStep>
<lastWakeup>2017-11-27 20:07:09.132 UTC</lastWakeup>
<isGetSupported>true</isGetSupported>
</WakeUpCommandClass>
</entry>
<entry>
<commandClass>BASIC</commandClass>
<basicCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<isGetSupported>true</isGetSupported>
</basicCommandClass>
</entry>
<entry>
<commandClass>ASSOCIATION_GROUP_INFO</commandClass>
<associationGroupInfoCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<autoSubscribeGroups>
<int>1</int>
</autoSubscribeGroups>
</associationGroupInfoCommandClass>
</entry>
<entry>
<commandClass>DEVICE_RESET_LOCALLY</commandClass>
<deviceResetLocallyCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</deviceResetLocallyCommandClass>
</entry>
<entry>
<commandClass>SENSOR_BINARY</commandClass>
<binarySensorCommandClass>
<version>0</version>
<instances>0</instances>
<versionSupported>0</versionSupported>
<isGetSupported>true</isGetSupported>
<types/>
</binarySensorCommandClass>
</entry>
<entry>
<commandClass>ZWAVE_PLUS_INFO</commandClass>
<zwavePlusCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>2</versionSupported>
<zwPlusVersion>1</zwPlusVersion>
<zwPlusRole>6</zwPlusRole>
<zwPlusNodeType>0</zwPlusNodeType>
<zwPlusDeviceType>0xc01</zwPlusDeviceType>
<zwPlusInstallerIcon>0xc01</zwPlusInstallerIcon>
<isGetSupported>true</isGetSupported>
</zwavePlusCommandClass>
</entry>
<entry>
<commandClass>NO_OPERATION</commandClass>
<noOperationCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
</noOperationCommandClass>
</entry>
<entry>
<commandClass>ALARM</commandClass>
<alarmCommandClass>
<version>4</version>
<instances>1</instances>
<versionSupported>4</versionSupported>
<alarms>
<entry>
<alarmType>SMOKE</alarmType>
<alarmState>
<alarmType>SMOKE</alarmType>
<reportedEvents>
<int>1</int>
</reportedEvents>
<outer-class reference="../../../.."/>
</alarmState>
</entry>
<entry>
<alarmType>BURGLAR</alarmType>
<alarmState>
<alarmType>BURGLAR</alarmType>
<reportedEvents>
<int>3</int>
</reportedEvents>
<outer-class reference="../../../.."/>
</alarmState>
</entry>
</alarms>
<v1Supported>true</v1Supported>
<isGetSupported>true</isGetSupported>
</alarmCommandClass>
</entry>
<entry>
<commandClass>POWERLEVEL</commandClass>
<powerLevelCommandClass>
<version>1</version>
<instances>1</instances>
<versionSupported>1</versionSupported>
<powerLevel>0</powerLevel>
<powerTimeout>0</powerTimeout>
</powerLevelCommandClass>
</entry>
</supportedCommandClasses>
<securedCommandClasses/>
<associationGroups>
<entry>
<int>1</int>
<associationGroup>
<index>1</index>
<name>Lifeline</name>
<profile1>0x0</profile1>
<profile2>0x1</profile2>
<commands>
<commandClass>BASIC</commandClass>
<commandClass>BATTERY</commandClass>
<commandClass>SENSOR_BINARY</commandClass>
<commandClass>ALARM</commandClass>
</commands>
<associations>
<associationMember>
<node>1</node>
<endpoint>0</endpoint>
</associationMember>
</associations>
</associationGroup>
</entry>
<entry>
<int>2</int>
<associationGroup>
<index>2</index>
<name>Sensor Basic Set</name>
<profile1>0x20</profile1>
<profile2>0x1</profile2>
<commands>
<commandClass>BASIC</commandClass>
</commands>
<associations/>
</associationGroup>
</entry>
</associationGroups>
<nodeNeighbors/>
<lastSent>2017-11-27 20:07:11.754 UTC</lastSent>
<lastReceived>2017-11-27 20:07:11.805 UTC</lastReceived>
</node>
Great - glad we’re making progress with your PIR sensor .
I have two suggestions…
First we try and work out what device IDs go with what device. This is the ideal solution and assumes the manufacturer has not duplicated devices codes. The problem here is to work this out - I could just take the data from you and @shorty707 and use this and wait for other people to complain their devices aren’t working . Not nice, but to do this we need to have people come forward to confirm devices.
1a. A variation on this theme - email the manufacturer and see if they will provide the information. Some manufacturers are very good with support - some just won’t even answer…
If the above doesn’t work, or shows duplication of device codes, then we can probably just add a smoke sensor channel to the PIR. It will probably work ok, but it’s also not nice and will likely confuse people. This will really be the only option if the manufacturer has not allocated separate codes for these devices.
So, to start, we should build a list of the device ID/Type and the device names.
OK, I will try to find an email and write the manufacturer.
Logs I have found from this device,
in openhab.log:
2017-11-27 21:07:09.702 [INFO ] [ommandclass.ZWaveVersionCommandClass] - NODE 16: Command Class SENSOR_BINARY has version 0!
and in events.log:
2017-11-27 21:21:57.423 [hingStatusInfoChangedEvent] - ‘zwave:device:21e427dc:node16’ changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2017-11-27 21:26:20.329 [vent.ItemStateChangedEvent] - node16_SmokeKaipule changed from NULL to 96