You can just install the new version over the top. I have done os-agent multiple times to make sure I was running latest and due to a new bunch of HA instigated incompatibilities I just reinstalled the requirements and ran the deb script file again just a few days ago.
Yes of course, but my point is that it is not just a one-off set-and-forget.
Chicken and egg :
I have HAS installed on Debian 12 but ends up with “Unhealthy system - Not privileged”.
I can not install “Advanced SSH & Web Terminal” because : “AddonManager.install’ blocked from execution, system is not healthy - privileged”
Any clue ?
rerun supervised installer could help
You can also set it to ignore the health check
For those who just want to upgrade from Debian 11 (bullseye) to Debian 12 (bookworm) check out my upgrade guide here. The guide is also valid for x86_64-devices.
3 Likes
Could I have some help please, I am trying to install HA suprvised on a intel based laptop following the official installation instructions on a clean whole disk install of Debian 12.
When I install the dependency “systemd-resolved” I lose internet access. I have tried setting my router to be the DNS server and /etc/resolvr.conf gets populated with nameserver: 8.8.4.4 nameserver: ( gateway address ) so Network Manager is working. But I still have no internet access. I have also tried editing resolvr.conf with 1.1.1.1.
When I disable systemd-resolved ( sudo systemctl disable systemd-resolved.service) internet starts working again and I can get to the stage where home assistant installation takes place but the script enables systemd-resolved and then stalls due to loss of internet.
I am able to open another terminal session and disable / stop systemd-resolved and the installation completes. When I reboot the laptop I have no internet with systemd-resolved active or disabled.
Has anyone done a clean install of Home Assistant Supervised on Debian 12, did you have these issues and how did you get internet working please?
Have you tried this?
1 Like
Thankyou for responding, I have tried this temporary fix but it did not work for me. resolv.conf is a symlink file that is updated by network-manager ( another dependency required by the home assistant installer ). Every time I boot the machine resolv.conf in overwritten.
Might be worth lodging an issue on Github then.
1 Like
man NetworkManager.conf
-
Using the CLI edit
/etc/NetworkManager/NetworkManager.conf -
Search for the [main] section in this file. It should look something like this:
[main]
dns=default
plugins=keyfile
autoconnect-retries-default=0
rc-manager=file
- Now change dns=default to dns=none just after the [main] tag like this:
[main]
dns=none
plugins=keyfile
autoconnect-retries-default=0
rc-manager=file
- Save the file and restart NetworkManager.service:
sudo systemctl restart NetworkManager.service
- Edit
resolv.confand add the DNS-server of your choice.
Next time you reboot your /etc/resolv.conf file will not get updated when using nm (network-manager).
Hope this helps.
6 Likes
Thank you, I will give it a bash ( pun intended ) tonight to see if permanently setting resolv.conf file to a set name server will solve the internet issue. I have done 3 or 4 installs, only my first time around did editing resolv.conf help the internet issue until I rebooted of course.
Also make sure you have disabled IPv6 withHA if your LAN is on IPv4 only:
HA → Settings → System → Network → Configure network interfaces: IPv6 → Disable
Thankyou for your suggestion regarding the IPV6. After I finally got home assistant installed ( solution below ) my internet die again just after home assistant loaded fully and before I was able to log into the GUI. I disabled IPV6 and stopped and started systemd-resolved and now everything is working, even after multiple reboots.
I have had heaps of trouble getting Home Assistant Supervised installed on an old laptop. The only solution that work for me was provided by @snakuzzo over at github ( Bug Report: Problems with systemd-resolved in 1.5.0 · Issue #304 · home-assistant/supervised-installer · GitHub ).
When I first saw his solution I had high hopes as it actually addresses the cause of the problem, systemd-resolved.
Here was his solution :-
"when you install systemd-resolved, it doesn’t work fine using stub listener (default option). If you disable stub listener, using another DNS server, it works fine.
So…to bypass the issue…
sudo apt install systemd-resolved
At this time, this breaks name resolution…
sudo nano /etc/systemd/resolved.conf
Uncomment this lines with no stub listener and your DNS server (eg. your router address):
DNS=192.168.1.1
DNSStubListener=no
Save and restart systemd-resolved
sudo systemctl restart systemd-resolved
Now check name resolution and go on with installation
11 Likes
This is the solution that worked for me!!
My Error
E: Unable to locate package systemd-resolved
Show us the output of:
sudo cat /etc/apt/sources.list
Well, this guide is for HA Supervised using Debian 12 (but not Ubuntu). Sorry, I cant help you with this one 
Please note THIS and THIS. You wont be able to install HA Supervised on any other OS than Debian 11 (obsolete soon) and Debian 12 (future proof).
1 Like
OK I’m reinstalling Debian 12
@Tamsy This is my Debian, I can’t update any packages right now
ngocdung@Linix:~$ sudo cat /etc/apt/sources.list
#deb cdrom:[Debian GNU/Linux 12.1.0 _Bookworm_ - Official amd64 NETINST with firmware 20230722-10:48]/ bookworm main non-free-firmware
deb http://deb.debian.org/debian/ bookworm main non-free-firmware
deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware
deb http://security.debian.org/debian-security bookworm-security main non-free-firmware
deb-src http://security.debian.org/debian-security bookworm-security main non-free-firmware
# bookworm-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.debian.org/debian/ bookworm-updates main non-free-firmware
deb-src http://deb.debian.org/debian/ bookworm-updates main non-free-firmware
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.