I’m not an expert on the process, but the Zwave binding code resides on Github here openhab/org.openhab.binding.zwave: openHAB binding for Z-Wave (github.com).
After a PR is merged (I think the time varies on a schedule based on euro time?) a zwave .jar appears here. openHAB-ZWave [Jenkins].
Then again on some schedule the builds are compiled into a distribution snapshot Integration Builds [Jenkins] (openhab.org). I think that is to what you are referring.
My general advice in situations like this is to just update the zwave binding, not update all of OH to a new snapshot. That introduces more variables of unknown effect. To just update the zwave binding
- uninstall zwave from the UI, ideally from the 3.3 release version or testing milestone
- go into the openhab-cli and after the passwords type
feature:install openhab-transport-serial. This is a dependency that is installed automatically when adding Zwave from the UI, but not when adding manually. - From the jenkins zwave site copy the jar into the openhab/addons folder (same location as the distribution kar file with all the bindings.
- Delete the Thing (do not exclude) and go to inbox/scan/zwave to pick it up again with the new properties
I don’t know. I have a local copy of the Zwave binding and it is still in there (with blinds_shutter, not blinds_control). Did you delete the thing and rescan. That may help.
Lastly, I picked up from another post that the zwave developer is very busy with his real job (traveling) explaining the delay in getting your changes into the binding. There is a way to update/add an XML file that you might consider. You can read about it here (OH2 procedure) and here (more recent). You can download the updated XML from the DB using the blue gear box in the upper right or you can wait.
Bob