Actually I don’t think it will appear in the actual OH snapshot (i.e. for those of us who install through PaperUI et al) until tomorrow, right? The current SNAPSHOT is still 1725 as far as I can tell, unless the snapshot build happened in the last hour or so.
Correct… this is currently only available in the binding snapshot. You could use the script or run…
bundle:update org.openhab.binding.zwave https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/addons/bundles/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
This latter method is how the script will work in the future. It’s nice, since Karaf will handle the dependencies for you! Possibly, I’ll extend the script so that you could pull down the snapshot version of any binding.
I thought the binding snapshot was compiled as part of the build compilation.
The binding snapshots are built through openhab2-Bundles. There are lots of builds… https://ci.openhab.org/. It looks like an openhab2-Distribution build has been started and completed, so this will also now be in the OH snapshot. The openhab2-Core build failed (again!), so you will not see any of those changes yet in the OH snapshot.
I can confirm that running the bundle:update works like a charm. No more exception when restarting OH and no more warnings.
2 Likes
I’m playing with a script that will update any binding requested to a snapshot version. I think this should be built into the REST API, so that the version used for a binding (stable, milestone, snapshot) can be specified by the user.
3 Likes