Repository navigation
Known limitations
Staging rules apply per update size (small/medium/large), not per individual entity: an entity can be excluded entirely, but can't get its own, different waiting period.
- Only works for entities identifiable as a Marketplace integration, Home Assistant Core/Supervisor/OS, a recognized Zigbee device model, or an app.
- Casting a vote requires linking a GitHub account (a quick one-time device-flow step); reading verdicts doesn't.
- A vote (and the community block) applies to the exact version jump. A negative verdict on 1.0.0 to 1.0.1 has no bearing on a direct 1.0.0 to 1.0.2 jump: those are tracked as entirely separate votes.
Only applies when Update all or auto-install triggers the install. The detail dialog's own "Open update" button just opens Home Assistant's native update dialog for the actual install click, same as clicking an update anywhere else in Home Assistant, so none of those go through Update Manager's pacing at all.
An update needing a newer Core than you're running shows as "Postponed" (required version included) instead of being retried or failing; resumes automatically once your Core catches up.
An entity with this per-entity toggle on (common for some Apps) is installed by Home Assistant itself, so Update Manager never announces or auto-installs it, to avoid racing that.
Hiding postponed updates still can't hide it though: Home Assistant's own skip action refuses to run on any entity with this toggle on, turn it off for anything you want Update Manager to actually manage. A live toggle can take up to 15 minutes to show up here, that's Home Assistant's own Supervisor polling interval, not something Update Manager controls.