The updates consolidation within settings is great, but it needs to have an “update all” or, better yet, the ability to select updates and execute an “update selection” that performs the selected updates sequentially. This would be super helpful on setups with numerous ESPHome devices.
I definitely agree that there should be an easier way to select all. ESPHome is frustrating because you have to update the add-on, then update all the devices. Currently, I’ll open the Web UI for ESPHome and click Update All to get all the devices, but I wish it were smart enough to update the add-on, then immediately update all devices.
Upvote.
3 Likes
You can write an automation to do that automatically or via an input_button
2 Likes
Speak for yourself 
Here’s a list of blueprints that auto update, just a few clicks in the UI to get them set up
https://community.home-assistant.io/search?q=%23blueprints-exchange%20auto%20update
2 Likes
From an end user point of view, the distinction between HA core and HA OS does not have much meaning. In both cases they result in the device going offline for a while then everything comes back newer.
I think these two should be combined as well as as many others as possible. The experience should be like windows, Mac, Linux, android, iOS, etc. If the user agrees to allow the interruption of updates we should do them all, after one consent.
Also there should be one backup at the start of the batch (saving storage space).
Sure, possible with an automation. But I think this WTH is to avoid the need for the average user to spend time on that.
1 Like
Actually, it’s best that the HA Core and HA OS updates are not combined. HA Core is the application, it has a set release cycle. On the other hand HA OS is released “as needed”, and many times may be addressing issues in the underlying Linux operating system.
I for one would not want a security vulnerability in the OS to remain unpatched for up to a month if it is actively being exploited.
This is a common practice in computing for that exact reason, it’s why Google updates Chrome on their schedule while Microsoft or Apple updates the Operating System on theirs. Those updates aren’t combined.
Which brings us back to this WTH - one click to update all the options in one go gets the number of cycles down to make it more efficient (even the OS’s now include package managers that can do an “update all” from a single request)
1 Like
Ok perhaps my wording wasn’t very clear, I didn’t mean that patches for each should be literally combined into the same release package, it’s ok that they are separate.
But the act of upgrading ‘everything outstanding on the list’ should be available as one action from the user point of view, and still be one action if they don’t care or understand the difference between OS, core, addons etc.
1 Like