ZWave binding migration to development version

I’ve spent the morning sorting out the merge and it’s now ready to go. Assuming there are no issues, this will be merged into master tomorrow morning (European time) and available via the normal snapshot route if you’re using 2.4 snapshot runtime.

As per the steps above (thanks @rlkoshak and @5iver) a good way forward to upgrade is as follows -:

  1. Backup.
  2. If on the release or testing version of OH and on an apt/yum based install, change to the snapshot release repo as the source.
  3. If you are not already running 2.4 snapshots, then upgrade OH using the procedure for your platform.
  4. Remove all Zwave Things except for the thing representing the Controller. If the controller is accidentally deleted, it should be recreated with the same ThingID, so that the channels do not change. This can be found in the channel info of an items file, or in a backup Thing.json file. If Things are manually configured in .thing files, they can be moved to another directory and then moved back to pull in the updated Thing definitions.
  5. Uninstall the Zwave binding though PaperUI or the Karaf console. How to do this depends on how it is currently installed. If manually installed, delete jar, then uninstall through Karaf, if it is still shows up with list -s | grep zwave . If installed through a UI or the console (a jar was never dropped into addons), uninstall though a UI or the console.
  6. Install the Zwave binding through PaperUI or the Karaf console.
  7. Go to the Inbox and scan for Zwave devices.
  8. Accept the nodes as they appear.
  9. If necessary, perform whatever wake up steps that are necessary for battery powered devices so the binding can figure out what it is.

The last point above is generally optional, however it is worth noting that all devices will initially be unknown as the XML files that the binding uses to persist information about the device will be recreated. Mains devices should reappear pretty quickly, but battery devices will take time - the exact duration will depend on the wakeup interval configured for the device. You can speed this up by manually waking up the devices (check the manual for each device to learn how to do this). There are a few devices that may not wake up at all by themselves (eg Minimote and Minimote) and these must be woken manually for them to be discovered.

5 Likes