bullseye comes with 2.0.16, where in buster its 1.5.7 the latest.
I might add mosquitto-bullseye repo to my buster machine and try to upgrade it.
as I understand, they want users to become more security aware, and by default 2.0ver it does not accept incoming anonymous connections outside localhost.
adding this to mosquitto.conf:
EDIT: aaand…done! I’m now running mosquitto 2.0.16, the same version that comes with latest openhabian bullseye. taking another backup.
now zigbee2mqtt left to go…
EDIT2: zigbee2mqtt done
sudo systemctl stop zigbee2mqtt
Go to the Zigbee2mqtt folder.
Backup zigbee2mqtt config.
cp -R data data-backup
git checkout HEAD -- npm-shrinkwrap.json
cp -R data-backup/* data
rm -rf data-backup
sudo systemctl start zigbee2mqtt
with a small detail that it had fallen apart after the upgrade, but managed to fix it.
nodejs had to be upgraded as well
now I am confident that everything will work on openhabian, as I am running latest versions of those 2 services.
I would like to add that I included the update procedure into openhabian under “optional components” - “2A install or update zigbee2mqtt”. If it finds an already installed zigbee2mqtt it does just the update.
So usually there’s no need to do it by hand.
And yes, openhabian always installs the latest version from GitHub.
I’m aware of all the bells and whistles you have there in openhabian, that’s the reason I want to migrate to it
so my future upgrades will be a breeze
now I’m on raspbian buster 10, but I upgraded all the components (OH, Z2M, MQTT) to their latest versions, so I can restore their configs on a fresh openhabian machine with minimal issues I hope.
What about major OS release upgrade, how you handle that? when debian 13 will be out, is it a breeze to upgrade openhabian 1.8 to say 2.0 or whatever it will be called?
I would say it depends.
Debian does not offer an official upgrade procedure. There are hacky descriptions how to do it anyway but I would avoid that because I could never be sure that later problems are not caused by the underlying os.
So If a future major release of openhab requires a newer jdk release (e.g. to benefit from new features) and this jdk is not supported by your current (old) debian version then the clean way will be to install a fresh debian (e.g. the openhabian image via raspberry imager) , restore backups and then upgrade openhab.
Experts, please correct me if something’s wrong…