Thank you, Marcus, for your reply.
In essence you are telling me to not use a fresh openhabian SD image to upgrade my excisiting openhab setup. Restoring a backup between release upgrades is asking for trouble.
To upgrade using openhabian-config (essentially an apt upgrade).
That leaves me with two questions:
But isn’t a backp and restore part of upgrading? For example, in an apt upgrade dpkg is carefull to backup configuration files that look to be user altered between upgrades. And when updating my digitalsSTROM server, I allways make a backup in case flashing the dSS messes something up and necessitates me to re-apply my configuration.
- What about future upgrades, especially in 2 years when Debian’s support for Buster will end? Since openhabians recommendation seems to be not to do an
apt dist-upgradebut to use a fresh openhabian image instead and many users (if not all) will likely want to avoid having tot do their setups all over again, you would want a way to transfer a working configuration. However restoring your openhab-cli backup will probably result in problems.
This might be solved by special instructions in the release notes.
Maybe it can be solved by a backup / restore script rewrite.
At least it would be usefull if there was some reference in the official docs about upgrading. I would be happy to contribute that. Should I write up a proposal on github and do a PR? Or better to discuss here a bit further until it’s clear my PR won’t contain total gibberish?
Am I correct that with text based configuration (OH2) restore was easier, only needing restoring files to /etc/openhab/ ? Whilst in OH3 with the configuration db in json (in /var/lib/etc | {userdata}) these aditional files and locations complicates this more? Maybe extra so because the files in the {userdata} folder can be machine altered?