Installing Home Assistant Supervised on a Raspberry Pi with Debian 11

Thank You @thanoskas and @Tamsy.

For what it’s worth if you still need it or others.

I was able to edit the boot.cfg file and change the 5.10 references to 5.9 filenames. You can connect your usb/ssd drive via another computer and edit that file easily

2 Likes

Few things that are missing : enable SSH, root SSH login allow, after install network manager is good to configure your WiFi using NMCLI. On precompiled image for Rpi3, there is issue with built-in voltage sensor Fe missing (thus Rpi power checker add-on doesn’t work) and with Esphome xtensa toolchain. I made my own tutorial for Rpi3, if anyone interested .

Please let us know if this bugs fixed and how do we change the hold command?

Whenever you want to change the package hold comand, just execute through CLI:

sudo apt-mark unhold package_name

got it…thanks

What I do is edit the source.list file and add # to the unstable branch line:

sudo nano /etc/apt/sources.list

# deb http://deb.debian.org/debian/ unstable main contrib non-free

How did that get in there in the first place?

As for the standart Debian 10 Buster installation for the pi4 sources.list contains by default:

deb http://deb.debian.org/debian buster main contrib non-free
deb http://deb.debian.org/debian-security buster/updates main contrib non-free
# Backports are _not_ enabled by default.
# Enable them by uncommenting the following line:
# deb http://deb.debian.org/debian buster-backports main contrib non-free

The official Debian image for raspberry 4:

https://raspi.debian.net/tested-images/

raspi 4 needs the latest kernel (5.5 or higher) and raspi-firmware newer than buster’s

P.d.: I think I remember that the default image had this activated, but I’m not sure about it.
maybe I added it to update something.

The latest image for Raspi4 comes with kernel 5.5.9 and works well with it. No problems with booting from SSD.

But kernel 5.5.10 which Debian tries to update to through sudo apt upgrade brings trouble because initramfs-tools needs to be v0.140 but the original image which comes with initramfs-tools v0.133 makes booting from ssd fail with the latest kernel 5.5.10.

Hello, does anyone still have problem with wifi that looks like wlan0 interface is missing or not working or is it just me? When I start wlan0 interface from command line it does not help. Supervisor just does not remember wifi configuration and behaves like wifi does not exist… Sometimes it detects wlan0, sometimes it does not…

Hi @kanga_who

First of all many thanks for your guide.
I have installed Debian on my Rpi3B+ and followed the steps.

sudo -i

Didn’t work for me. I got the

-bash: sudo: command not found

I instead set a password for the root account and used the su command

I have issues also with the last command

curl -sL "https://raw.githubusercontent.com/Kanga-Who/home-assistant/master/supervised-installer.sh" | bash -s -- -m raspberrypi3

I get

[info] 
[info] This script is taken from the official
[info] 
[info] Home Assistant Supervised script available at
[info] 
[info] https://github.com/home-assistant/supervised-installer
[info] 
[warn] The following is missing on the host and needs 
[warn] to be installed and configured before running this script again
[error] missing: apparmor

The package was already installed, and if I’m trying to install again I get:

apt-get install apparmor-utils
Reading package lists... Done
Building dependency tree       
Reading state information... Done
apparmor-utils is already the newest version (2.13.2-10).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Can you please help?
Thanks in advance

Did you forget to install sudo itself? Looks like you missed the step:

apt install sudo -y

You don’t want to do that, installing and running HA as the super user!
I suspect this is the culprit for the issues you described with the last command.

If you really strictly stick to @kanga_who’s installation guide and don’t leave out steps or change commands you should be good.

1 Like

Yep… You’re right.
I missed the sudo installation (that’s happen when you are following a guide late in the night :sweat_smile:).

I was able to complete the installation.
Let’s see whether it works.

Thanks for your prompt help

Edit:
I got the “Preparing Home Assistant” page :muscle:

thanks for sharing, works perfectly

While using this method to install Debian on a Rpi4.
Do you guys also see this message every 10 seconds in your dmesg command?

[email protected]:~$ dmesg -T

[Tue Apr 20 09:13:01 2021] mmc1: sdhci: ============================================
[Tue Apr 20 09:13:16 2021] mmc1: Timeout waiting for hardware cmd interrupt.
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Cmd:       0x0000371a | Max curr: 0x00080008
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: Host ctl2: 0x00000000
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[Tue Apr 20 09:13:16 2021] mmc1: sdhci: ============================================
[Tue Apr 20 09:13:27 2021] mmc1: Timeout waiting for hardware cmd interrupt.
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: Host ctl2: 0x00000000
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[Tue Apr 20 09:13:27 2021] mmc1: sdhci: ============================================
[Tue Apr 20 09:13:38 2021] mmc1: Timeout waiting for hardware cmd interrupt.
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Sys addr:  0x00000000 | Version:  0x00001002
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Blk size:  0x00000000 | Blk cnt:  0x00000000
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Argument:  0x00000000 | Trn mode: 0x00000000
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Present:   0x1fff0001 | Host ctl: 0x00000001
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Wake-up:   0x00000000 | Clock:    0x0000f447
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Int enab:  0x00ff1003 | Sig enab: 0x00ff1003
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Caps:      0x45ee6432 | Caps_1:   0x0000a525
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Cmd:       0x00000502 | Max curr: 0x00080008
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00000000
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Resp[2]:   0x00000000 | Resp[3]:  0x00000000
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: Host ctl2: 0x00000000
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x00000000
[Tue Apr 20 09:13:38 2021] mmc1: sdhci: ============================================

Yes. Same here rpi4.

For a Raspberry Pi 3B, this is a huge understatement. According to docker ps, took 10 minutes to start the landing page docker… I thought executing that last command would have meant everything was done and I could open the web interface… Nope. 30 minutes later, still waiting… I thought something was going wrong with my USB boot install, but I realized it was still churning when I opened top…

The guide is based on a 4gb Pi 4, as stated in the opening paragraph. YMMV with other models.

My experience using a USB SSD with a Pi3 B+ is about a 10-15 min download and install time.

What controller (brand/model) are you using? Looks to me that the controller is not supported.

Although a bit outdated regarding a compatibility list of supported controllers take a look here.