Created a VM on Proxmox to run Home Assistant Suprevised. Followed the installation here GitHub - home-assistant/supervised-installer: Installer for a generic Linux system and have a number of years Linux experience. The host has internet access, but HA throws a warning that the node does not have access. This is likely caused by the NM warning of being mis-configured.
Here’s some output:
root@debian-home1:~# nmcli d
DEVICE TYPE STATE CONNECTION
lo loopback connected (externally) lo
docker0 bridge unmanaged --
hassio bridge unmanaged --
eth0 ethernet unmanaged --
veth486986b ethernet unmanaged --
veth781900d ethernet unmanaged --
veth7b67e6a ethernet unmanaged --
veth8d888fa ethernet unmanaged --
vethb66a630 ethernet unmanaged --
vethc173334 ethernet unmanaged --
root@debian-home1:~# cat /etc/network/interfaces
source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
I read the interface needs to be managed, and I had them managed, but that was only after editing the config put in by home-assistant.deb package; which seemed wrong, and even when managed home assistant still warned that network manager was not configured correctly.
I’m close, but would appreciate any tips or advice. Thanks in advance!
Could someone do me a favour and post the output of a working system of the above commands? At least I could try and match that. Again, thanks in advance.
Thanks for the posts. Well, I have some real strange activity.
After running the installer instructions I have the output I printed above. I have to then manually active Supervisor eth0 with nmtui which changes the IP.
I am unable to connect to home assistant via a browser at any point, despite the python -m homeassistant process running.
Has anyone successfully installed HA Supervisor on Debian 12 recently? Just I’m stepping through each of the manual steps methodically, but after installing the home-assistant .deb networking is broken.
Could someone post their /etc/NetworkManager/NetworkManager.conf, /etc/NetworkManager/system-connections/default, and /etc/network/interfaces files. Thanks!
My mistake, I have /etc/NetworkManager/system-connections/Supervisor\ eth0.nmconnection not default. But still, it looks sane.
This is so strange then, because everything looks like it should, I just can’t connect to the HA instance that’s being hosted.
On boot I have this:
debian@home1:~$ nmcli d
DEVICE TYPE STATE CONNECTION
lo loopback connected (externally) lo
docker0 bridge unmanaged --
hassio bridge unmanaged --
eth0 ethernet unmanaged --
veth4bace57 ethernet unmanaged --
veth78ecc14 ethernet unmanaged --
veth988c9c7 ethernet unmanaged --
vethb77e99d ethernet unmanaged --
vethc68ce32 ethernet unmanaged --
vethea96991 ethernet unmanaged --
It is my understanding, and from the helpful posts here, that eth0 should be managed. I can achieve that by using nmtui and activating eth0. At which point the IP address changes, the device state updates to managed, but still the HA instance is not available.
debian@home1:~$ nmcli d
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected Supervisor eth0
lo loopback connected (externally) lo
docker0 bridge unmanaged --
hassio bridge unmanaged --
veth4bace57 ethernet unmanaged --
veth78ecc14 ethernet unmanaged --
veth988c9c7 ethernet unmanaged --
vethb77e99d ethernet unmanaged --
vethc68ce32 ethernet unmanaged --
vethea96991 ethernet unmanaged --
I checked all the container logs and there’s a log of no supervisor internet connection. I have HA running in a firewalled vLAN. Does the installer need internet access to operate locally?
I did test allowing all traffic from the host IP on eth0 but the supervisor still complained about not having internet access. I’m a bit lost at this point.
Okay. I found out at least part of the problem, it’s between the chair and computer … sitting comfortably, I was visiting :80 but HA is :8123.
Still complaining about network manager though:
Unsupported system - Network Manager issues
System is unsupported because Network Manager is missing, inactive or misconfigured. Use the link to learn more and how to fix this.
Found out the reason and workaround to my problem, it is because the interface is not NM managed. I can manually activate the connection and restart all the containers and then HA is happy, but the configuration does not persist over reboots.
I’m searching for the solution, and would be interested if any one else knows of one, or the reason why it doesn’t persistent in the first place!
Appreciate it, will definitely take a look. I am so close to having Supervisor sorted though, not that I need it for anything specific, but that I’ve put a bunch of time into automating cloud-init and home-assistant installation that it would seem like a waste to change now
I have a sneaking suspicion the issues I have are because the base Linux image is cloud-init based, and it’s doing something with the networking. Only guessing at the moment, no evidence to support the theory.
I got it working in a very inelegant way. Created a systemd service unit that runs nmcli dev set eth0 managed yes on boot after NetworkManager. It’s nasty, but the interface is now managed and connected.
The new systemd-resolved package will not be installed automatically on upgrades as it has been split into a separate package. If using the systemd-resolved system service, please install the new package manually after the upgrade, and note that until it has been installed, DNS resolution may no longer work as the service will not be present on the system.
Please also note:
Installing this package will automatically give systemd-resolved control over /etc/resolv.conf. If you don’t want this, follow this post to regain control over /etc/resolv.conf.
In case systemd-resolved is not installed on your system simply running
