I am running 3.4.3 openhabian, and wondered if there is an upgrade path to openHAB v5.x?!
Googling and searching shows 3–>4 migrations, but no 3–>5. Making me think if a 3–>4 and 4–>5 = 2-step migration is required.
Any hints appreciated.
Theoretically it should work to go straight from 3.4 to 5.0. The number of breaking changes and their impact even over that wide stretch is relatively small compared to, for example, the differences between 2.5 and 3.0.
The upgradeTool should be able to handle a lot of these breaking changes for you, but only for managed configs. It won’t go and change your .things files for you (for example, except in one case which won’t apply to you because it’s a config file that didn’t exist in 3.4 in the first place). This runs during an upgrade.
But I fully expect a lot of stuff to be broken. The changes made to make units work properly in 4.0 is probably going to be the biggest change you’ll have to deal with. A bunch of add-ons will require discovery/recreation of Things. There are lots of new features in the rules languages but not too much breaking there.
You can take it in steps in order to split up the work. You can go from 3 → 4 and then you only have to deal with two years worth of breaking changes. Once you get your config up to where everything works moving from 4 → 5 should be relatively painless.
There’s not a lot of breaking changes in between OH 4.3 and OH 5 that require manual changes to your configs. So most of the work will be done in that 3 → 4 upgrade. I’d say you may as well upgrade all the way in one go because of that. Or, upgrade from 3.4.3 → 4.0 → 4.1 → 4.2 → 4.3 → 5.0. Each of those steps will be a relatively small amount of work to upgrade at a time since you’ll only be addressing six month’s worth of changes to OH at a time instead of years worth.
You’ll need to go through the announcements for each release between 3.4 and 5.0 to find out what you need to do (if anything) to adjust your configs though. You can’t just look at the latest announcement and get all the details you need.
Note, there is a bug in the upgradeTool so if during the upgrade to 5.0 you see an error from upgradeTool you can ignore it. What that part of the tool does won’t apply to you anyway. A fix is coming in 5.0.1.
1 Like
For this reason, it’s better to upgrade to 4.3.6 first, so that the upgradetool works. Then immediately upgrade to 5.0.
1 Like
I thought the yaml upgrade was done last. So the three other tasks would complete even if there is an error.
The yaml upgrade isn’t the problem. There were missing dependencies needed in the first three steps so all steps failed.
1 Like