I switched to the .deb package when they introduced it. They did change the pre-requisites removing avahi and adding resolved.service at some point. No biggie. You’re never going to break anything by running the install again.
Sorry I kind of missed this thread when it was posted or I would’ve said something sooner. The reason systemd-resolved is required is because all LLMNR and mDNS queries are delegated to it from containers managed by supervisor. There were a lot of issues around mdns names not working properly within HAOS such as this one and this one (there’s others if you want to search around in plugin-dns, supervisor, or esphome repos or just search around this forum). This was because the DNS plugin had some code that tried to handle mdns and frankly wasn’t very good at it. And LLMNR wasn’t handled at all.
Now we delegate all queries of those types to the host system itself. This has eliminated these issues as we use the native systemd-resolved service, as long as the host can resolve those names then anything managed by supervisor can as well. But because of this supervisor needs that service running otherwise anything managed by supervisor is completely unable to resolve mdns or llmnr names.
Unfortunately it looks like changing the supervised installer was missed as a part of that, sorry that created a hassle for you all. Hopefully this better explains why it occurred at least. I thought I had explained it in the unsupported help for that message but maybe it needs an update. If folks have a suggestion for how to make the unsupported systemd-resolved page more intuitive let me know or please feel free to submit a PR.
4 Likes
I appreciate your update @CentralCommand. Hearing the back story is always interesting and valuable. Missing stuff from time to time is normal and understandable - you and the HA team do a sensational job across a massive project with a huge user base. My HA installation is big and complex and it almost never breaks - it’s amazing.
My main beef is not that the docs aren’t good enough (we’d all love better docs, but let’s be reasonable). It is that there doesn’t seem to be any push comms (eg the blog / HA update notes) that are targeted to supervised installation users. For HA core, the quality of the release notes are just brilliant - deprecations, breaking changes, new features the whole shooting match - it’s fantastic.
It would be awesome if something similar could be done with supervised installation users in mind.
I’m not good at going back to the docs to find updates like the unsupported systemd-resolved note. Maybe that’s on me, but I’d love it if there was some kind of notification (like the main blog or the developers blog or something) that flagged changes to the requirements needed to stay “supported”, to the HA supervisor or to the supervised installer (which sometimes indirectly indicates things that need to change on already deployed supervised installs).
2 Likes
“You are never going to break anything by running the .deb install again…”
Quick question. I have several processes running on the host, and using HA Supervised on - Raspbian - not Debian. So my question is, would that change my OS to Debian and not ‘disturb’ my host processes (I have a bummer of a feeling you will just start laughing and say NO!!..)? (UGH)
No. . You can’t switch raspbian to debian like that.
Yeah I know it was a ridiculous question… ugh
1 Like