-5
Why is Home Assistant an operating system and not an application installable through distro packages? (feddit.uk)
submitted 2 years ago by to c/homeassistant@lemmy.world
69 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 37 points 2 years ago* (2 children)

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
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 6 points 2 years ago (2 children)

    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
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 2 years ago

    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
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago

    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
  • fedilink
  • source
  • parent
  • [+] [S] -24 points 2 years ago* (last edited 2 years ago) (2 children)

    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
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 19 points 2 years ago (1 child)

    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
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 13 points 2 years ago* (last edited 2 years ago) (1 child)

    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
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] [S] -21 points 2 years ago (2 children)

    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
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 10 points 2 years ago* (last edited 2 years ago) (1 child)

    Yeah, I don't think I agree with you at all. Software development and operation are vastly different jobs. Packaging is yet a different story. Maintainers need different things than developers. Handling dependencies is a chore, and you need lots of them if your product speaks dozens of protocols and can interconnect with thousands of devices, each with their own quirks... All the people have something in mind. They already pay attention to deployment and support several methods. Sure it's not the method you have in mind. But the world doesn't specifically revolve around you. There are other factors at play. And sure. It'd be awesome if we solved software packaging, dependency hell, the supply chain of larger projects and everything. It's just not easy. And reality has quite some limitations. It's just... fighting reality doesn't get you anywhere. Sometimes we have to make ends meet with imperfect solutions. Or you just live without a smart home. Or use a different software stack. I mean there is FHEM and some other projects.

    And with that said, there is some merit to what you're saying. Software should be designed with usage in mind. It's just not easy and there are contradicting requirements. Either someone puts in all the effort to cater for your specific use-case... Or they don't.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] [S] -17 points 2 years ago* (1 child)

    They already pay attention to deployment and support several methods. Sure it's not the method you have in mind. But the world doesn't specifically revolve around you.

    It's not my method. Writing software with distributions in mind is the standard in free software development.

    It's just not easy.

    Indeed. That's why many engineers don't bother. Especially poor engineers.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •