Never had a problem with that. But every month I start already with the .0b0 release, so I know already what to expect. More people should run the beta’s. Just don’t do it on your production HA instance.
<<Just don’t do it on your production HA instance.>>
Thats interesting.
How can I setup a test instance?
Would’nt there be conflicts in the network?
Can I even simulate a conbee stick?
Guys, following this issue, I would like to be able to have a “prudent update” option to upgrade to the latest previous version (which means being one month late on the updates).
e. g. : I’m on HA 2021.8.8, HA 2021.10.0 is out and I have a “prudent update” option to upgrade to HA 2021.9.9 (whatever the latest version is)
I know it wouldn’t be 100% safe but it would be more safe.
What do you guys think about it ?
If you always wait with the update until a day around the 30th of a month, that would have the same effect. Make a calendar series for always the last monday or tuesday etc of a month
Yes, time consuming non automated stuff is probably what we all want here
The google drive backup is really worthwhile installing, i killed my HA instance ages ago, was my fault.
Spun up new vm, minimal setup, install google drive addon, pulled the backup down and restored in like an hour.
The comment about not wanting to spend an evening restoring, you click the update button so you have to take some responsibility if it goes wrong. Click it when you have an evening spare.
Everyone should plan at least a little bit for any update to go wrong on any device or software.
The Samba Backup add-on is great too if you have a NAS.
I know this wont help you but maybe in the future. Always transfer the backups to other devices. Im using an automation which sends backups to my nas.
Sounds like you should update the last day of the month? (as the new major release is always in the first week of the month and the last week usually doesn’t have any updates)
When I upgrade from Windows 10 to Windows 11, i plan some time to fix possible issues. But when i install monthly updates for my Windows 10 system I assume everything works after a reboot. If there is a 1% chance that the system does not come back online, people would not be using Windows.
would be great to know if this is something the team is working on.
I have Gas (and Water) with analogue meters and would like to add them on a regular basis (like weekly/monthly). There are some workarounds, but seem to be quite tricky and buggy. So before doing all the work for a workaround, I’d like to know if manually adding consumptions is a work-in-progress feature
Lets take yesterday for an example, I had a Teams meeting scheduled in and I knew I had a windows update to do. Yea I could update it in time because I have about an hour before the meeting but the meeting is potentially worth a new customer to me so I will wait, just in case.
I always recommend to anyone, as you are about to click the button just think “what happens if it doesn’t come back” then plan for it.
The difference here is HA is tied in with loads of other components and services with lots of bits having to come together python, rest and all the potential custom components.
It is more like upgrading a service for customer with say IIS, SQL backend with SQL reporting services and some dum dum also made it the DHCP server there is much more to consider then just pressing the windows update button.
Same thrown errors here with 7 Z2M Tuya plugs. The state class ‘total_increasing’ is not available. I cannot change from measurement to total increasing running 2021.9. Is this right?
What if I forget or I am unable to do it in that window ?
The problem is you can only update to the latest version from the user interface.
I will probably update to the previous version of a new release via SSH now but a basic end user (who is probably or will be the target for Home Assistant) will not be able to do that.
Again that happens because there are many people running insider builds of windows and update previews that beta test before released on patch Tuesday and even then there are issues with updates.
Did you upgrade to Zigbee2Mqtt 1.21.1 already ?
This is NOT a problem as the energy keeps on working. Z2M will be updated eventually, in the meantime it still works.
I agree.
There should be an option in the gui to stay one month behind and thus be on the “final” version of the previous months build, rather than having to learn “don’t install the .0 version” the hard way.
I don’t think there are enough problems to warrant putting off the updates so long but to be fair if there isn’t anything new in the update you need there is little reason to upgrade unless you are like me and just have to be on the latest.
Problem with waiting until the end of the month, especially someone who isn’t Mr Super Tech probably isn’t going to even read the breaking changes anyway so if 2021.8.7 is going to break something at the beginning of the month it is still going to break it at the end of the month.
There is certainly merit in waiting for x.x.1/2/3 or whatever to make sure a new major release has some bugs worked out.
been pointing at that need in dev_energy and beta, but kept hitting the wall of ‘Water is not energy’ repeatedly.
Honestly, I don’t understand the core team doesn’t see water is the Resource to focus going forward in reducing our homes ecological footprints (less water is less energy, water stores our heat pumps energy, etc etc ) and thats only local. Why do we have a CO2 sensors for global indication and not Water?
In a household with 4 daughters, it is very clear water == energy no denying there.
Glad you mention it here atop of the thread, maybe we can get some traction…
a nice link Water-energy-food nexus - WUR on the subject