@matze.lingen Updated the config, also added the new notification method re import the blueprint and you also have it.
1 Like
thanks a lot worked great
Doing this or just only installing updates that are >7 days old is a very reasonable automatic way of avoiding faulty releases 99%+ of the time.
i was a bit to early after the new blueprint it worked like one ore two times and after that i am only getting emails like this:
i use it in 2 different HAs and it stoped working on both 
sorry
anything i can help you with the troubleshooting?
How does the age of the update make it better?
If there is an issue then there will still be an issue, or do I miss something?
Here is the update schedule for april.
2026.4.1 - April 3
2026.4.2 - April 11
2026.4.3 - April 17
2026.4.4 - April 24
So your method would only install .2 release
Those are all HACS integrations which require a restart after an update. They possibly were updated previously and are still waiting for a restart to be applied properly.
I suspect the new updates can’t be installed before the older updates are applied. Check your settings or repairs screen - you’ll probably see a notification telling you that you need to restart to apply the updates.
Because typically, if there are large breaking issues, they are discovered quickly and then fixed.
Point releases are typically more bug fixes, so typically don’t introduce a lot of new issues and are inherently safer.
But each to their own. I’m not interested in arguing over it.
What happens if you manually start the update ?
it worked. and they are installed
You are clearly not the target audience for this blueprint. Lots of people (including me) have run hundreds and hundreds of updates without issue and prefer the headache of a missed breaking change every year (or maybe never) over spending time reading countless release notes saying "bug fix". Not everyone have the same amount of time at hand and it's different how we choose to spend it. I spend it with my kids instead of reading about bug fixes. If it breaks I do a rollback in minutes and it's fine again. I only had 1 instance of not being able to start since 2020 and it wasn't because of an update. And my setup is a mess of HACS and custom stuff so my feeling is it should break more often but it never does.
I see instead of just not installing the blueprint, you keep coming back to post your negative view on it. Why is this?
Just consider it as a Warning, and move on, do what you fell comfortable with.
Next time an Auto-update occur and potential break things, and when you wake up, and have to go spending time with your Kids, make sure you don’t disappoint them, because you have to fix your Home-Alarm or Heating system Automations
PS: Do notice that my previous commends (those 2 “keep coming back” ( Within few first hours ) was a month ago, when this was “released”, And OP’s has made further Changes, to his initial Post ( Thou non which rocks with the fundamental risks of Auto-Update of HA/Apps/integrations, however with a slight “warning” ) i then clicked “Normal” on this Topic, to avoid seeing further Commends, ( Unless someone found a reason to Address Me, Calling upon my Attention )
Your experience is not of relevance to me , and most likely also suffering from concrete facts , so why spend time on posting/replying just to make me “Come Back” with my “negative” thoughts.
2 Likes
Most updates in ESP-Home is new features and it just doesn't make sense to update to get new features that your old yaml doesn't use.
You are wearing down the write cycles on the chip, risking unrecoverable failures which could mean you need to plug in the device with USB to flash it.
If there is something wrong with your devices then sure do the updates if there is a bug fix for that specific part, but only a fraction of the updates really do any change to your device since ESP-Home does not install stuff you don't use.
So the binary of pre update and after update is exactly the same.
Unless there is a breaking change that ruins stuff for you.
So what are you gaining on all these updates?
This cannot be true if you just press the update button every time on ESP-Home devices.
There has been numerous breaking changes with wifi and API, or something like that, that you need to change your yaml before updating.
1 Like
For me it is not running fine I now have an update since yesterday for an add on and it is not getting updated. What can I provide to finde the issue?
I feel the shade strongly.
I am looking at the combined wisdom, history, and experience of the first dozen or so responders to this thread who did so with alarm and caution, and how the release has coped with a few updates, and how it will cope with the battering of a core or ZigBee change over the next month or so, and reserve my judgement.
I trust the developers have the ability to automate updates and choose their deploy options based on experience, technical support load, and hindsight.
Should this app prove to be faultless and consistent, it may sway a few opinions.
In the meantime, I will not blindly rush in to comprehensively alter my operating environment so carefully nurtured over time and patiently coaxed and wrangled into meeting my needs by reading the carefully prepared release notes, focusing particularly on breaking changes, and watching the forums for newly reported problems immediately after releases.
Cutting edge: yes. Bleeding edge: I'll gleefully leave that to others with a smirk and helping hand, thank you!
Did you install the latest blueprint ?
It has error detection, it writes it in the HASS loggs
Would love to help you to find the root cause to make the blueprint better.
- 5.2.0: Added detailed failure reason logging to system_log with level
error. Failed updates now log entity state, installed/latest version, and
timeout info. Uses logger
homeassistant.components.automation.advanced_auto_updater for easy
filtering.