Skip to content

Settings reference

Jump to bottom
klaptafel edited this page Nov 4, 2026 · 2 revisions

Every setting lives on the Settings tab (nothing is asked for during setup itself). This page covers what each one actually does.

Master switch

A single switch (switch.update_manager) that pauses all auto-install activity in one click, without touching any of the rules below, so flipping it back on picks up exactly where it left off.

Per-size rules

Small, medium, and large updates (see how a release is sized under How auto-install decides) each get two independent settings:

  • Wait: how many days a release has to exist before it counts as "ready" (0 to 365). Defaults: 1 day (small), 3 days (medium), 7 days (large).
  • Auto-install: whether Update Manager presses install itself once the wait is over, or leaves it for you to do by hand. Off by default for every size, on purpose: auto-install is enough of a step up in consequence that it should never switch on silently.

Announce countdown

How long a cancellable countdown runs before a scheduled auto-install actually executes, from 1 hour up to 336 hours (14 days). Defaults to 24 hours.

Entity overrides

Two opposite, mutually exclusive lists (an entity can't be on both at once):

  • Excluded entities: never auto-install, no matter what the size/wait rules above say. Still shown normally in Updates/History. Core, Supervisor, and OS start out on this list by default.
  • Always-auto-install entities: skip the wait and the announce countdown entirely, installing the moment the update is available, size rules and community votes included. The strongest override this project has, only a manual "Skip this version" outranks it.

Weekday & time restrictions

Optional, shared across all sizes: restrict when an update is allowed to become "ready" at all, e.g. only ever on Saturdays, or only after 20:00 on weekdays. Enable it per day, with an optional specific time for that day (leave the time blank for "any time that day"). This layers on top of the wait/auto-install settings above, it doesn't replace them: an update still needs its wait to elapse too.

Trusted voters

A list of GitHub usernames whose own "healthy" vote on a specific version jump overrides your size/wait rules entirely, skipping straight to ready. See How auto-install decides for exactly how this weighs against a problem report from someone else.

Updates tab display filters

These only change what the Updates tab shows you, nothing about what actually installs:

  • Hide postponed updates (default: on): hides updates waiting on a newer Home Assistant Core version.
  • Show skipped updates (default: on): include entities you've used Home Assistant's own "Skip this version" on.
  • Show not-installable updates (default: on): include entities Update Manager can't currently install for some other reason.

Clone this wiki locally