Gents,
After running openhabian-config in openHAB 4.1.1 - Release Build,
I saw a blue message informing me that a new openhabian1.9 has been released based on Debian bookworm and not on old bullseye, and installation via migration is recommended.
I found a description of migration on the forum via:
1.backup on a working version,
2.renaming the backup to initial.zip and uploading it to a new card,
3.modifying the openhabian.conf file by uncommenting the line # initialconfig=/boot/initial.zip
Everything went smoothly and I have a working version of openHAB 4.1.2 - Release Build now but the table after logging in via the terminal still shows bullseye
###############################################################################
############### openhabian ##################################################
###############################################################################
I don’t know what instructions you found on the forum and why you used them rather than the official ones which are linked to on the openHABian download page such as the OH4 migration FAQ thread.
Reading those should answer your question. The OS itself is not part of openHABian or openHAB so upgrading doesn’t change anything about it.
Migration means to install a freshly downloaded 1.9 image to a new SD and import the old config there.
Put the SD in your Windows system and open the first (only) partition. Edit openhabian.conf and set clonebranch=openHAB3. That should result in (latest) OH3 being installed.
Also put your backup zip file there, name it initial.zip. That’ll auto-import the config during install.
Now put the SD in the Raspi and turn it on. Let openHABian do its install magic.
When finally done, login and run openhabian-config menu option 03 to upgrade to OH4
however I adapted instruction to my situation as I did have 4.1.1 so not needed to install OH3 and then upgrade to OH4, I guess?