Installing Home Assistant Supervised using Debian 12

Community Guides
161

What version are you on ? it seems ESPhome does not find your g++ compiler.

162

ESP Home: Current version: 1.15.3

arch aarch64
chassis
dev false
docker true
docker_version 19.03.13
hassio true
host_os Debian GNU/Linux 10 (buster)
installation_type Home Assistant Supervised
os_name Linux
os_version 5.4.72-v8+
python_version 3.8.6
supervisor 2020.11.0
timezone Europe/Amsterdam
version 0.117.6
virtualenv false
163

ESPHome dev compiles successfully

image
image661Ɨ553 34.3 KB

164

Removed ESPHome and installed the Beta version:


Compiling /data/test/.pioenvs/test/src/esphome/components/api/api_connection.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/components/api/api_pb2.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/components/api/api_pb2_service.cpp.o
sh: 1: xtensa-lx106-elf-g++: not found
Compiling /data/test/.pioenvs/test/src/esphome/components/api/api_server.cpp.o
*** [/data/test/.pioenvs/test/src/esphome/components/api/api_connection.cpp.o] Error 127
*** [/data/test/.pioenvs/test/src/esphome/components/api/api_pb2.cpp.o] Error 127
*** [/data/test/.pioenvs/test/src/esphome/components/api/api_pb2_service.cpp.o] Error 127
sh: 1: xtensa-lx106-elf-g++: not found
*** [/data/test/.pioenvs/test/src/esphome/components/api/api_server.cpp.o] Error 127
========================= [FAILED] Took 30.50 seconds =========================

Still same issue.

165 
dial tcp: lookup registry-1.docker.io on [::1]:53: read udp [::1]:43754->[::1]:53: read: connection refused

During the last step (curl) the system looses dns resolution and throws the above error.

166

Some changes were pushed through Github yesterday for the Supervisor. This issue has been addressed now.

167

Heh, well, Iā€™m new, referred from another thread. Iā€™m a real amateur at this. HOW amateur, you ask? Well, I WONā€™T tell you how long it took me to realize that the username of root isā€¦ ā€œrootā€. I sat, googled, got frustrated, and finally asked some friends. LOL Yes, THAT amateur!!

But I CAN follow directions. Debian is up to 10.6.0 now, and there was a bit of trouble with network drivers, but Iā€™m not new to COMPUTERS, just Linux/Debian stuff, so I figured it out.

So now Iā€™m up to the initial ā€œinstall HAā€ at 2.2 I typed in sudo -i and Iā€™m back at root. Then I typed in that first long line that starts with "apt-get install and I get Reading package listsā€¦ Done, building dependency tree, reading state informationā€¦ Done.

Then it says Package Network-Manager is not available but is referred etc etc
Package apparmor-utils is not available, but is referred etc etc
E: Unable to locate package software-properties-common
E: package ā€˜apparmor-utilsā€™ has no installation candidate
E: Unable to locate package jq
E: Package ā€˜network-managerā€™ has no installation candidate

I typed that long line twice to make sure it wasnā€™t me - same thing.

Any assistance is appreciated.

168

I assume you followed step 2.1 and updated the OS first and that was successful?

169

Yes, I had done it in step 1.18. Did I need to repeat it?

170

Was it successful? You mentioned network problems/drivers.

171

It looks like you didnā€™t install the dependencies before running the script?

OR maybe there is a problem with sources.listā€¦
can you show that to us?
(I had an issue with my proxmox install where it could not for some odd reason update as it couldnā€™t hit the debian mirror so I changed the mirror it was using and problem solved)

1 Like
172

It was. At least, it LOOKS like it was. It took a couple minutes. But now Iā€™m looking at the end of the lines of that update - it says 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

I got an IP address from step 1.19 though.

173

that was my next suggestion

174

Heh, remember that ā€œamateurā€ thing I mentioned? I donā€™t know how to get this to show. Or I mean, I donā€™t know what commands to type to get this.

175 
sudo nano /etc/apt/sources.list

It should look something like this.


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
deb http://deb.debian.org/debian/ buster-backports main contrib non-free
176

Seems it canā€™t find/install the dependencies so that is probably whyā€¦ Iā€™d expect to see timeout errors though or something in the console.

177

dep cdrom: [Official Debian GNU/Linux Live 10.0.6 standard 2020-9-26T10:36]/ buster main

is what it lists twice, then a couple websites. Then a bunch of lines starting with # that seem like descriptions.

178

show the whole file pleaseā€¦ what seems gibberish to you isnā€™tā€¦

179

So-Iā€™m sitting at the monitor for that PC, and using my tablet for this forum. Iā€™ll have to take a pic of the monitor (*ugh sorry) and post if thatā€™s ok.

180

Ideally, this is what you want your list to look like. I would suggest that because you didnā€™t have a network connection during the Debian installation process, the sources list didnā€™t get updated.

deb http://deb.debian.org/debian buster main
deb-src http://deb.debian.org/debian buster main

deb http://deb.debian.org/debian-security/ buster/updates main
deb-src http://deb.debian.org/debian-security/ buster/updates main

deb http://deb.debian.org/debian buster-updates main
deb-src http://deb.debian.org/debian buster-updates main

remove the existing config from that file, copy this in, Control+x to save, then run

sudo apt update && sudo apt upgrade -y
2 Likes