6 points

I installed it on Ubuntu server on my raspberry pi 4 and it took a couple months to fall over and become useless.

I’ve been running their OS since then and it has been absolutely rock solid. It’s been 5 or 6 years now, all I do is add more devices occasionally and update it when it occurs to me.

If you have a life and you don’t absolutely love tuning your OS for special purposes in ways that are already solved problems, the hass os image is the way to go.

permalink
report
reply
9 points
*

Before I understood Docker, I used to have HA installed directly on bare metal side by side with other “desktop” apps.

To be able to access devices, HA needs many different OS-level configurations (users, startup, binding serial ports, and much more I don’t have a clue about). It was a giant mess. The bare OS configuration was polluted with HA configurations. Worse, on updating HA, not only did these configurations change, the installation of HA changed enough that every update would break HA and even the bare OS would break in some ways because of configuration conflicts.

Could this be managed properly through long term migration? Yeah, probably, but this is probably a ton of work, for which a purpose-built solution already exists: Docker. Between that and the extra layer of security afforded by dedicating an OS to HA (bare metal or virtualized), discouraging the installation of HA in a non-dedicated environment was a no brainer.

permalink
report
reply
-5 points
*

this is probably a ton of work, for which a purpose-built solution already exists: Docker

LOL Docker isn’t a “solution” to the pressure of good engineering.

permalink
report
parent
reply

It’s true some things are harder to do in the container configuration; it’s easier installed as an OS, especially integrations like Z-Wave, ZigBee, RTSP, Eufy, ESP, and so on. All of these require running other software, and in containers it’s a fair bit of fussing with port and host OS device connections.

I’ve always run it in a container, without issue. It works fine, but I’m comfortable with the command line and LXC. That said, flashing an ESP hardware device and getting it connected to HA running in a container has so far defeated me, because I have to give access to the device in the configuration of the container before I run it, but the device flashing process itself is time limited and expects a process to be waiting on it when it is connected. It’s a chicken/egg problem I haven’t yet figured out which wouldn’t be a problem if I were running the HA OS.

HA isn’t the only software that just works better when it controls the while OS. Kodi is another that encourages users heavily to running it as an OS.

Regardless, it runs fine via

podman pull ghcr.io/home-assistant/home-assistant: latest

and there’s a package in AUR that wraps the container up with a systemd service - it’s as close to a bare package install as you’re likely to get.

What’s a little funny to me is that, despite that I’ve been running HA in a container for the past 4 years, I’m working towards getting a dedicated device and running HA OS on it. If we ever move out of this house, I’m not going to spend weeks going around replacing all of the hardware - smart sockets, lights, garage door opener, security, etc etc - with dumb devices; and for any of that to be worth anything, it’s going to need a controller configured for it, which means, I’m planning on selling the HA server device with the house. For that case, I don’t want anything but HA running on that device, and for that, it’d just be easier and smoother to run HAOS.

My advice is to run HA in a container until you are sure that’s the direction you want to go, but not for so long that it’s going to be a PITA to migrate to a dedicated server. But - hey, just IMHO - plan on running HAOS. If I knew then what I know now, that’s what I would have done.

permalink
report
reply
6 points

You should ask this to your favourite distro packagers, not to the home assistant developers.

In any case, it is such a mess of dependencies due to load of optional packages, very active development, that continuously break dependencies on the package repo.

What advantage would bring have a most of the time obsolete distro specific repo? On a maintainer POV this is the typical use case for distro agnostic deployment, maybe flatpak, maybe docker.

permalink
report
reply
-11 points
*

You should ask this to your favourite distro packagers, not to the home assistant developers.

I disagree. The Home Assistant developers are the ones who chose to create an OS. They could have chosen to create distro packages instead, or at least software which is amenable to being packaged by distros.

obsolete

What does that mean in the context of Home Assistant?

permalink
report
parent
reply
3 points
*

It seems to me they chose to provide a platform that vastly simplifies the installation of their software and maintenance of its code from a debugging standpoint. This seems perfectly reasonable. This appears to bother a particular community who feel entitled enough to demand multiple developers cater to their distribution’s needs. Shit needs to stop.

permalink
report
parent
reply
-3 points

This appears to bother a particular community who feel entitled enough to demand multiple developers cater to their distribution’s needs.

Your reading of the situation is wrong.

permalink
report
parent
reply
1 point

Since HA depends on a lot of python packages, on external softwares and libraries it could not feasible to ensure that the versions packaged with the distribution will always be in line with those needed by HA

permalink
report
parent
reply
-2 points

it could not feasible

I disagree.

permalink
report
parent
reply
4 points

It comes down to what are the developers willing or able to support.

For smaller teams they usually don’t want the responsibility of maintaining the package for distros, and HA developers have chosen to not support that option themselves. In their case I see it - what’s the benefit or incentive to them to maintain packages and the associated support costs or headaches. Containers mean they get a known state and don’t have to try to support unknown environments.

Some interested people can maintain the packages for their chosen distro - for instance I see one for Gentoo but it’s only up to 2024.6. It’s the first that came up in a search but there are likely more too supported by the community.

In my case, I also think that using HAOS on a dedicated box has led to a more stable experience as it’s not competing for resources on my other hosts, and attaching devices to it is much simpler. I think encouraging a solid base for people means a better experience overall when to be honest it’s hard to get started with it to begin with for many people.

permalink
report
parent
reply
37 points
*

It is both.

Home Assistant created an OS for appliance like installations.

But there is also the docker images, repo packages (I know Arch Linux has it in the repo) and pip based packages too.

permalink
report
reply
6 points

I installed it on my home Ubuntu server many years ago. Every now and then I get notification in HA, that my OS is unsupported. And if I want to update HA, add-ons or Supervisor, I can’t, because “Docker is misconfigured” - I have Portainer installed. In order.to update, I have to stop Portainer and restart HA Supervisor. HA itself works, but sometimes I don’t get it. Especially the Portainer bit.

permalink
report
parent
reply
3 points

For some reason, on Ubuntu, the Supervisor container loses its “privileged” status. I’m not sure if it periodically restarts itself or something , but that also was happening to me.

I moved my setup to Debian 12, did a fresh Supervised install, and then restored a full backup from my Ubuntu instance and I haven’t had this issue since.

permalink
report
parent
reply
4 points

Maybe you where on an older Ubuntu LTS. I don’t know which Ubuntu they consider “supported”.

I’ve been running my HA in Docker on Arch Linux for the last 4-5 years and I have never been notified that my OS is unsupported. Could be portainer related.

permalink
report
parent
reply
-23 points
*

docker images

Is not distro packages.

Arch Linux

It’s not in Debian. There’s no Red Hat packages either. Or OpenSUSE. It’s not even in OpenWrt which would make the most sense. So it looks like no useful, practical distro packages.

pip

Is not distro packages.

permalink
report
parent
reply
19 points

You didn’t mention in your OP that it had to be debian distro packages. I just gave examples of HA being packaged in other ways than a complete OS.

I could have said: “If you want to run HA from packages, you need to install Arch!” But I didn’t. Chill out.

permalink
report
parent
reply
-23 points

You didn’t mention in your OP that it had to be debian distro packages.

It doesn’t. WTF are you talking about?

permalink
report
parent
reply
13 points
*

A lot of software isn’t packaged for Debian. Especially complex ones and webapplications tend to be Docker containers or something like that. Home Assistant has a lot of Python dependencies which are a chore to maintain the Debian way. Same probably applies to some other distros. I mean it can be done, as Arch and NixOS show…

And you have Docker, you can install HA core in a Python virtual environment on any distro, or install Supervised, or the appliance (OS).

So there are many ways to install it. And I have the same complaint for other software. For example I’d like Nextcloud and a few other collaboration services to be available as distro packages. Sadly they aren’t available like that.

permalink
report
parent
reply
-21 points

A lot of software isn’t packaged for Debian.

Yes, often projects which are engineered without distros in mind. Which is to say, engineered poorly.

permalink
report
parent
reply

homeassistant

!homeassistant@lemmy.world

Create post

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

Community stats

  • 1.1K

    Monthly active users

  • 261

    Posts

  • 1.6K

    Comments

Community moderators