This did NOT work for me.
Well, somethings changed. Here’s what I did and what happened.
I followed your instructions. The first time it failed but it seems to have been a permissions issue with the old 2.4.0 jar file. I made it world writable and then tried again and it worked…kinda.
Now I have ZWave installed via PaperUI I don’t know if that’s important.
The FIRST time I got the upgrade on the console to work, everything seems to have worked just fine. I used the command:
bundle:update org.openhab.binding.zwave https://openhab.jfrog.io/openhab/online-repo-snapshot/2.5/org/openhab/binding/org.openhab.binding.zwave/2.5.0-SNAPSHOT/org.openhab.binding.zwave-2.5.0-SNAPSHOT.jar
Then I checked the results with:
list -s | grep zwave
So far, so good, it listed the 2.5.0 jar with a long string of numbers that I assume is the snapshot or build number.
I rebooted my system.
Everything came back up.
I went back into the console and issued the ls command again and it was back to 2.4.0.
So I tried the update again.
Everything seemed to have worked, it was showing the 2.5.0 again. BUT. I got distracted for a few minutes and then just to make sure, I did the ls command again and it was back to 2.4.0.
Long story short, I could not get it to stay on 2.5.0. I eventually uninstalled it form the console, uninstalled it from PaperUI, rebooted and reinstalled 2.4.0 from Paper UI. (I cut out about an hour of banging my head on the monitor and trying different permutations.)
I now have 2.4.0 up and running just fine but obvs, I can’t use the sensors yet.
Have you ever seen it where the upgrade works but then it reverts to the older version? That jsut seemed odd.
Nothing else is running on this system, it’s a little RPi dedicated to openhab.