Zwave ZD2201

[Ffrog (Fred)]

Hoping someone with some zwave database expertise can help me out.
I’ve just got a ZD2201 door/window sensor, which is in the zwave database and is detected by the OH2 & zwave binding. Unfortunately I’ve had no luck getting a sane open/close from the sensor.

After updating the database and trying out the updated XML I’m still no closer. I believe the ‘issue’ is that the sensor uses the Alarm command/notification for both a Burglar and Door open/close. They differ by the notification type (0x06 for Door and 0x07 for Burglar) and in addition the event for the notification type is used to distinguish between open and close, for both: with Burglar (0x00 close, 0x03 open) and Door (0x17 close, 0x16 open).

I don’t know how to update the database so that it will generate the correct XML for OH2 so it understands both Burglar, Door and open/close for each. Below are some logs from when I ‘stimulated’ the sensor to produce each response so it looks like OH2 gets all the messages but it doesn’t know what to do with them.

Can anyone help and explain how I need to set up the database entry for this kind of sensor?

Cheers!
F.

PS Chris, I can’t seem to remove the binary sensor from the ZD2201 database entry - but I’m pretty sure its wrong!

No Buglar 
2017-06-10 14:20:59.284 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Application Command Request (ALIVE:DONE)
2017-06-10 14:20:59.285 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Starting initialisation from DONE
2017-06-10 14:20:59.286 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Incoming command class ALARM
2017-06-10 14:20:59.287 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Received ALARM command V4
2017-06-10 14:20:59.288 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Process NOTIFICATION_REPORT V4
2017-06-10 14:20:59.289 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: NOTIFICATION report - 7 = 0, event=0, status=255
2017-06-10 14:20:59.289 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Alarm Type = BURGLAR (7)
2017-06-10 14:20:59.290 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-06-10 14:20:59.291 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-06-10 14:20:59.536 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Application Command Request (ALIVE:DONE)
2017-06-10 14:20:59.536 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Starting initialisation from DONE
2017-06-10 14:20:59.538 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Incoming command class ALARM
2017-06-10 14:20:59.539 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Received ALARM command V4
2017-06-10 14:20:59.540 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Process NOTIFICATION_REPORT V4
2017-06-10 14:20:59.541 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: NOTIFICATION report - 7 = 0, event=0, status=255
2017-06-10 14:20:59.541 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Alarm Type = BURGLAR (7)
2017-06-10 14:20:59.543 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-06-10 14:20:59.544 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255

Buglar
2017-06-10 14:21:10.334 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Application Command Request (ALIVE:DONE) 2017-06-10 14:21:10.335 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Starting initialisation from DONE 2017-06-10 14:21:10.337 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Incoming command class ALARM 2017-06-10 14:21:10.338 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Received ALARM command V4 2017-06-10 14:21:10.339 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Process NOTIFICATION_REPORT V4 2017-06-10 14:21:10.340 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: NOTIFICATION report - 7 = 255, event=3, status=255 2017-06-10 14:21:10.341 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Alarm Type = BURGLAR (7) 2017-06-10 14:21:10.346 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got an event from Z-Wave network: ZWaveAlarmValueEvent 2017-06-10 14:21:10.347 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255 2017-06-10 14:21:10.379 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Application Command Request (ALIVE:DONE) 2017-06-10 14:21:10.380 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Starting initialisation from DONE 2017-06-10 14:21:10.382 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Incoming command class ALARM 2017-06-10 14:21:10.383 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Received ALARM command V4 2017-06-10 14:21:10.384 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Process NOTIFICATION_REPORT V4 2017-06-10 14:21:10.386 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: NOTIFICATION report - 7 = 255, event=3, status=255 2017-06-10 14:21:10.387 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Alarm Type = BURGLAR (7) 2017-06-10 14:21:10.389 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got an event from Z-Wave network: ZWaveAlarmValueEvent 2017-06-10 14:21:10.390 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255

Door Closed

2017-06-10 14:22:08.026 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Application Command Request (ALIVE:DONE)
2017-06-10 14:22:08.027 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Starting initialisation from DONE
2017-06-10 14:22:08.030 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Incoming command class BASIC
2017-06-10 14:22:08.031 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 41: Received Basic Request
2017-06-10 14:22:08.032 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 41: Basic Set sent to the controller will be processed as Basic Report
2017-06-10 14:22:08.033 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 41: Basic report, value = 0x00
2017-06-10 14:22:08.035 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-06-10 14:22:08.036 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 0
2017-06-10 14:22:08.054 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Application Command Request (ALIVE:DONE)
2017-06-10 14:22:08.056 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Starting initialisation from DONE
2017-06-10 14:22:08.059 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Incoming command class ALARM
2017-06-10 14:22:08.061 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Received ALARM command V4
2017-06-10 14:22:08.063 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Process NOTIFICATION_REPORT V4
2017-06-10 14:22:08.065 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: NOTIFICATION report - 6 = 0, event=23, status=255
2017-06-10 14:22:08.067 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Alarm Type = ACCESS_CONTROL (6)
2017-06-10 14:22:08.072 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-06-10 14:22:08.074 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-06-10 14:22:08.082 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Updating channel state zwave:device:88bf0286:node41:alarm_access to ON [OnOffType]

Door opened

2017-06-10 14:22:33.277 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Application Command Request (ALIVE:DONE)
2017-06-10 14:22:33.278 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Starting initialisation from DONE
2017-06-10 14:22:33.280 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Incoming command class BASIC
2017-06-10 14:22:33.281 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 41: Received Basic Request
2017-06-10 14:22:33.283 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 41: Basic Set sent to the controller will be processed as Basic Report
2017-06-10 14:22:33.285 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 41: Basic report, value = 0xFF
2017-06-10 14:22:33.288 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2017-06-10 14:22:33.289 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
2017-06-10 14:22:33.311 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Application Command Request (ALIVE:DONE)
2017-06-10 14:22:33.312 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 41: Starting initialisation from DONE
2017-06-10 14:22:33.315 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 41: Incoming command class ALARM
2017-06-10 14:22:33.316 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Received ALARM command V4
2017-06-10 14:22:33.317 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Process NOTIFICATION_REPORT V4
2017-06-10 14:22:33.318 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: NOTIFICATION report - 6 = 255, event=22, status=255
2017-06-10 14:22:33.319 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 41: Alarm Type = ACCESS_CONTROL (6)
2017-06-10 14:22:33.321 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2017-06-10 14:22:33.322 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2017-06-10 14:22:33.326 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 41: Updating channel state zwave:device:88bf0286:node41:alarm_access to ON [OnOffType]

[chris (Chris Jackson)]

Are you really talking about the ZD2202, or the ZD2102 (or maybe they are the same?). I can’t find a 2202 in the database.

@Ffrog

They differ by the notification type (0x06 for Door and 0x07 for Burglar)

For the ZD2102 this is already configured.

@Ffrog

can’t seem to remove the binary sensor from the ZD2201 database entry

I guess we’re talking about different devices then since I don’t see a binary sensor. Can you post the link to the device you are talking about since searching the database for 2202 doesn’t seem to find it .

[Ffrog (Fred)]

Its a ‘ZD2201 Multisensor 4in1’ paper UI and the box it came in agree on that … all the numbers its doing my head in…

[chris (Chris Jackson)]

Can you post the link to the device you are talking about in the database please.

[Ffrog (Fred)]

Apologies http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/450

[chris (Chris Jackson)]

Thanks - not sure why the search didn’t find that .

Can you post the XML for your device and I’ll look at updating the classes…

[Ffrog (Fred)]

Ahh okay so its not as simple as a database config change - or is there an advanced button I didn’t see?

Regardless Cheers!

Here is the XML
<node> <deviceClass> <basicDeviceClass>ROUTING_SLAVE</basicDeviceClass> <genericDeviceClass>SENSOR_NOTIFICATION</genericDeviceClass> <specificDeviceClass>NOTIFICATION_SENSOR</specificDeviceClass> </deviceClass> <homeId>0xed4ea4c9</homeId> <nodeId>41</nodeId> <version>4</version> <manufacturer>0x109</manufacturer> <deviceId>0x1f10</deviceId> <deviceType>0x201f</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>VERSION</commandClass> <commandClass>MANUFACTURER_SPECIFIC</commandClass> <commandClass>DEVICE_RESET_LOCALLY</commandClass> <commandClass>ASSOCIATION</commandClass> <commandClass>ASSOCIATION_GROUP_INFO</commandClass> <commandClass>POWERLEVEL</commandClass> <commandClass>BATTERY</commandClass> <commandClass>ALARM</commandClass> <commandClass>SENSOR_MULTILEVEL</commandClass> <commandClass>CONFIGURATION</commandClass> <commandClass>WAKE_UP</commandClass> <commandClass>FIRMWARE_UPDATE_MD</commandClass> </nodeInformationFrame> <supportedCommandClasses> <entry> <commandClass>MANUFACTURER_SPECIFIC</commandClass> <manufacturerSpecificCommandClass> <version>1</version> <instances>1</instances> <versionSupported>2</versionSupported> <initSerialNumber>false</initSerialNumber> <deviceManufacturer>265</deviceManufacturer> <deviceType>8223</deviceType> <deviceId>7952</deviceId> </manufacturerSpecificCommandClass> </entry> <entry> <commandClass>DEVICE_RESET_LOCALLY</commandClass> <deviceResetLocallyCommandClass> <version>1</version> <instances>1</instances> <versionSupported>1</versionSupported> </deviceResetLocallyCommandClass> </entry> <entry> <commandClass>ASSOCIATION</commandClass> <associationCommandClass> <version>2</version> <instances>1</instances> <versionSupported>2</versionSupported> <maxGroups>1</maxGroups> </associationCommandClass> </entry> <entry> <commandClass>ALARM</commandClass> <alarmCommandClass> <version>4</version> <instances>1</instances> <versionSupported>4</versionSupported> <alarms> <entry> <alarmType>BURGLAR</alarmType> <alarmState> <alarmType>BURGLAR</alarmType> <reportedEvents> <int>3</int> </reportedEvents> <outer-class reference="../../../.."/> </alarmState> </entry> <entry> <alarmType>ACCESS_CONTROL</alarmType> <alarmState> <alarmType>ACCESS_CONTROL</alarmType> <reportedEvents> <int>22</int> <int>23</int> </reportedEvents> <outer-class reference="../../../.."/> </alarmState> </entry> </alarms> <v1Supported>false</v1Supported> <isGetSupported>true</isGetSupported> </alarmCommandClass> </entry> <entry> <commandClass>FIRMWARE_UPDATE_MD</commandClass> <firmwareUpdateCommandClass> <version>1</version> <instances>1</instances> <versionSupported>2</versionSupported> </firmwareUpdateCommandClass> </entry> <entry> <commandClass>WAKE_UP</commandClass> <WakeUpCommandClass> <version>2</version> <instances>1</instances> <versionSupported>2</versionSupported> <targetNodeId>1</targetNodeId> <interval>3600</interval> <minInterval>600</minInterval> <maxInterval>604800</maxInterval> <defaultInterval>3600</defaultInterval> <intervalStep>200</intervalStep> <lastWakeup>2017-06-10 04:39:22.679 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_MULTILEVEL</commandClass> <multiLevelSensorCommandClass> <version>7</version> <instances>1</instances> <versionSupported>7</versionSupported> <sensors> <entry> <multilevelSensorType>LUMINANCE</multilevelSensorType> <multilevelSensor> <sensorType>LUMINANCE</sensorType> <initialised>true</initialised> </multilevelSensor> </entry> <entry> <multilevelSensorType>TEMPERATURE</multilevelSensorType> <multilevelSensor> <sensorType>TEMPERATURE</sensorType> <initialised>true</initialised> </multilevelSensor> </entry> <entry> <multilevelSensorType>RELATIVE_HUMIDITY</multilevelSensorType> <multilevelSensor> <sensorType>RELATIVE_HUMIDITY</sensorType> <initialised>true</initialised> </multilevelSensor> </entry> </sensors> <isGetSupported>true</isGetSupported> </multiLevelSensorCommandClass> </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>CONFIGURATION</commandClass> <configurationCommandClass> <version>1</version> <instances>1</instances> <versionSupported>1</versionSupported> <configParameters> <entry> <int>1</int> <configurationParameter> <index>1</index> <size>1</size> <value>0</value> <readOnly>false</readOnly> <writeOnly>false</writeOnly> </configurationParameter> </entry> <entry> <int>2</int> <configurationParameter> <index>2</index> <size>1</size> <value>10</value> <readOnly>false</readOnly> <writeOnly>false</writeOnly> </configurationParameter> </entry> <entry> <int>3</int> <configurationParameter> <index>3</index> <size>1</size> <value>10</value> <readOnly>false</readOnly> <writeOnly>false</writeOnly> </configurationParameter> </entry> <entry> <int>4</int> <configurationParameter> <index>4</index> <size>1</size> <value>10</value> <readOnly>false</readOnly> <writeOnly>false</writeOnly> </configurationParameter> </entry> </configParameters> </configurationCommandClass> </entry> <entry> <commandClass>BASIC</commandClass> <basicCommandClass> <version>1</version> <instances>1</instances> <versionSupported>1</versionSupported> <isGetSupported>true</isGetSupported> </basicCommandClass> </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>ZWAVE_PLUS_INFO</commandClass> <zwavePlusCommandClass> <version>1</version> <instances>1</instances> <versionSupported>2</versionSupported> <zwPlusVersion>1</zwPlusVersion> <zwPlusRole>6</zwPlusRole> <zwPlusNodeType>0</zwPlusNodeType> <zwPlusDeviceType>0xc07</zwPlusDeviceType> <zwPlusInstallerIcon>0xc07</zwPlusInstallerIcon> <isGetSupported>true</isGetSupported> </zwavePlusCommandClass> </entry> <entry> <commandClass>BATTERY</commandClass> <batteryCommandClass> <version>1</version> <instances>1</instances> <versionSupported>1</versionSupported> <batteryLevel>100</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_ENHANCED</libraryType> <protocolVersion>4.5</protocolVersion> <applicationVersion>6.1</applicationVersion> <hardwareVersion>3</hardwareVersion> </versionCommandClass> </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>DEVICE_RESET_LOCALLY</commandClass> <commandClass>ALARM</commandClass> <commandClass>SENSOR_MULTILEVEL</commandClass> </commands> <associations> <associationMember> <node>1</node> <endpoint>0</endpoint> </associationMember> </associations> </associationGroup> </entry> </associationGroups> <nodeNeighbors> <int>1</int> <int>7</int> <int>21</int> <int>22</int> <int>24</int> <int>25</int> <int>36</int> </nodeNeighbors> <lastSent>2017-06-10 04:39:23.319 UTC</lastSent> <lastReceived>2017-06-10 04:39:23.362 UTC</lastReceived> </node>

[chris (Chris Jackson)]

@Ffrog

Ahh okay so its not as simple as a database config change

Well, it is, but… There are 2 issue - firstly, I don’t allow normal users to delete stuff (just a safety measure), and once a device is defined, uploading further XML files only changes a few things - it can’t completely redefine a device. Again, this is for safety so that someone doesn’t upload the wrong XML to a database entry that lots of people use, and it destroys it.

Changes need to be made manually - I’ll take a look as it’s probably easiest…

[chris (Chris Jackson)]

I’ve updated the database and will do an update to the binding tonight (hopefully!).

[Ffrog (Fred)]

Awesome, I’ll check it out in the morning!

[Ffrog (Fred)]

Hi Chris, Some bad news? I just tried with https://openhab.ci.cloudbees.com/job/PR-org.openhab.binding.zwave/850 but all zwave nodes are stuck in INITIALIZING state now. I’ve e-mailed a log to you, if it helps. Cheers F.

PS I’m going to try rolling back (but with updated XML to confirm the sensor functionality).

[chris (Chris Jackson)]

Strange - the only thing that has changed for a long time is the database, so I suspect this might not be related.

[chris (Chris Jackson)]

What version of the binding have you been using? Are you using the development version - that’s what you’ve downloaded here, so if you weren’t using this before, then it really won’t work.

I thing from the logs above that you’re using the main snapshot versions, so you should continue to use this and not the development branch.

[Ffrog (Fred)]

Hi Chris, Prior to this update this morning i was using 2.1.0.201706092128 ( https://openhab.ci.cloudbees.com/job/PR-org.openhab.binding.zwave/844) but with modified database entry for ZD2201. Most bundles are stock openhabian release module versions with just zwave updated.

I’ve rolled back to 2.1.0.201706092128 and all the nodes have come back, just waiting for ZD2201 to be re-recognised.

I’m not sure what you mean by main snapshot versions vs development branch. Do you mean wait until https://openhab.ci.cloudbees.com/job/openHAB2-Bundles/lastSuccessfulBuild/org.openhab.binding%24org.openhab.binding.zwave/ has completed a new build?

[chris (Chris Jackson)]

@Ffrog

I’m not sure what you mean by main snapshot versions vs development branch.

The snapshot version is the master version - it’s what you would install if you were running normally. If you’re testing the bleeding edge with the security additions, then that’s in the development branch - it’s a major change, and you can’t swap between the branches.

The development branch is discussed here -:

OH2 Z-Wave refactoring and testing... and SECURITY

The latest version of the development binding dated 8th Sep 2018 is here. Toward the end of last year I spent some time doing some initial refactoring of the ZWave binding in OH2. This focussed on rewriting the way transactions work as this is an enabler for other areas of the code. At the same time I also restructured the different layers of the binding to make things cleaner, and done some changes to support a system of autocoding the command classes directly from the Z-Wave standard which s…

Since you weren’t running this version previously, you can’t just change to it, so if you want to use the PRs off Cloudbees, then make sure they aren’t from the development branch - use the master branch (or just install through the UI and then you’re definitely ok ).

[Ffrog (Fred)]

Ok got it, thanks. For the record I rolled back to 2.1.0.201706092128 (with updated database entry for ZD2201) and the new channels for tamper and door turned up :). I created items and linked them but I’ve been unsuccessful in triggering either?

[Ffrog (Fred)]

Ignore - looks like everything is fine! Apart from resetting my ZWave USB stick… what a PITA!