hi!
may i ask to make this feature optional?
it doesn’t work! Never. it doesn’t work with any kinds of issue.
http://homeassistant.local:8123/config/logs?provider=supervisor
nothing here.
You likely configured backup to go to a network storage. I suspect you entered the wrong credentials or have some other kind of misconfiguration.
While you could remove the network storage entry and switch to local backup or disable backup, that would be rather unwise. Unless you do not mind losing your entire config on some mishap like a storage faillure.
Sir, sorry. it’s nothing related backup. it just for example.
yesterday was the same issue with another device / plugin - click “Repair issue” - oh sorry, Could not apply the fix. bye bye! 
Sorry to say, but judging by your title, i would have expected more than a few pictures to describe an “Issue”
Could you “click” on /Settings/System/Logs and in top-right corner choose Supervisor , and copy a fraction of the “RAW”-log option and paste it here , formatted correctly, cording to the forums “requirements”
( Top-first post in the Forum ) or just post another picture, if that’s your preferred way )
Yes the last URL in your post bring me to my supervisor log(as it an http (not https) and beside it’s a “local” address , this also requires that your network system can “handle” such correctly
“Optional” ? what the repair-function ? ( Don’t click on it!, it’s Optional) the log reporting ? ( Don’t read it ) which it seems like you doesn’t anyway
Any integration can warn you for impeding harm using a repair. There is no general option to 'Stick your head in the sand", as the Dutch would say.
It needing to reconnect every couple of seconds seems like a problem to me.
If you don’t have time to read, you don’t have the time to write. Simple as that. (c) S King
I am just asking to make repair-function optional with [remove] [reload] [dismiss]
and annoyed message disappears
Report Your Feature Request on HA’s Github-Repo
1 Like
ok, thank you.
FYI
{
"version": 1,
"minor_version": 2,
"key": "repairs.issue_registry",
"data": {
"issues": [
{
"created": "2025-12-24T21:39:55.548504+00:00",
"dismissed_version": null,
"domain": "hacs",
"is_persistent": false,
"issue_id": "restart_required_996854813_tags/v2025.12.7"
},
{
"created": "2025-12-25T10:57:50.252019+00:00",
"dismissed_version": null,
"domain": "hassio",
"is_persistent": false,
"issue_id": "69a6669a5bd7408cb98b441e1d70c7d2"
},
{
"created": "2025-12-25T12:33:23.424056+00:00",
"dismissed_version": null,
"domain": "hassio",
"is_persistent": false,
"issue_id": "27eefa789599433da2d173274e3c27e4"
}
]
}
}
Qee ?, this just shows this “functions” current state ( which you already showed in your picture
You have a Peddle Restart Hanging (+16 hours ) means Restart ! , if that aint gone after a restart , try to reboot , if still no luck post a Topic here (about that) or raise a report/issue in github
stop.
Let’s keep work and pleasure separate.
HACS asking to reboot - it’s ok.
but the question was about repair. this annoyed message for me and i wouldn’t want to reboot my HASS every time when this message appears.
Ok, in your “repair log” you (only )show 3 log-entries( 2 Hassio ), that looks great
All from today, so what happened to the 3rd, did that “repair” actually worked , as you “hoped” ?
Restarting is a ‘sledgehammer’ solution. I’m looking for a way to clear these ghost repairs without a full reboot. The disk (today issue) is fine, the Matter server (yesterday issue) is fine, but the UI is stuck in the past.
supervisor log for today:
e[33m2025-12-25 14:54:34.215 WARNING (MainThread) [supervisor.addons.options] Option 'anonymous' does not exist in the schema for Mosquitto broker (core_mosquitto)e[0m
e[33m2025-12-25 14:54:34.216 WARNING (MainThread) [supervisor.addons.options] Option 'zigbee_herdsman_debug' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)e[0m
e[33m2025-12-25 14:59:34.197 WARNING (MainThread) [supervisor.addons.options] Option 'zigbee_herdsman_debug' does not exist in the schema for Zigbee2MQTT (45df7312_zigbee2mqtt)e[0m
e[32m2025-12-25 15:03:18.881 INFO (MainThread) [supervisor.mounts.manager] Removing mount: BACKUPe[0m
e[32m2025-12-25 15:03:18.942 INFO (MainThread) [supervisor.mounts.manager] Creating or updating mount: BACKUPe[0m
e[32m2025-12-25 15:03:19.058 INFO (MainThread) [supervisor.backups.manager] Found 8 backup filese[0m
e[32m2025-12-25 15:03:24.120 INFO (MainThread) [supervisor.mounts.manager] Removing mount: BACKUPe[0m
e[32m2025-12-25 15:03:24.187 INFO (MainThread) [supervisor.mounts.manager] Creating or updating mount: BACKUPe[0m
e[32m2025-12-25 15:03:24.287 INFO (MainThread) [supervisor.backups.manager] Found 8 backup filese[0m
e[32m2025-12-25 15:03:26.469 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m
e[32m2025-12-25 15:03:28.883 INFO (MainThread) [supervisor.mounts.manager] Removing mount: BACKUPe[0m
e[32m2025-12-25 15:03:28.938 INFO (MainThread) [supervisor.mounts.manager] Creating or updating mount: BACKUPe[0m
e[32m2025-12-25 15:03:29.043 INFO (MainThread) [supervisor.backups.manager] Found 8 backup filese[0m
Ok, so you l left out this “issue” i assume that answer my question ( Yes, that did work, the one at 10.57 is fixed, thank you )
… or was / is it the one at registered at 12.33 we are “working on” ? ( I assume your (bad)day started around 10.57 )
I still don’t get what it is for “feature” you want, fix the issues reported and they will/should “vanish” for the Repair, if it doesn’t report this , as mentioned in the github.
So as i understand you clicked 1 issue and in an instance(a click) Repair fixed it for you( You didn’t even have to look in your logs, or tamper with anything
And now your in a position, where the Repair-Feature can’t fixed the reported issue( which you have no clue about what really is/was ) Anyways “Repair” can’t fix it.
You have to look in your logs for “warning/errors” around the time it occur, Tha’s all the “pop-up” message says
Yes, this " Entry in Repair, will remain, until the reported issue is fixed, or “obsolete”
I wouldn’t be surprised if they both are gone after you “Restart”
So is your “Feature Request” as simple as this ( Don’t show me a pop-up if “repair can’t fix an issue” )
You can have the option to “Choose” ignore, again “ignore hide the reported issue” but it’s still “logged” as you shows in the repair-log, And an issue which ends up in “ignored” will most likely “Vanish” … like after it’s fixed, regardless if the fix is just few clicks away … like i.e “Restart”
Anyways , Good Luck with your “Feature” request
I see you are a big fan of the ‘have you tried turning it off and on again’ approach.
While that works for my grandma :))) I’d prefer a system that doesn’t require a ‘sledgehammer’ reboot to clear a stale notification for a problem that no longer exists.
The issue is obsolete, the logs are empty, yet the UI persists. If you think a 16-hour pending restart is the root of all evil, we clearly have different standards for system stability.
Cheers!
WBR, O.
1 Like
i don’t
Your UI is a Browser-UI, some times flushing the cache helps
Buttom line:
You are dead wrong ( Don’t post this is your “Feature Reauest”
I’ve spent 30+ years developing banking systems, where state management is everything. In professional environments, if an automated ‘Repair’ fails to track a manual fix, we provide a way to manually acknowledge or dismiss the state.
My ‘Feature Request’ is simple: the UI needs an [Issue already solved / Dismiss] button.
Relying on a full system restart just to clear a stale notification is a sign of poor state handling, not a user error. If the logs are empty and the storage is up, the system shouldn’t be stuck in a ‘Repair required’ loop.
Let’s move past the ‘have you tried a reboot’ logic and talk about better UI/UX.
Like “Ignore”
Edit: You do know this "Ignore-Button already exists !?
1 Like
yep. but I can’t see.