v0.17.0

A calmer, more native-feeling interface, plus fewer repeat notifications.

A calmer, more native-feeling interface
Timer pills, the status alert, and verdict pills now use Home Assistant's own badge style instead of a custom one, sized to match. The timeline now has its own soft background and skips an extra line when it's not needed. Hovering over a row no longer shows square corners poking through the rounded card. The dialog header's fallback icon also scales properly now.

Fewer repeat notifications
A flickering entity, a Zigbee install queue moving forward, or a restart could each make you get notified again about something you'd already seen. Fixed.

If you use the notify Blueprint, re-import it too. It got a few fixes of its own this time.

Also in this release

• Trusted voters (Settings tab) now has its own picker dialog, same as the Never/Always lists already did, instead of sitting inline on the page. It also accepts a full GitHub profile link now, not just a username. And none of these three pickers save themselves anymore the moment you pick something: Close is now Save, and only takes effect when you actually press it.
• The update dialog now shows real community stats: an open-issue count, and how many times the version you're looking at has been downloaded.
• A postponed update could wrongly show "Up-to-date". Fixed.
• A History entry's install method is now left blank instead of guessed, when it genuinely isn't known.

👋🏻

v0.16.0

A redesigned update-detail dialog ✨

Opening an update now shows a cleaner header: its real icon or brand logo centered above the name, with status shown as a small badge underneath. A new menu on the header links out to Marketplace/HACS, the repository, or its issues page, whichever actually apply.

Also in this release:

• Rounded corners on every entity picture throughout the panel, not just the hard square Home Assistant shows by default.
• Entity names now match Home Assistant's own current naming style (the device's own name), everywhere in the panel.
• List rows now show "installed → latest" instead of just the latest version, matching the History tab.
• Fixed: a failed update could keep showing its "Installing" spinner forever.
• Fixed: a long entity name in the dialog's title bar got cut off mid-word.
• Fixed: the notify Blueprint's notification queue could fill up during a big "Update all" batch, raised from 10 to 30.

The Wiki's Understanding the interface page now walks through what every badge actually means, with real screenshots. Running into something odd, or just have a question? Open an issue or start a discussion on GitHub, always happy to help.

👋🏻

v0.15.1

A too-old-Core "Postponed" update is now detected the moment it first appears, straight from the repository's own release info, instead of only after a real install attempt already failed. Also now sorts to the bottom of that section.

"Update all" on a real batch could also fail some installs outright, racing against itself during HACS's own backup step. Every install now waits its turn.

👋

v0.15.0

A notify Blueprint for your phone

One importable automation for scheduled, installed, failed, and "needs a manual install" notifications, with an Install button on the last one, each switchable independently. Built on two new sensors, sensor.update_manager_pending_installs/sensor.update_manager_failed_installs, also readable directly by any other automation. Import it directly, or see the Wiki for simpler examples.

Also: the README is now a short pitch, deeper stuff (a new Settings reference, troubleshooting, how auto-install decides) moved to the Wiki.

Added

• A Marketplace custom card can now show a real icon in Update Manager's lists, by shipping a brand/icon.png (optionally dark_icon.png) at its root, same as an integration already can. See the Wiki's "For card authors" page.

Changed

• Now requires Home Assistant 2026.11.0 or newer. The two repair issues this integration can raise are now tied to its own config entry, cleaned up automatically if it's ever removed.

Fixed

• An entity postponed for a too-old HA Core version could keep showing in "Scheduled updates" forever, since nothing ever re-checked it.
• A reload/restart (or the panel's own refresh button) now re-checks auto-install state immediately, instead of waiting up to 5 minutes.
• The update-detail dialog could open showing the previous entity's scroll position.
• A release's update_manager.zip asset could be missing, breaking HACS downloads. Now built and attached automatically.

👋

v0.14.0

Hi everyone! 👋🏻

Updates that need a newer Home Assistant Core now wait for it

Some Marketplace/HACS repos set a minimum HA version in their own manifest. Installing one too early used to fail outright, with auto-install blindly retrying every few minutes forever. Now shown as "Postponed" with the required version, and it resumes automatically once your HA Core actually catches up.

Entities managed by Home Assistant's own "Auto update" are no longer raced

If an entity has Home Assistant's own per-entity "Auto update" toggle on, Home Assistant already installs it on its own schedule. This integration used to still try to announce and auto-install it too, which only caused confusion. The Updates list and detail dialog now show a "Managed by Home Assistant" badge instead. Thanks to @Kurisutian for the detailed report and reproduction data (#15)!

Added

• Updates that need a newer Home Assistant Core now wait for it, shown as "Postponed" with the required version. Resumes automatically once your HA Core catches up.
• A failed Marketplace install caused by its own first-run warning not being accepted yet now says so directly, instead of a generic "check the logs".
• An entity with Home Assistant's own "Auto update" toggle on is no longer announced or auto-installed by this integration. Shown with a "Managed by Home Assistant" badge instead.

Fixed

• A version with a fourth "hotfix" component (e.g. v0.5.9.1) was always classified "Large", however small the change. Now treated like an ordinary patch bump.
• HACS-origin detection didn't recognize HA 2026.11's new "Marketplace" platform, breaking community-vote identification for existing HACS-installed updates.
• A batch of simultaneous auto-installs could fail with OSError: Directory not empty (HACS's own shared backup directory racing itself). Installs are now serialized.
• Several near-simultaneous GitHub token refreshes could each log the same failure. A short cooldown now avoids the repeat.
• A panel error with no real message could show as the literal "[object Object]". Now shows the actual detail.

Thanks as always for the issues and reports, they're what keeps this moving forward.

v0.13.0

Two things in this release: Update Manager is now searchable directly in HACS, and auto-install failures handle themselves much more gracefully.

Update Manager is now in the HACS default store

Search for "Update Manager" directly in HACS. No custom repository needed anymore.

Auto-install failures now back off and keep trying on their own

A user reported auto-install silently failing and retrying over and over on a repeated HACS download error (#12), with nothing showing it was stuck. Tracing it down turned up a real, widespread HACS bug (hacs/integration#5643, not yet fixed upstream), and a gap worth closing either way: a failed auto-install retried every 5 minutes forever, with barely any visibility, and manually clicking Install yourself to work around it gave even less.

Escalating backoff instead (5 min → 15 min → 1 hour, capped), shown exactly like any other scheduled auto-install everywhere in the UI, including for an "Always auto-update" entity, which previously showed nothing at all while quietly failing and retrying. Keeps trying on its own with no further action needed; it should resolve itself once whatever's actually broken gets fixed.

Also in this release

• Clicking Install (or Install all) yourself in the panel gave less failure feedback than an automatic retry. Now shows the same "Failed updates" notification an auto-install failure gets, just without starting an automatic retry of its own.
• A Home Assistant Core (or OS) update could show up in History as install method "External" instead of "Manual", or not make it into History at all, depending on timing. Fixed a third code path that had the same gap two earlier fixes already closed elsewhere.

v0.12.2

Fixed: a community vote's own reported link could be crafted to run as a script instead of opening as a page, if you ever clicked it. Links are now only ever clickable when they're a plain http(s) address, anything else shows as plain text instead.

v0.12.1

Two small cosmetic fixes in the update-detail dialog's timeline: a misleading "below" in the held-back text (the verdict it points to actually shows right above it), and a mismatched icon/gap size on your own reported reason when it sits next to another detail line in the same step.

v0.12.0

Hi everyone! A big one: new services for automations, a new standing "always auto-update" override, and a handful of fixes found along the way. Thanks to everyone who tested across three betas.

New services: get_release_notes and cancel_scheduled_install

Two new services (Developer Tools > Actions), the first this project has ever registered. update_manager.get_release_notes returns the exact same compiled, decorated release notes the update-detail dialog itself shows: the right version range, an add-on's own embedded link to a real upstream project chased and appended where applicable, issue and mention references and emoji decorated the same way, and the real blog announcement link for a Home Assistant Core update instead of a plain GitHub releases link. update_manager.cancel_scheduled_install cancels a scheduled auto-install. Both let an automation react to the existing update_manager_announced event on its own, for example running its own analysis of the release notes through Home Assistant's own AI Task, a local LLM, or anything else, before deciding whether to let a scheduled auto-install proceed. update_manager_announced itself also gained a release_url field. See discussion #11 for a show and tell example of using this. Closes #9.

Always auto-update list

Entities on this new list install the moment a new version is available, skipping the staging wait, the announce countdown, and the community vote check entirely. This sits alongside the existing "Never auto-update" list, previously just called "Always manual". Each list now shows a configured-entity count with a button that opens the picker in its own dialog instead of inline. Closes #10.

Also in this release:

• "Ready all" button in the Postponed group, next to "Update all" in Ready to update.
• Fixed: a tier-gated Core or OS update that had genuinely already succeeded could still trigger a false "couldn't install" notification, caused by a restart racing against the tier gate's own bookkeeping.
• Fixed: a Core or OS update installed through Home Assistant's own native dialog could show up in History as "External" instead of "Manual".
• Fixed: the detail dialog's scroll position leaked between different updates. Each one now remembers its own, the same way the tabs already do.
• Fixed: a GitHub token refresh race could mark the linked account broken and demand an unprompted re-link, even though nothing was actually wrong.
• Fixed: the release notes loading spinner flashed even when the notes were already cached, making a cache hit look like a fresh reload.

As always, let me know if anything looks off after updating.

v0.12.0-beta.3

Fixed

• get_release_notes now matches the update-detail dialog exactly: the changelog is trimmed to just the relevant version jump, an add-on whose own notes just point at a real upstream project (e.g. Zigbee2MQTT or Mealie) gets that upstream project's release notes appended, text is decorated the same way (issue/mention links, emoji), and a Home Assistant Core update gets the real blog announcement link instead of the plain GitHub releases link.
• A tier-gated Core or OS update that had genuinely already succeeded could still trigger a false "couldn't install" notification. This happened because Home Assistant itself restarts as part of that kind of update, which could prevent the queue's own bookkeeping from being saved in time, causing the already-completed install to be retried after the restart. As an extra safety net, this kind of notification is now also never shown at all for an update that's already on the correct version, regardless of the cause.