91
Home Assistant - Deprecating Core and Supervised installation methods, and 32-bit systems
(www.home-assistant.io)
this post was submitted on 23 May 2025
91 points (96.0% liked)
homeassistant
14645 readers
2 users here now
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
It's reasonable for an engineering standpoint. Bummer for people who don't want to run HASSIOS or install HA on an already provisioned system without having to fuck with docker.
Yeah, easiest way to turn me off a project is pushing black box installers. Don't trust software that tries hiding what its doing.
Well that's not really an issue since it's open and you can see what it's doing anyway.
What turns me off is software that insists on running with unreasonable privileges. Rootless podman containers are the way to go – you can decide the privileges of the user account running the container, and the container image is inspectable (and tweakable if you find something you don't like). And for the devs, maintaining (just) a container image is way less overhead than managing distribution-specific packages for 5 different package managers and dozens of distributions
Funny part is I'm responsible for some software which needs just a little privilege.
The direct install option runs as a broadly unprivileged user, thanks to systemd service for imparting one, surgical ambient capability to the process.
A team that wraps it in a container however demands it be run privileged, because they say the container runtimes dont support the same granularity, so the container users end up with unreasonable privileges while the direct install users are almost completely running unprivileged.