Can't install add-ons due to unhealthy system

1

This is my system information

## System Information

version | core-2025.11.3
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
container_arch | armv7
user | root
virtualenv | false
python_version | 3.13.9
os_name | Linux
os_version | 6.12.47-haos-raspi
arch | armv7l
timezone | Europe/Zurich
config_dir | /config

<details><summary>Home Assistant Cloud</summary>

logged_in | false
-- | --
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok

</details>

<details><summary>Home Assistant Supervisor</summary>

host_os | Home Assistant OS 16.3
-- | --
update_channel | stable
supervisor_version | supervisor-2025.11.5
agent_version | 1.7.2
docker_version | 28.3.3
disk_total | 115.2 GB
disk_used | 3.0 GB
nameservers | 194.230.55.96, 212.98.37.130
healthy | failed to load: Unhealthy
supported | failed to load: Unsupported
host_connectivity | true
supervisor_connectivity | true
ntp_synchronized | true
virtualization | 
board | rpi2
supervisor_api | ok
version_api | ok
installed_addons | 

</details>

<details><summary>Dashboards</summary>

dashboards | 2
-- | --
resources | 0
views | 1
mode | storage

</details>

<details><summary>Network Configuration</summary>

adapters | lo (disabled), enu1u1 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth0377594 (disabled), veth97d5000 (disabled), veth7e9ae02 (disabled), veth9c61a52 (disabled), vethc4702db (disabled), vethff2fab3 (disabled)
-- | --
ipv4_addresses | lo (127.0.0.1/8), enu1u1 (192.168.1.59/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth0377594 (), veth97d5000 (), veth7e9ae02 (), veth9c61a52 (), vethc4702db (), vethff2fab3 ()
ipv6_addresses | lo (::1/128), enu1u1 (fe80::84c7:e35f:8037:783/64), hassio (fd0c:ac1e:2100::1/48, fe80::a080:3fff:fe9e:88aa/64), docker0 (fe80::8858:aaff:fed1:ac5d/64), veth0377594 (fe80::509d:33ff:fe1a:8652/64), veth97d5000 (fe80::5c05:88ff:fe26:3e7c/64), veth7e9ae02 (fe80::c8d6:f9ff:fec6:ca00/64), veth9c61a52 (fe80::f4e4:64ff:fec2:c529/64), vethc4702db (fe80::fc57:c4ff:fe69:e1d/64), vethff2fab3 (fe80::2ca9:77ff:fe80:e047/64)
announce_addresses | 192.168.1.59, fe80::84c7:e35f:8037:783

</details>

<details><summary>Recorder</summary>

oldest_recorder_run | 9 December 2025 at 11:50
-- | --
current_recorder_run | 9 December 2025 at 17:06
estimated_db_size | 0.54 MiB
database_engine | sqlite
database_version | 3.49.2

</details>

I’m aware that armv7 (and therefore my Raspberry Pi 2 Model B) is unsupported with the upcoming release and that that means I can’t update my supervisor, but I don’t understand why that blocks me from installing add-ons on this still supported version of core-2025.11.3.

Any idea on how to get rid of the 'AddonManager.install' blocked from execution, system is not healthy - supervisor error?

Screenshot 2025-12-09 at 18.01.11
Screenshot 2025-12-09 at 18.01.112092×1306 201 KB

2

And with a Pi2 which is also not supported it probably ran out of memory.

You should back-up to a set of mid-year HA versions that match and try that.
I mean you are now stuck at whatever rev forever, you should stick to a version that at least worked at one time.

3

Hey,

thanks for your reply.

The Pi consumes 300MB memory out of the 1GB memory it has. It should also be still supported with the version I’m running.

That’s a good idea and I was considering it, the thing that surprises me is that the system only became “unhealthy” and “unsupported” after the supervisor upgrade (as intended) failed. Now I can’t seem to get out of this state which in turn prohibits me from installing add-ons.

IMG_4458
IMG_44581125×2436 163 KB

4

I too have still a Raspberry Pi 2B running. What I have see that a lot of add-ons have received updates lately that removed 32bits. So lastest versions can’t be installed anymore.

Did you try a host reboot, not just a HA restart?

5

Yes, unfortunately a full reboot and also disconnecting from power did not help. I’ll try with a fresh install where I don’t try to update the supervisor

6

Doesn’t work either, I might try downgrading to 15.2 later today and see if that does the trick.