homeassistant

13963 readers

133 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 2 years ago

MODERATORS

GreatAlbatross@feddit.uk

greatalbatross@lemmy.world

Update policy? (lemmy.world)

submitted 11 hours ago by oz1sej@lemmy.world to c/homeassistant@lemmy.world

11 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] TedZanzibar@feddit.uk 6 points 10 hours ago

I skim read the changelogs for breaking changes but mostly just YOLO it whenever I'm in the mood to update or a new monthly release drops.

That said, the VM that runs HAOS and the Z2M addon is snapshotted every night with two week's worth of retention, and I let HA do its own scheduled backups in case a snapshot restore doesn't work for whatever reason. So far I've never had a need for either but I rest easy knowing the options are there.