Hello fellow OpenHAB enthusiasts! I’ve been diving into the world of Z-Wave integration with OpenHAB 2.2, and I must say, it’s been quite a journey. I wanted to share my experiences and see if anyone else has encountered similar challenges or has insights to offer.
My Setup:
- Controller: Aeon Labs USB stick (Z-Stick Gen5)
- Range Extender: Aeotec Range Extender (EU) DSD37-ZWEU
- Sensors: 5x Sensative Strips (door/window sensors)
- Rain Sensor: POPP Z-Rain
The Journey So Far:
When I first migrated to OpenHAB 2.2, I decided to stick with the older v1.x Z-Wave binding. It worked like a charm, except for the POPP Z-Rain sensor, which I’m still troubleshooting. All other devices were discovered and functioning smoothly. However, the allure of newer features in the v2.2 binding was too strong to resist, so I decided to make the switch.
The Transition to v2.2 Binding:
Uninstalling the old binding, clearing out old Z-Wave related files, and installing the new binding seemed straightforward. I followed the steps meticulously:
- Uninstalled v1.x binding via PaperUI
- Removed all Z-Wave related files from the file system
- Installed the new v2 binding
- Verified
zwave.cfgsettings - Checked configuration parameters in PaperUI
The Challenge:
Despite all these steps, my devices aren’t being discovered properly. The logs show that the controller is initializing and nodes are being detected, but there’s no option to link items with the nodes. I’m left with a setup that feels almost there, but just out of reach.
Logs and Symptoms:
Here’s a snippet from the logs:
15-Jan-2018 14:37:13.126 [INFO ] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Connecting to serial port ‘COM4’
15-Jan-2018 14:37:13.143 [INFO ] [g.openhab.binding.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
15-Jan-2018 14:37:13.145 [INFO ] [al.protocol.commandclass.ZWaveSecurityCommandClass] - Update networkKey
15-Jan-2018 14:37:13.149 [INFO ] [ab.binding.zwave.internal.protocol.ZWaveController] - Starting ZWave controller
And the node discovery logs:
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 1: Node found
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - NODE 2: Node found
…
15-Jan-2018 14:37:16.545 [INFO ] [col.serialmessage.SerialApiGetInitDataMessageClass] - # Nodes = 8
Despite these positive signs, the devices remain elusive in terms of item linking.
Questions and Seek for Answers:
- Has anyone successfully migrated from v1.x to v2.2 without such issues?
- Are there specific configurations or additional steps required when upgrading the binding?
- Could there be residual configurations or cached data that I might have missed?
Next Steps:
I’m considering reaching out to the developers or checking the latest documentation for any known issues or migration tips. If anyone has insights or has encountered similar problems, I’d greatly appreciate your advice!
Let’s keep the conversation flowing and help each other navigate the exciting yet sometimes tricky world of Z-Wave integration!
Best regards,
John