Wrong deprecated 32-bit system message

[Maurizion]

The problem

Just updated to : core-2025.6.1 but still deprecated 32-bit message but i don’t understand why :

What version of Home Assistant Core has the issue?

core-2025.6.1

What was the last working version of Home Assistant Core?

core-2025.5

What type of installation are you running?

Home Assistant Container

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

[Maurizion]

uname -a Linux raspberrypi4 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

[joostlek]

Oh thanks for opening an issue, let's discuss it here. What's the content of /etc/apk/arch in the container?

[Maurizion]

Oh thanks for opening an issue, let's discuss it here. What's the content of /etc/apk/arch in the container?

armv7

[joostlek]

What container are you running? You might be running a different arch container on your aarch64 system

[Maurizion]

What container are you running? You might be running a different arch container on your aarch64 system

Yes you are right , the image pulled was based on armv7 arch even if my system is aarch64. Then i was forcing the platform for the image to be linux/arm64 but after that home assistant container seems not to start anymore .....

[joostlek]

How do you force the platform? I believe they are generally well at detecting what image to pull nowadays

[Maurizion]

How do you force the platform? I believe they are generally well at detecting what image to pull nowadays

Using docker compose yaml file:

services: home-assistant: container_name: home-assistant image: ghcr.io/home-assistant/home-assistant:stable platform: linux/arm64 ......

[dhmvk]

I've been reading along because I think I have the same issue.

Running HA in a Docker container. Got the deprecation notice.

/etc/apk/arch gives armv7

I used to use the docker run command without a platform parameter. I've now added it but it doesn't change the result.

docker run -d \ --name homeassistant \ --platform linux/arm64\ --restart=unless-stopped \ [etc]

Also, uname -m in the docker container gives aarch64.

Running on a raspberry pi, Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

[MichaelMKKelly]

someone else on discord brought this up. looks like that it likes to report that the CPU is aarch64 in uname even if your using 32 bit Raspbian

[dhmvk]

Had to search on Google for a while, but found the following.

https://pimylifeup.com/raspberry-pi-os-check-32-bit-64-bit/

This tells us to use dpkg-architecture --query DEB_HOST_ARCH which, for me, returns armhf. The articles states that that is indeed 32-bit.

Honestly I don't know if this is truthful if all other things aren't. How does HA determine if the deprecation message needs to be shown?

[bvdf0251]

Tagging as I got the same today after upgrading.

[ruttromp]

Having the same issue. Pulled docker image is based on armv7.

Setup:

• Raspberry Pi 4 Model B Rev 1.2
• HA as docker image
• OS Debian (bookworm)

Output uname -a on the host: Linux HomeAssistant 6.1.57-v8+ #1688 SMP PREEMPT Thu Oct 12 15:14:26 BST 2023 aarch64 GNU/Linux

[MichaelMKKelly]

@ruttromp try running

dpkg-architecture --query DEB_HOST_ARCH

on the host

[bvdf0251]

@ruttromp try running

dpkg-architecture --query DEB_HOST_ARCH

on the host

Its showing armhf while on HA itself its showing aarch64 as does uname -m

Pulling image via ghcr yml

No architecture line in yml

[MichaelMKKelly]

@bvdf0251

@ruttromp try running

dpkg-architecture --query DEB_HOST_ARCH

on the host

Its showing armhf while on HA itself its showing aarch64 as does uname -m

Pulling image via ghcr yml

No architecture line in yml

yeah, the way the kernel reports is a little strange sometimes. it is a 64-bit CPU but you are running 32-bit software. as you can see your package management arch is set to 32-bit arch type

you will likely need to reinstall your host system using a 64-bit OS image.

[ruttromp]

dpkg-architecture --query DEB_HOST_ARCH Is returning armhf on the host

So the OS is 64 bit and packages are on 32 bit architecture? How did that happen? Would mean I need to reinstall OS.

[MichaelMKKelly]

dpkg-architecture --query DEB_HOST_ARCH Is returning armhf on the host

So the OS is 64 bit and packages are on 32 bit architecture. How did that happen? Would mean I need to reinstall OS.

yes, 32-bit was default for a while on a lot of stuff so probably was an accident. it does seem that a large amount of the people that are using 32-bit are doing so unintentionally.

[VictorDrijkoningen]

I had the same problem on the RPi4 and just changed from the raspberrypi4-homeassistant image to the raspberrypi4-64-homeassistant image, which then fixed the depreciation notice.

[agners]

The system health will report the Container architecture with the next release (see https://github.com/home-assistant/core/pull/147372).

However, when running Home Assistant Core container, ultimately what architecture is supported natively depends on the installed Docker version. The architecture of Docker itself is shown in docker info. If that reports something other than aarch64 on Raspberry Pi, then you have to reinstall a 64-bit operating system (and Docker) to actually run 64-bit versions of the Home Assistant Core container..

The error is correct, as we deprecate the 32-bit version of the container, which your system seems to be using.

[home-assistant[bot]]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (homeassistant) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homeassistant can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign homeassistant Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

homeassistant documentation homeassistant source _{^{(message by IssueLinks)}}