I just got my network built & noticed that I’m behind two updates. When is it good to update? Do you update when it first comes out or wait? Can you revert the update if something goes wrong?
1 Like
Most of the time yes but there have been releases where the process was not straightforward (because of certain changes).
You choice of installation method also governs the ease of rolling back a release. If you use the Core installation method (Python app in a venv) that takes more steps to rollback than the other three installation methods.
When I used the “python app in a venv” method, I would typically wait a few versions before upgrading. Now that I am using the Supervised installation method, I typically update as each new release becomes available (perform a snapshot before upgrading so that you can use it in the event of needing to rollback).
2 Likes
when x.b0 comes out lol.
I went with supervised. I seen some people say that it was risky on updating but that was for older versions so it must be different for supervised newer versions. So if something goes wrong does the snapshot actually bring everything back Z-Wave/Zigbee & Node-Red included? Thanks for your time!
If something goes wrong you can easily roll back to a previous version. If you restore a snapshot it would have to be very broken for the rollback not to work but the snapshot will contain all that.
1 Like
Cool great to know that the snapshot will restore it all! 
Since I got all my automations moved from SmartThings. Seems like a great system so far!
Only problem I had was not looking at the OZW Log & getting ahead of the Z-Wave inclusion with making Unknown Nodes LOL The OZW Log doesn’t open up on iOS only Android it seems.
1 Like
Yes, but only on my test-HA machine. But then I’m at least sure what could break if x.0 comes out.
I can count on 2 fingers the number of times I have had to roll back a beta in 2 years and I always test them on my production system.
I typically update my core-installation a day before a new version is published. That way I get a pretty recent version with all kinds of bug-fixes included.
- After careful reading of release notes - thou i still miss some crucial info as not always it is easy to recognize that change might be applicable to you.
- After making necessary changes or be prepared to makes these in confiuration - this minimizes downtime if something requires to be updated.
- After making sure that I have recent backup and snapshots created
- Every single time new version arrives… skipping versions might make update process a nightmare due to accumulating breaking changes.
1 Like
Lately I’ve been on an “every other” update path since probably 0.9X versions and sometimes I’d even skip an extra one or two in there, but that’s because I’ve tried to transition from tinkering with the system to using the system. If a component broke (MyQ is the biggest one for me) I will typically try to just update that component with the bug fix. If too many components break or a few components have new features I want to eventually try out, then I will ear-mark that version for my development environment to test, then update my production environment after a few days to see if a point release shows up in the waiting period. Most of my updating is done on weekends either late at night or early in the morning so I have some time that I’m actually home to verify everything I use on a day to day basis works and test out new features I implemented. I read the breaking changes of every release regardless if I update to it or wait so I’m prepared. I then use my development environment to verify my configuration is correct and implements the breaking changes so I don’t have any nasty surprises when that version goes live.
Clone / Image your disk before you update and then you won’t need to worry about reverts. But, that’s generalized good computer advice.
Personally, I only update if something stops working or I need a newer component / feature.
I administer two different HA instances, 1 at home and 1 at the office (both in venvs on Ubuntu 18.04).
Office instance remains 1 full release version behind unless API / service changes force my hand (e.g. the pymetno update in 0.111.4).
Home instance is updated to each new release usually the weekend after the release, depending on community feedback / reported issues or if I’m waiting on an imminent fix.
I review all the release notes and the accompanying feedback threads prior to upgrading, and both instances are backed up each night using some hand-rolled Python scripts (Office to USB drive, Home to NAS share which is then replicated out in my standard backups of backups flow).