Installing Home Assistant Supervised using Debian 12

Community Guides
1026

lsb-release was, but not apparmor. I just followed this guide, but installed the latest standard Debian 11 release.

1027

Hello,

I have just installed HA-Supervised on debian 11. Thanks to the instructions was simple and worked like charme. Thanks for this!
However, after install, all my docker containers were gone and only the home-assistant ones were left :frowning: I was able to track this down to the fact that the Home-Assistant installation comes with an own /etc/docker/daemon.json and one very relevant input in mine was missing:

"data-root": "/srv/dev-disk-by-id-ata-xx/docker-container",

Can I just manually add this, or would this be overwritten?

And a second question:
Since I installed, I cannot reach any services anymore that I had on this server from the internet:

  • Wireguard Server
  • Nginx Reverse-Proxy

What could be the reason?

Best regards,
Hendrik

1028

Iā€™ve followed this guide step by step and the services are running but I canā€™t log in to the web service. I use my machine IP and port 8123 (the same that was displayed after the successful installation).
Iā€™ve installed it on Debian 11. The device is Odyssey X86J4125800 with CPU Intel Celeron J4125.
Both agent and supervisor services are running. However, I canā€™t access the web service. I also noticed that the network on my device stopped working. I tried to grab a new os agent from GitHub but I canā€™t access the internet on the device. The device is connected via cable to the router. Any idea how can I restore the internet and access the web service?

1029

lsb-release was missing from https://raspi.debian.net/tested/20230102_raspi_4_bullseye.img.xz (install made yesterday)

1031

This was key to get a Supervised install in a Proxmox LXC container. Although it will be unsupported, I just wanted to have a look at this kind of install. So far so good!

I really like the OS virtualization of LXC containers vs HW virtualization of VMs.
Iā€™m trying both at this moment as Iā€™ve had the HAOS VM running for more than a year already under Unraid.

1032

How lame to block unsupported install just because some people arenā€™t following bug reporting rules. Not cool.

2 Likes
1033

This has been coming for a very long time, move on.

2 Likes
1035

You understand Iā€™m just a HA user who tries to help others by writing guides and had nothing to do with that decision, right?

This is an install guide, if you want to vent to Devs, start a new topic or head to Github.

2 Likes
1036

Iā€™ll be sure to do that. I confused you with the maintainer. My apologies kind sir. (Iā€™ve removed my sarcastic reply)

1037

install it at a j1900 pc. work very well! thank you!

1038

Great work!! Thanks a lot!
Can you update link for Debian image with firmware?
this is it

1039

Thank you for the nice guide! I used it to install Home Assistant Supervised on an old i386 HP laptop. I needed to make a few changes, and I documented them here: http://adrianpopagh.blogspot.com/2023/04/installing-home-assistant-supervised-on.html

So far, it runs great!

1040

Just a bit of warning:

Bookworm release planned on 2023-06-10

https://lists.debian.org/debian-devel-announce/2023/04/msg00007.html

According to ADR-0014, we still have 2 months after that to upgrade.

1041

Hi i just wanted to share that the homeassistant-supervised (1.4.2) is missing some smartness.
indeed even if iā€™m on debian 11, i have some custom networking rule
basically i did a bridge between ethernet and wlan as the computer is underground and as i have bad wlan there but some wlan devicesā€¦
therefore i use the computer as a hotspot :wink:

auto lo
iface lo inet loopback

auto enp8s0
allow-hotplug enp8s0
iface enp8s0 inet manual

auto wlp7s0
allow-hotplug wlp7s0
iface wlp7s0 inet manual

auto br0
iface br0 inet static
  bridge_ports enp8s0 wlp7s0
  address 192.168.1.101
  broadcast 192.168.1.255
  netmask 255.255.255.0
  gateway 192.168.1.1
  bridge_stp off
  bridge_waitport 0
  bridge_fd 0

and when the deb file is triggered it messes up the /etc/network/interfaces file with something that of course breaks my networkā€¦

then the install script is blocked in such way :

[info] Fix kernel dmesg restriction
Ajout de Ā« dĆ©tournement de /etc/NetworkManager/NetworkManager.conf en /etc/NetworkManager/NetworkManager.conf.real par homeassistant-supervised Ā»
Ajout de Ā« dĆ©tournement de /etc/NetworkManager/system-connections/default en /etc/NetworkManager/system-connections/default.real par homeassistant-supervised Ā»
Ajout de Ā« dĆ©tournement de /etc/docker/daemon.json en /etc/docker/daemon.json.real par homeassistant-supervised Ā»
Ajout de Ā« dĆ©tournement de /etc/network/interfaces en /etc/network/interfaces.real par homeassistant-supervised Ā»
DĆ©paquetage de homeassistant-supervised (1.4.2) ...
ParamƩtrage de homeassistant-supervised (1.4.2) ...
[info] Restarting NetworkManager
[info] Enable systemd-resolved
[info] Set up systemd-journal-gatewayd socket file
[info] Enable systemd-journal-gatewayd
[info] Restarting docker service
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu
[info] Waiting for checkonline.home-assistant.io - network interface might be down...
ping: checkonline.home-assistant.io: Nom ou service inconnu

not a big deal if you are physically on the computer, so you can fix the interfaces file and restart networking

but if the computer is without screen/input and if you did all this per ssh ā€¦ then good luck ;p

if someone could fix that point this would be awesome :wink:

1042

The Supervisor controls the networking, so every time you update you will have the same issue.

Itā€™s not a functionality loss, itā€™s the way a Supervised install works.

1043

Youā€™re perhaps missing the ā€œdonā€™t f*** with your debian installationā€ part of the instructions.

I know it is a PITA, but thems the rulez.

1 Like
1044

When I try to install home-assistant on Debian 11,

why is it forcing ipv6?

1045

What do you mean by ā€œforcedā€?
Your debian 11, that you chose to manage yourself, has ipv6 enabled, apparently.

Those are the kind of issues your are supposed to be able to handle if you follow the supervised route.

1 Like
1046

ok but in that case could the supervisor enable the user to have a bridge ?
I mean i have home assistant on a computer designed to be a NAS and my nas is also doing network bridge as the devices underground donā€™t see the WiFi .

I donā€™t mind if another tool handles the network but i guess that this should be possible right ?

1047

The Supervisor controls networking, end of story. If you need or want something different, Supervised install is not for you. Iā€™d suggest you look into running a HA OS VM instead, that way you can do whatever you want with the rest of the machine.

2 Likes