Z-Wave node got lost with snapshot of z-wave binding of build #1120 from Cloudbees

[svenschaefer74]

@cdjackson

I just tried the latest snapshot of the binding and after exchanging the JAR file and restarting the openhab service one of my mains powered nodes (node 32) wasn't existing anymore.

I'm using a Razberry board on a RPI2 w/o any issues so far.

I've attached the according xml file for the node from /var/lib/openhab/zwave
node32.xml.txt

I've also tried to catch the relevant part of the zwave.log
zwave.log.txt

I already restarted the complete RPI2 but this didn't change anything (as expected).

I've not yet tried to include the device again.

Funny enough I still can see the node32 in the network overview of the HABmin interface.

Additional info:

• With the snapshot binding from January 3rd everything was fine.
• The device that got lost is a Fibaro FGS222.

[svenschaefer74]

After a couple of useless tries I had to get the Switch working again since otherwise my wife wouldn't have been happy 😁

I removed the wall switch, set the controller into inclusion mode and pushed the wakeup button of the FGS222 a couple of times. Finally the device reappeared in HABmin again as node32. From there on everything works fine again.

I added the according zwave.log beginning with the inclusion mode.
zwave.log.txt

When I looked through the binding settings in HABmin I found that the 'Enable SUC mode' value was empty. I thought that I'd remember that it was set to true before I used the latest snapshot binding but there is no proof. Anyhow I set it to true.

If there is anything else I can do to support the investigation I would be happy to help.