#Addons are claiming CPU/OS is not supported on one of the two almost same Rpi4 instances

1 messages Ā· Page 1 of 1 (latest)

livid mirage
#

I'm running two Home assistant instances, both on Raspberry Pi 4 Model B Rev 1.1 . I just noticed On one of them, I'm not able to install some addons (which are installed on the other one) due to the system/cpu incompatibility. The error sadly does not state anything else.

Both instances are running Home Assistant OS 15.2

Working one reports cpuinfo as:

āžœ  ~ cat /proc/cpuinfo 
processor       : 0
BogoMIPS        : 108.00
Features        : fp asimd evtstrm crc32 cpuid
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x0
CPU part        : 0xd08
CPU revision    : 3

...

Revision        : c03111
Serial          : 10000000507622dd
Model           : Raspberry Pi 4 Model B Rev 1.1

But the failing one as:

processor       : 0
model name      : ARMv7 Processor rev 3 (v7l)
BogoMIPS        : 270.00
Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xd08
CPU revision    : 3

...

Hardware        : BCM2711
Revision        : c03111
Serial          : 10000000682dc734
Model           : Raspberry Pi 4 Model B Rev 1.1
sweet vessel
#

Which add-ons are missing?

livid mirage
#

Frigate in this case, but in general list looks like this:

#

while is should:

cinder leaf
#

What does ha host info and uname -a for both say?

#

Also please don't shorten such outputs like the cat above.

livid mirage
#

Working:

agent_version: 1.7.2
apparmor_version: 3.1.2
boot_timestamp: 1747668153997185
broadcast_llmnr: true
broadcast_mdns: true
chassis: embedded
cpe: cpe:2.3:o:home-assistant:haos:15.2:*:production:*:*:*:rpi4-64:*
deployment: production
disk_free: 79.5
disk_life_time: null
disk_total: 116.5
disk_used: 32.3
dt_synchronized: true
dt_utc: "2025-05-20T16:48:01.325422+00:00"
features:
- reboot
- shutdown
- services
- network
- hostname
- timedate
- os_agent
- haos
- resolved
- journal
- disk
- mount
hostname: homeassistant
kernel: 6.6.74-haos-raspi
llmnr_hostname: homeassistant
operating_system: Home Assistant OS 15.2
startup_time: 1.053003
timezone: Etc/UTC
use_ntp: true
virtualization: ""

Linux a0d7b954-ssh 6.6.74-haos-raspi #1 SMP PREEMPT Mon Apr 14 16:32:39 UTC 2025 aarch64 Linux
Not working:

apparmor_version: 3.1.2
boot_timestamp: 1747762666517174
broadcast_llmnr: true
broadcast_mdns: true
chassis: embedded
cpe: cpe:2.3:o:home-assistant:haos:15.2:*:production:*:*:*:rpi4:*
deployment: production
disk_free: 48.3
disk_life_time: null
disk_total: 57.8
disk_used: 7.2
dt_synchronized: true
dt_utc: "2025-05-20T17:39:15.133751+00:00"
features:
- reboot
- shutdown
- services
- network
- hostname
- timedate
- os_agent
- haos
- resolved
- journal
- disk
- mount
hostname: homeassistant
kernel: 6.6.74-haos-raspi
llmnr_hostname: homeassistant
operating_system: Home Assistant OS 15.2
startup_time: 1.104388
timezone: Etc/UTC
use_ntp: true
virtualization: ""```
`Linux a0d7b954-ssh 6.6.74-haos-raspi #1 SMP PREEMPT Mon Apr 14 16:31:13 UTC 2025 armv7l Linux`
sweet vessel
#

The first is a 64 bit installation, the second one a 32 bit one.

#

Two different OS variants.

livid mirage
#

Shieeet, I wonder in which part of my life I screwed that. Any easy way to upgrade?

cinder leaf
#

AFAIK no. You need to re-flash and restore a backup.

livid mirage
#

thank you šŸ˜ž

#

Should't it be matter of replacing the boot partition only šŸ¤”

cinder leaf
#

What about all the binaries in the other partitions?

livid mirage
#

isnt it the bunch of python stuff? I will go with backup restoration anyway