32-Bit notification on 64-Bit system

[n0r]

The problem

Hi, after upgrading to 2025.6 I received the notification that my system is running on the to be deprecated architecture 32-Bit.
I am pretty sure that my System is running on 64-Bit (Hopefully nothing overseen).

This is what my system states in various places:
Host: Raspberry Pi 4, Linux [...] 2023 aarch64 GNU/Linux
Home Assistant Docker container: aarch64 Linux
System Information from Home Assistant Frontend: aarch64

Maybe some other users are facing the same issue or have a quick solutions.
Kind regards

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.4.4

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

[MichaelMKKelly]

possible dupe of #146806
can you run this on the host system:
dpkg-architecture --query DEB_HOST_ARCH
and post the result?

[cyberrock]

dpkg-architecture --query DEB_HOST_ARCH
arm64

[n0r]

dpkg-architecture --query DEB_HOST_ARCH

Sure:
armhf

[MichaelMKKelly]

@n0r

dpkg-architecture --query DEB_HOST_ARCH

Sure: armhf

then you are running a 32 bit OS. you will need to reinstall your OS and ensure its the 64 bit version. uname lies to you (sort of) but the package manager reveals what is actually installed. if its any consolation this is a fairly common issue and people don't realise they have actually been running 32-bit the whole time.

[n0r]

@n0r

dpkg-architecture --query DEB_HOST_ARCH

Sure: armhf

then you are running a 32 bit OS. you will need to reinstall your OS and ensure its the 64 bit version. uname lies to you (sort of) but the package manager reveals what is actually installed. if its any consolation this is a fairly common issue and people don't realise they have actually been running 32-bit the whole time.

@MichaelMKKelly wow this is really interesting as I clearly thought I would have chosen the 64-Bit OS version back then. Do you know how this uname problem arises, as when reading through the internet I always stumbled upon the "uname" option?Never read about your command in some forums.

[MichaelMKKelly]

@n0r

@n0r

dpkg-architecture --query DEB_HOST_ARCH

Sure: armhf

then you are running a 32 bit OS. you will need to reinstall your OS and ensure its the 64 bit version. uname lies to you (sort of) but the package manager reveals what is actually installed. if its any consolation this is a fairly common issue and people don't realise they have actually been running 32-bit the whole time.

@MichaelMKKelly wow this is really interesting as I clearly thought I would have chosen the 64-Bit OS version back then. Do you know how this uname problem arises, as when reading through the internet I always stumbled upon the "uname" option?Never read about your command in some forums.

you are not the first and wont be the last. 32 bit was default for RPI OS for a lot longer than people realise

its just the way it reads the hardware and not the packages that are installed. in general across systems its not really an issue but. there's a bit of an edge case here.

At least you proactively dealt with the situation. there will be people that just ignore it because they think they are on 64 bit and the notification is a bug. then when stuff stops working in the future they will absolutely loose their shit.