homeassistant

15548 readers

12 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.

Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation

Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk

founded 2 years ago

MODERATORS

GreatAlbatross@feddit.uk

greatalbatross@lemmy.world

Update policy? (lemmy.world)

submitted 3 months ago by oz1sej@lemmy.world to c/homeassistant@lemmy.world

15 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

[–] Cyber@feddit.uk 3 points 3 months ago

I agree, this pretty much covers all the points.

I do full disk backups of HA, Zigbee2Mqtt, etc every now & again as well as backups before updates.

And I don't so updates when I'm in a rush - that angers the bug gods who strike my systems down with system faults.

Do it on a Saturday morning and it all goes smoooooothly