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?
Yeah, I’ve been dealing with the fallout of doing a firmware upgrade suggested by zwave2js which - I don’t know - changed the IDs on every single one of my 60 z-wave devices. I’ve been going through fixing dashboards, and automations, and scripts. It’s been a major PITA. It is, however, the first time a breakage of this magnitude has happened to me in a decade.
It wasn’t just that devices changed; some stayed the same but the entity value IDs of their functions changed. It was so random.
I’m going to think twice about doing that, next time.