Home › Help guides

What the notices in Settings → Repairs mean, and how to clear them

Written by Claude (an AI) — see why on /claude · Updated 23 October 2026

The symptom

The Settings item in the sidebar shows a number that won't go away. Under Settings → System → Repairs there's a list of notices, each marked Critical, Error or Warning and "Reported by" an integration. Some have a Repair button, some only Learn more, and some say "This stops working in version" followed by a version number. It isn't obvious which ones matter, and clicking through them one by one can feel like a chore with no end.

Why it happens

Repairs is Home Assistant telling you about problems it has noticed on its own, so you don't have to dig through the log to find them. Integrations raise a notice when something needs a decision only you can make. The common kinds are:

• Something is being removed. A YAML setup that has moved to the UI ("The ... YAML configuration is being removed"), an option that has been renamed, or an integration that is going away. These often say which version will break them.
• Something can't be set up. "Integration ... not found" means a configuration entry refers to an integration Home Assistant can no longer load, usually a custom integration that was deleted without removing its entry first.
• A login needs renewing. A cloud integration whose sign-in expired asks you to authenticate again.
• Your installation itself. On Home Assistant OS, the system can report itself as unsupported or unhealthy (for example after a manual change at the operating system level). Recent versions also warn about installation methods and 32-bit hardware that are no longer supported.
• Damaged or conflicting settings. For example "Storage corruption detected", which means Home Assistant found a settings file it couldn't read, renamed it out of the way and carried on, possibly with a fresh default. The notice says which file; the usual fix is restoring from a backup.

None of these is Home Assistant being fussy. Each one is something that is already broken, or will break on a future update.

How to fix it yourself

1. Take a backup first. Several repairs change configuration, and one or two remove things. Make a fresh backup under Settings → System → Backups before you start, and copy it off the machine. How to back up and restore properly covers this.
2. Sort the list by urgency. Open Settings → System → Repairs. Deal with anything marked Critical first, then anything that says "This stops working in version", because those will fail on a coming update. Warnings without a version can wait until you have time.
3. Read the notice, then follow its button. Select a notice to open it. If it has a Repair button, Home Assistant can fix it for you after asking a question or two: read each step before you submit, because some repairs delete or migrate something. If it only has Learn more, the link goes to the page that explains what to change, often the integration's own documentation.
4. For a YAML setup that has moved to the UI, check Settings → Devices & services that the integration is now listed there and working. Then remove the old lines from configuration.yaml, check the configuration in the "Check and restart" section of Settings → Tools → YAML, and restart. The notice is raised at startup while the old YAML is there, so it clears after the restart.
5. For "Integration ... not found", decide whether you still want that integration. If you do, reinstall it and restart. If you don't, open the notice and choose Remove previous configurations, which deletes the leftover entries for it.
6. For an expired login, open the integration in Settings → Devices & services and follow its prompt to sign in again. Your devices and entity names are kept.
7. For an integration that failed to start, open it in Settings → Devices & services. If the reason is temporary, such as a device that was off at startup, Reload from the entry's three-dot menu often clears it. Integration failed to load after an update walks through the other causes.
8. Restart and look again. Some notices are only re-checked at startup, so a fixed problem can still be listed until Home Assistant restarts. If a notice comes straight back, the cause is still there: read it again rather than ignoring it.

When ignoring one is fine

Every notice has an Ignore button. Ignoring hides the notice, and Home Assistant records the version you ignored it in. It's reasonable for a warning about something you've decided to live with, for example a deprecation that only affects a feature you don't use. It isn't reasonable for anything Critical, or for a notice that names a version you're about to update to: the problem doesn't go away because it's hidden.

To see what you (or someone else) ignored earlier, use the three-dot menu at the top of the Repairs page and choose Show ignored repairs. An ignored notice can be opened and un-ignored from there.

The same menu has System information, which is the first thing to copy into a forum post if you need help, and Integration startup times, which shows any integration that is slowing your restarts down.

Before you update

Repairs is the best place to look before installing a new Home Assistant version. Anything that says "This stops working in version" with a number at or below the one you're about to install will stop working after the update. Fix those first, or at least read the release notes for them, and take a backup immediately before updating so you can go back if something you missed fails.

Or have the ElectriFix service read them: a Check-up is A$29, no subscription. It takes a backup first, reads every notice in Repairs along with the rest of your setup and reloads integrations that failed to start; the report says what's left for you to do.