I used to just update stuff when I could see an update was available. This changed dramatically when a few months ago, I updated Zigbee2mqtt to version 2 and my whole house stopped working. That marked the moment when the other inhabitants in my house decided that the home automation project had gone too far.
Since then, when I saw an update was available, I’ve waited - preferably until I had seen other people reporting that stuff still worked. But now I’ve realised, that if I wait too long with an update, another update just comes along…
Can I somehow configure HA to always automatically install e.g. update 2.1.3 once update 2.1.4 becomes available? Or is that a nogo too? I realise that the only sure-fire way to do this is with a staging environment, where everything is tested out before updating the production environment. But how many of us has that kind of a setup?
I wouldn’t use that policy because what if 2.1.4 includes a fix for an issue in 2.1.3?
My update policy is wait until a month comes put, then update to the newest previous month’s version. Patches for bugs go into mainline and are backported so this minimizes bugs in the new features.
@chaospatterns
It is interesting how many people think that an update could not contain previous bugs, if they just wait long enough for the installation…
There’s no guarantee bugs get fixed in a newer version, but there’s a higher chance of a software feature working if it’s been out for awhile with a few patch releases than it is for a brand new feature to work day one on a YYYY.MM.0 release. Home Assistant generally holds new features for those YYYY.MM.0, but patches get backported.
@chaospatterns
Yeah, No, it makes sense to wait 2-3 hours after a release to see if the update is bricking something, but otherwise the chances for a bug are the same with every update and feature.
There is an uncountable amount of bugs, that has been previously fixed in the wild, and almost every software on the planet is involved…