Good morning everyone.
I don’t seem to find any thread specifically about this that’s why I’m opening a new one.
My case is quite simple. I upgraded my 4.1.x installation to 4.3.x, but after a while found out that the Openwebnet binding, which I’m heavily reliying on for my installation, has major bugs and problems in the 4.3.x version with very little hope for the developer to be active and fix them.
My only choice here is reverting back to 4.1.x.
I’m on a Rpi4 Openhabian setup.
I know downgrading is apparently not supported, so what I was thinking was of making a fresh 4.1.x install and upload my 4.1 backup which I made before I did the update.
So I want to write a new card with openhabian and force it to install OH 4.1.x
How can I do this in the best way to have few problems as possible?
It is fundamental otherwise 90% of my installation is basically trash.
I usually rollback to a previous version using the apt command on the terminal. Never failed me but creating a backup before such actions is always a wise precaution.
checking available version numbers:
apt-cache showpkg openhab
doing a roll back to a specific version:
sudo apt-get install openhab=4.2.2-1 openhab-addons=4.2.2-1
before downgrading your openHAB version, you could consider to try out the 4.2.x version of the OpenWebNetBinding.
Deinstall it on your openHAB and download the 4.2.x JAR from JFrog, drop it in your addons folder.
@florian-h05 : Interesting, reason for my downgrade is a bug in the zigbee binding in 4.3 (already reported and being solved). Is this a generic solution? Could I use the 4.2 zigbee binding on 4.3 openhab in a simular way? And most important, won’t deinstalling the zigbee binding make it forget all attached zigbee devices/things/items?
Deinstalling a binding does never remove its Things and/or Items.
The Things will just fail to initialize without the binding being installed.
My suggested approach above should be used with caution, don’t expect it to work in general - changes in openHAB Core APIs or dependency upgrades break compatibility between JARs compiled for a different openHAB version and the used openHAB version.
For 4.2 JARs on 4.3 I am however confident that it could be tried at least to use a 4.2 JAR o 4.3, for 4.1 JAR on 4.2 I don’t think it will work, we don’t need to try it out.
As you said your issue with ZigBee were reported and are solved:
As the fix has been backported (see Commits · openhab/org.openhab.binding.zigbee · GitHub), it should get picked up by our openHAB 4.3 patch release sandbox CI build, which uploads the build artifacts to JFrog.
I would recommend to uninstall the ZigBee add-on and download the latest org.openhab.binding.zigbee KAR from JFrog.
Drop the KAR file into your addons folder and ZigBee should be running again.
Thank you.
I will try this tomorrow, even if I read that some of the issues seemed to be present in the 4.2 version too.
But I will give it a go.
Regarding @supersjel suggestion of downgrading, which will eventually be my B plan, is there anything I should be aware of before doing a downgrade (except taking a backup of course)?
No,.as far as I know this is enough. The apt system keeps track of everything and does the job. Usually even a reboot is not necessary. Did it a few times and never had any trouble. And if all fails, with a backup your original plan “a clean install” is still an option.
So I can think only of two things. Do remember, if you installed more than openHAB on the raspberry to backup that too. In my case I got some nodeJS programs on the todo list. And copy the backups to an USB stick to be completely safe.
If you have transformations in any of these bindings that support chained transformations, the configurations would have been converted to arrays and won’t load properly in 4.2 or earlier.
