Version 5.2.0
Changelog
* **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.
* **5.1.0:** Added optional notify.send_message support for modern
notification services (e.g. Telegram). Both legacy notify and
send_message can be used simultaneously.
* **5.0.2:** Removed deprecated sensor.backup_manager_state. Backup is now
treated as blocking (hassio.backup_full is synchronous).
* **5.0.1:** Moved release URLs to the final notification to avoid the
255-character log limit.
* **5.0.0:** Added optional pre-run backup, release notes in notifications,
and day-of-week filtering.
* **4.1.1:** Robustness fixes for state handling, log truncation, and entity
filtering.
* **4.1.0:** Fixed install_timeout to use minutes instead of a time-of-day
selector.
* **4.0.0:** Major robustness improvements for resume handling and
notifications.
* **3.0.0:** Major refactor with all review improvements applied.
Advanced Auto-Updater with Smart Resume, Backups & Final Notifications
Stop worrying about manual Home Assistant updates
Are you tired of constantly checking Home Assistant for new updates and installing them manually?
With this automation blueprint, you don’t have to worry about that anymore.
This blueprint automatically detects pending updates and installs them for you in a safe, controlled order — including optional pre-run backups, retry handling, restart survival, and exactly ONE final notification when everything is done.
This blueprint automatically detects all pending Home Assistant updates and installs them for you in a safe and controlled order — including notifications, backups, and automatic handling of restarts.
What does this blueprint do?
This automation is a robust, set-and-forget update manager for your entire Home Assistant ecosystem. It gives you granular control over what gets updated and executes everything in a safe, strict order.
It starts on your chosen daily schedule and can be limited to specific days of the week. Before installing the first update, it can optionally create a full Home Assistant backup, giving you a clean rollback point.
From there, it installs updates in a smart sequence: first Add-ons and HACS/custom integrations, then Supervisor and OS, and finally Home Assistant Core.
Because OS updates may reboot the system and Core updates restart Home Assistant, this blueprint is specifically designed to survive restarts and continue automatically after boot. It tracks progress using helpers, resumes from the correct stage, retries failed Add-on or HACS updates, and sends a single consolidated notification only after the full run is complete.
Key features
Granular Control
Choose exactly which update types should be installed automatically:
- Add-ons
- HACS & custom integrations
- Home Assistant OS & Supervisor
- Home Assistant Core
Day-of-Week Filtering
Only allow the update run to start on the days you choose.
Optional Pre-Run Backup
Create a full Home Assistant backup before the update sequence begins.
Smart Sequencing
Updates are installed in a safe order to reduce dependency issues and instability.
Smart Retry Loop
Automatically retries failed Add-on and HACS updates up to your configured maximum.
Restart & Reboot Survival
If Home Assistant restarts after a Core update or the system reboots after an OS update, the blueprint resumes automatically on startup.
Zero Spam Notifications
Sends exactly ONE final notification at the end of the full run.
Release Notes Links in Final Notification
Release URLs are gathered for the final notification instead of the live log, avoiding the 255-character helper limit.
Robust State Recovery
Built-in guards detect and clear stale, stuck, or out-of-sync run states.
Update order
To minimize risks, avoid dependency breakage, and handle reboots safely, updates are installed in this exact order:
- Pre-run backup (optional)
- Add-ons
- HACS & Custom Integrations
- Retry loop for failed Add-on/HACS updates
- Home Assistant Supervisor
- Home Assistant Operating System
- Home Assistant Core (always last)
This structured approach ensures that supporting components are updated first, while reboot-triggering updates are handled at the end.
Notifications & Log Output
You can configure one or more notification services, such as:
notify.mobile_app_your_phonenotify.telegramany other Home Assistant notify service
During the run, the automation stores a compact progress log in a helper so the update state survives restarts and reboots.
At the end of the sequence, the blueprint sends a single easy-to-read summary showing exactly what happened, including:
Successfully installed updates
Updates that failed
Retry attempts for failed downloads
Pre-run backup result
Release note / release URLs
Any updates still pending
Example final notification:
✅ Updates completed
──────────────────────────
💾✅ Backup
✅ Node-RED
✅ HACS
❌ Mushroom [R1]
✅ Mushroom [R2]
✅ Supervisor
✅ HA OS
✅ HA Core
📋 Release notes:
🔗 Mushroom: https://...
🔗 HA Core: https://...
Important notes & risks
System restarts and reboots
If you enable OS or Core updates, Home Assistant will temporarily go offline during the process.
Breaking changes are still possible
An update may install successfully but still require manual fixes to dashboards, integrations, or automations afterward.
Backups are strongly recommended
The new pre-run backup option adds an extra safety layer, but always make sure you have enough disk space and that your backups are stored safely.
Helpers are required
This blueprint relies on helpers to track:
- the update log
- the current stage
- whether a run is active
- whether the final notification has been sent
Log helper length matters
The log helper should be limited to 255 characters, which is why release URLs are only included in the final notification.
Best for hands-off users who understand update risks
This blueprint is ideal for users who want mostly autonomous update management and are comfortable with the inherent risks of automatic updates.
