honestly, it gives me more control on HA side and furthermore and the most important thing is to be able to install auto Google backup which only can run on HAOS or HA Supervised. Else I will go with the docker method and install everything else on a separate LXC.
How? Iād be really interested to know
I would be very interested in this too and am willing to rethink my HA installation strategy to get that claimed even more control over HA
WARNING this line bricks debian 12 installs ability to connect to net.
sudo apt install apparmor jq wget curl udisks2 libglib2.0-bin network-manager dbus lsb-release systemd-journal-remote systemd-resolved -y
everything after results in Temporary failure resolving 'deb.debian.org'
cant even ping a domain like github.com
Ended up reformating and reinstalling debian 12 to resolve the issue, then followed these instructions again to brick the system again.
Itās not an issue with those instructions - they are required for a Supervised installation.
I believe the issue is with the systemd-resolved
package and a fix is posted above, outside of the control of HA.
can you point me towards this fix? there are 1085 replies and the thread loads via ajax infinite scroll so its a bit hard to search for anything relevant.
Thank you. Much apreciated
Because you can
Just because you can doesnāt mean you should
Edit your /etc/systemd/resolved.conf
configuration.
DNS=ip.ip.ip.ip
After this, restart resolved with systemctl restart systemd-resolved.service
[error] Armbian 23.08.0-trunk bookworm is not supported!
Wondering though why you are still insiting on installing HA Supervised on an unsupported OS.
There are only two supported operating systems to run the Supervisor on:
Home Assistant OS
Debian 12 (Bookworm)
These operating systems are actively tested and maintained, for use with the Supervisor.
Simply asking your favorite search engine would have told you the very sameā¦
Armbian 23.08.0-trunk bookworm is built on top of Debian 12. Iām looking for a solution
So, which of the two words āno derivativesā do you donāt understand?
Docker CE >= 20.10.17
Systemd >= 239
NetworkManager >= 1.14.6
udisks2 >= 2.8
AppArmor == 2.13.x (built into the kernel)
Debian Linux Debian 12 aka Bookworm (no derivatives)
Home Assistant OS-Agent (Only the latest release is supported)
To be honest, I donāt really get the whole point of not allowing an SSH server as default, especially if the host should be supervised. Is it just to conflict interests?
- Without SSH server - Supervised, supported, but needs a monitor and keyboard, so cannot be headless.
- With SSH server - Supervised, unsupported, no need for monitor and keyboard, so can be headless.
Even the Home Assistant OS provides a way to access the host system through SSH by utilising dropbear. Why dropbear canāt be used with a Supervised install as well and stay supported?
Can someone explain this? What is the point of that?
Hereās why I think they did that (just my opinion of course).
A few years ago the development team announced that, due to a shortage of resources, they would stop offering Home Assistant Supervised. In other words, it would cease to exist as an official installation method.
The community was displeased with the decision and, after much discussion, the compromise was to support Home Assistant Supervised on Debian only and with strict limitations on what else could run on the host machine, namely nothing else because the machine should be dedicated to running Home Assistant software.
The reason is that other software may interfere with Home Assistantās operation and the development team doesnāt have the bandwidth to study the affects of all possible external influences. If the community had refused these terms, there would be no official Home Assistant Supervised installation method.
FWIW, I run SSH and Samba servers on my host machine. I know that, technically speaking, this violates the guidelines. However, based on experience, these services have no, or negligible, impact on Home Assistantās operation. Theyāre available as Add-ons but I prefer having them separate from Home Assistantās ecosystem. Given that theyāre available as Add-ons, Iām comfortable with the fact I havenāt installed anything that is significantly different from what Home Assistant already supports.
My problem is supervising a Supervised installation without connecting a monitor and keyboard. And for the sake of requirements keep it supported.
So the options which I see are, go on another level of virtualisation (like Proxmox) to be able to supervise the Supervised installation, or get a hardware which has a built in IPMI or similar solution. But generally why to overengineer it. (I donāt have the hardware and try to keep it simpleā¦)
Supervised runs just fine headless, nothing, you canāt maintain thru SSH.