We have deprecated [...] Home Assistant’s Supervised installation method, which involves running your own operating system, then installing the Supervisor and other requirements on top of that.

Tell us you can't architect software like a first-year without using those words. Proper packaging has been out for 30 years.

My foray into self-hosted home automation was set to begin, but if they can't release software like adults then fuc--uh, good luck to them.

Home Assistant has so many moving parts, so I don't complain. I do wish containers would become first class citizens like the OS, because some stuff is just harder in containers. The only thing I can think of as to the "why" is because of how the OS project installs software, but that's an easily addressed problem so it must be something else.

Still, it's nice to know the container method is moving forward; I'm so done with installing specific OSes just to use some given piece of software.

Gotta admit, it was a bit difficult to get my head around all the different installation types when I was a new user, so simplification is probably well over due

I'm on supervised install on Ubuntu server. All worked fine for many years, except Supervisor being bitchy about me having Portainer installed for no reason. Last week or so, my machine started acting weird. After reboot I couldn't access it via local ip, only via external hostname. What keeps happening is after reboot Supervisor creates new network config for my ethernet, that causes this. It uses the network-manager to do this. I have netplan doing the config. Nyone else?

This seems reasonable to me?

If you're running it that way you still can, they're just not going to accept bug reports or have end user docs anymore. All the developer docs will still cover it.

It's an open source project and they need to focus their energy on known good configs.