Supervisor confused about HAOS version

Installation Home Assistant OS
1

Supervisor reports a different version in the UI than it does in the console. It seems to think I booted the alternate boot partition. What lead to this was this:

I shut down HA for a power cut, but somehow the shutdown was apparently not complete. After that, hardware reboots took close to 30mins where HA was not available at all, not for SSH either. It seemed like it failed to boot and switched boot partitions to work. It showed a repair that something had changed and it needed a reboot. It also appeared to have booted HAOS 18.0 instead of 18.1 which I had run before.

Several attempts later at installing HAOS 18.0 and 18.1 and switching boot partitions, a hardware reboot now progresses at normal speed on both boot partitions. However, the nagging repair remains, and Supervisor reports the wrong OS version in the GUI. The CLI shows it booted the other partition.

Does anyone have any clues how to fix this? note all the differences in the CLI version and the gui, and also the GUI being confused it should update the OS. When I try it notices the new version is already installed:

IMG1332
IMG13321128×554 70.7 KB

IMG1330
IMG13301208×717 48.1 KB

IMG1329
IMG13291299×1366 145 KB

IMG1331
IMG1331979×1483 174 KB

2

I don’t know answer to your question as I’m using ha core in docker compose.
But doesn’t it seem a bit ridiculous after all questions you have answered for others that you will probably not get any help.
I’m writing this because this forum is went from user to user help to user to keep official narrative.
It just simply killed curiosity different approach to same problems and diversity as a virtue.

3

Stupid question. Maybe browser cache issue?

4

Thank you for brainstorming with me. It is not a stupid question, and no. I purged the cache, but it also switches when I boot the other partition, and OS update notifications also look at the wrong value.

5

If I don’t get answers, it is probably because this is just plain weird. I am also considering writing it up as a bug, because at least one of those places is reporting snot what is real, but what it thinks is real.

6
7

Ah, thanks! That sure looks relevant.

8

Llol was gonna suggest to try to update the OS from the CLI or restore a backup, but @Baxxy13 stepped in just in time.

Guess there is user to user help after all!

9

Updated the hell out of all today. The backup restore I discarded because it does not contain any supervisor or os things.

But yes, help came pretty quick. I just wonder: balloob closed the issue referring to a code change but no clue in what version or how or when it will land in a release. But hey, he’s the boss :slight_smile:

10

Merged into supervisor which updates automatically, so I’m guessing it’ll be released early next month at most.

If there’s another hotfix release of supervisor (this fix missed 2026.07.1 by 2 days), then it’ll be much less than that

11

This is a bug with current Supervisor 2026.07.1, and it will be solved with Detect pending OS update after marking the booted slot good by agners · Pull Request #7022 · home-assistant/supervisor · GitHub. I am about to release a new version which addresses this issue. This only affects users on beta channel (Supervisor 2026.07.1 won’t be promoted to stable).

12

2026.7.2 indeed fixed the problem. Thank you for the fast solution.