It looks like you are running the RPI4 in 32-bit ARMv7 mode. If uname -m says aarch64 then it is 64 bit. If it says armv7l then it is 32 bit.
So as for your case this is correct: Use the arm7 package instead of the aarch64 package.
1 Like
And how many time Pi3 worked? As I already wrote I was able to run ha before @Tamsy help, but os freezes after 1-7days. I’m using ha since 3 years - started with core, next docker, and from 1-1,5 year as supervised, so I’m not interested in HA OS. I decided to not waste more time on debian and this instruction. I installed again raspbian and used official script
https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh
and from 4 days it’s working. I hope it will stay that way and recommend it everybody with similar problems with freezes on raspberry 3. I know that it makes my installation unsupported, but better running unsupported that not running supported.
Still running, no problems.
The script in this guide is identical, so that has made no difference. I merely forked the script way back when Supervised was announced to be deprecated.
Unless you have some specific need to run Supervised, you would be better off running HA OS on a Pi3 and having a supported installation.
1 Like
After I updated to the 1.2.1 agent my logs load very slowing under supervisor /system/ logs. Sometimes not at all. Tamsy told me in a private message he see this also. Are you?
I actually noticed this behaviour since OS Agent v.1.1.1 already. Loading the Log at Supervisor → System takes up to 45 sec. Nothing in the logs (daemon.log). It seemingly also does not affect any functionality.
pi@rpi3-20210823:~$ sudo lsusb
Bus 001 Device 004: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 005: ID 0451:16a8 Texas Instruments, Inc. CC2531 ZigBee
Bus 001 Device 006: ID 0424:7800 Microchip Technology, Inc. (formerly SMSC)
Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Is there any special reason why you have connected the Aeotec Z-Stick Gen5 and the TI CC2531 ZigBee-Stick to a USB2-hub which is connected to one of the USB ports of the RPI3?
Sudden freezes after some time with HA Supervised on Debian are discussed multiple times on this very thread and the culprit is often discovered as a power issue.
Are you aware that the Aeotec Z-Stick Gen5 pulls up to 5V from the USB port?
Is your USB2-hub externally powered? I would try to connect the two sticks through 2 extension cables to individual USB-ports on your RPI3 and monitor whether it still freezes after some time when run with Debian 11.
Please also note that not every externally powered USB-hub seems to be compatible with the RPI. Proper research should be done before. You might find some information about compatible USB-hubs, besides also from other sources, here.
No I am not seeing any slowdown or failure to load.
You did a fresh install with Debian 11 but not an upgrade from Buster to Bullseye, did you? 
No I have upgraded from stretch>Buster>bullseye. I have played with Proxmox VM’s with fresh bullseye but my main HA was upgraded from Buster.
Correct but you specifically asked if I was seeing a slowdown. My machine is an Intel NUC for my main HA.
1 Like
You are correct. I was just pointing out to @Tamsy that your setup is different than ours. Both of us are using a pi4.
@Tamsy
There is an existing GitHub issue on the logs slow to load. Looks like it has effected others longer.
Thank you for the information. Studying it now…
Thanks, I wrote ‘dtparam=sd_poll_once’ in /boot/firmware/config.txt, but nothing changes, I get the error messages every 10-12 second.
Hi All,
I have some trouble during the fresh Debian 11 on my Raspberry pi 4 4gb.
I success to copy an image on my SD Card (I didn’t test yet with an SSD). But when I start my Rpi4, I have a lot of lines which scroll but the screen goes black and nothing…
I have tested with 3 different SD Card and I can easily install the Raspberry Pi OS. I also tried :
- to download again the file xz image : same problem
- to restore the EEPROM backup and restart the Rpi4: same problem.
I think that I have a problem with a 32/64 bits version…
Thanks for your help.
Smilorel
Unless you have a specific need to use Supervised, use HA OS instead.
For someone like me that used a laptop, if you set a root_authorized_key in the sysconf.txt file, it will make the installation procedure full headless, with no HDMI cable, monitor, or keyboard needed.
Well, this thread is about installing Home Assistant Supervised on a Raspberry Pi with Debian 11.
I must have missed that there is a Raspberry Pi Laptop available now 
I meant I was using a laptop to flash the Debian image, and I did not have another monitor or keyboard. So I set a root_authorized_key in the sysconf.txt before plugin the microSD on the Raspi. That way you can go straight through ssh.