Issue of the topic: please be detailed explaining your issue
I’m new to Zwave and what I have unstood ther are som bugs in the Zwave binding 2.4 (stable) and have find here in the community that Chris recomends to install the 2.5 SNAPSHOT build.
I have searched in many topics and the documentation but not found any accurate answers on my topic.
Now I have some questions:
I have found severel links to the SNAPSHOT but wonder what is the officiel link?
Is it allways the same link to the latest binding?
Do I have to follow the instructions in the topic “ZWave binding updates” when update to the SNAPSHOT?
@scottk, thanks for the instructions. I also followed it closely in order to replace the 2.4.0 Z-Wave binding, formerly installed via PaperUI by the 2.5.0 Snapshot of April 20th, provided at the given link. The idea is to be able and control new devices that are not yet part of the 2.4.0 release.
I did as you said but I did nothing else but these steps. I checked that the .jar file is in the /usr/share/openhab2/addons folder. However, I now don’t see the new Z-Wave Binding in PaperUI anymore, not under Addons-Bindings nor under Inbox when I want to pick a binding to find new devices. It does appear in Karaf when I bundle:list as “installed”.
Is there anything you have to do in order to make the snapshot-version work? Is there a way to check if is recognized and may only don’t show up in PaperUI?
OK, it is resolved. I found in another thread that sometimes you also need to " feature:install openhab-transport-serial" in the Karaf in that case. I did that before I updated the Z-Wave because I though it was a one-time installation of a package rather than a procedure you have to execute after installing the bundle.
2.5.0 is now up and running and it correctly recognized the new devices.
@chris is the 2.5 snapshot version:
A) compatible w/ OH 2.4.x
B) Generally “stable”
C) The only way to get access to newer devices in the db? (aka, are there any 2.4.x point release of the binding that would also accomplish this?)
I think I’ve lamented this before, but it’s too bad there’s not a way to split the db portion out to a separate “binding” or piece of code (I realize it’s far too intertwined to do).
I’m not 100% sure - it’s 9 months since 2.4 was released and I think there may be some changes that require the 2.5 runtime.
Generally, I believe so.
Yes - short of rolling your own…
Yes, this is a discussion that comes up again and again. The bottom line is -:
openHAB doesn’t support this. To do this myself I would need to create a special configuration provider and really moves away from openHAB core features.
it is not guaranteed to work in any case. New features get added to Java that are interpreted by the XML files, so new options in the XML may fail. Basically, compatibility between XML is only ensured by liking the two together.