Why have to wait, for each esp yaml project to Update to latest version and than to upload. For people with big number esp devices, to wait and update one project is pain. Why not update ALL in background, in HA and than send the new yaml?
Make this a pool to new updates?
Through the WebUI of ESPHome you mean?
There is a FR of someone with more or less the same request: Scheduled bulk updates with a two-phase pipeline (compile at a preset time, then OTA upload), per-device exclusions, and outcome notifications · esphome · Discussion #3462 · GitHub
If you use the CLI, you can already do what you are asking by using the compile command:
Why to update in the first place?
What if update breaks them ALL in background?
You are right Karosm, however I also get the thought process 'ah there is an update, I need to apply it’s that is pushed everywhere else (operating systems, apps on your phone, …)
For example, the recent(ish) change on the framework meant quite a bit of memory saving on the ESP devices here.
I have 3 years old phone and I have never updated the fw. I can’t recommend that to anyone because in this case some safety issues likely exist.
But if I have esphome device that works reliably as I want at this moment, why should I update it for memory savings?
There is good reason to update regularly though, it’s easier to handle breaking changes when they are fresh and limited. Updating every few years can be painful.
But I would not recommend automatic updates. Your devices might break uncontrolled manner on the wrong moment.