So my idea was to do a backup and upgrade the entire OH system to 2.5 / milestone 4. … BUT: as far as I can see I there is now way to upgrade an executable OH in the stable version to 2.5 … or I see that wrong?
You can upgrade just the Z-Wave binding rather easily with the script. If you choose, you can upgrade your Stable 2.4 version to the Testing 2.5 Milestone 4 but you need to change what repository your system uses.
If you are using openHABian, it is quite easy. What OS are you using?
You can update your installation, you just need to add the repository that you’d like to use and then run the OH upgrade script. I recommend this, since there have been so many changes since 2.4 and 2.5 stable is close to release.
If you choose to update just the binding, I suggest not using the script to do a manual install. Just run this in the console and the dependencies will be taken care of for you, which is better than a manual install where the dependencies need to be manually resolved.
ajajaj - seems i am not even clever enough so handle the karal console … i’ve just startet with openhab-cli console … then typed “help” and now im caught in a loop … what do i have to type to get out …?
If you have manually installed the zwave binding, you need to delete the jar from addons. If you have never installed the zwave binding, you need to run bundle:install instead of bundle:update.
Although, I may understand this better… that message may be due to the version change. Uninstall the zwave binding…
Yes, uninstall the zwave binding that you have (through Paper UI or the console) and then run bundle:install. Your Things will be there when you install it again. But ALWAYS do a backup before making changes!
Is the binding active? Have you restarted OH? Do you have a controller Thing and is it configured properly? What do you see in the openhab.log after setting zwave to debug?
If this is all too complicated, upgrade your OH to 2.5M4 or wait for 2.5 stable.
No. You do not need to manually install dependencies if you use bundle:install (or bundle:update). When installed in this way, Karaf resolves the dependencies for you, just like when you install through Paper UI.