If I am not mistaken the tradeoff is losing add-ons but being able to install other services.

So… what is your experience? Are add-ons useful/common for your use case?

  • sylverstream@lemmy.nz
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    I’m running the docker version as I’m also using the rpi for other things, like imageview and pi hole. I don’t really miss addons, the only annoying thing is that most documentation assumes you’re running ha os.

    But if you don’t plan to use it for anything else than HA, I’d go for HA OS.

  • DrM@feddit.de
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    You can go supervised! You still have most of the operating system available to your needs and you can still use add-ons. I use it for years and it works like a charm

  • EnglishMobster@kbin.social
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    1 year ago

    HA OS is the way to go.

    You don’t want to have to think about it. HA OS just works. You set it up and let it run.

    There’s no sense in trying to kerfuffle other things into it. You don’t want to do too much on the Pi anyway because it’ll lower the responsiveness of Home Assistant slightly. If you want a server that does things, buy a separate NAS and run it alongside HA OS.

    • dipbeneaththelasers@kbin.social
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      This is what I do with a Pi running HAOS and a Synology ds920+ running backups and everything else. It’s been rock solid, gives me a decent backup solution, my home automation is stable and responsive and no-fuss, and plenty of options for tinkering. Highly recommend.

  • zach@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I recommend HA OS. What happened to me is that I used docker, got everything set up how I liked it, then had to move over to HA OS when I needed a specific add on and didn’t have any other solution.

    If you don’t already have a plan for other services, might not make sense to use docker, too.

  • Number1@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I run my own a VM.

    I was sceptical about running in a OS that I can’t run my normal updates and automations on but HA OS has been rock solid and easy. Plus you get a few more features

    • g5pw
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      I second that, I just put it in a VM on my proxmox host. zero issues so far.

  • Jeena@jemmy.jeena.net
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    I used a ton of AddOns, really practical because they also embed themselves easily into the rest of Home Assistant. I would go for the HA OS. But I also do wish there was a AddOn to install random docker images.

  • PupBiru@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    home assistant in docker is definitely not for the feint of heart! the networking requirements are actually quite intense, and really don’t map well to virtual networks like dockers uses

    … among other issues

    HAOS on a pi; i’ve tried the docker thing time and time again, and the next chance i get in blowing it all away and starting on real hardware again

  • wagesj45@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I’ve run both, and the OS version is much more stable and easier to keep running. Whether you use an rpi or a VM, use the dedicated OS and save yourself the heartache of trying to get your hardware working with docker.

  • Bp#9@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Its not super hard to manually set up with docker or podman but you have to deal with integrating and updating the add-ons yourself. I ran out of CPU on a pi4 (due to a buggy websocket client in the end) and moved to a small form factor x86_64 server under Rocky. I ran manually using just containers (podman in this case) and it worked fine but integrating and updating the equivalent of add-ons was a lot of manual plumbing work that I don’t find much fun anymore.

    I switched back to hassos, but under KVM. This for me is the best of both worlds: I get the fully managed/integrated work of Frenck and friends for HA and can still access and manage the machine normally (and use it for other services).

    There’s nothing remotely realtime about the python code in the core HA, it works well in a reasonbly provisioned VM (4 cores, 8G ram) backed by a good SSD. There is some religion in the community about not using VM’s: it is a layer of complexity and I understand why folks on discord don’t want to help people with it, but technically it works well for this class of app.

  • cerebrate@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    @unknowing8343

    I used the fanciest possible setup with HA running in a Kubernetes cluster and its helper services likewise, but that’s severe overkill for most people unless they’ve got compute to burn and need/want/enjoy customizing the heck out of everything.

    A Pi, even a Pi 4, isn’t compute to burn but also isn’t expensive enough to need other services on it to justify it. For what it’s worth, I’d suggest HA OS and dedicating the Pi to it.

  • kamin@lemmy.kghorvath.com
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I run the docker because it’s really easy to migrate to another machine if I needed. I just rsync the data and re-run the yaml on the new machine and I’m back up within seconds.

  • nosut@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Home assistant OS is also my recommendation. Add-ons are pretty important IMO. Plus for something I am planning to try and have 100% uptime and controlling my home smart devices I don’t want it containerized and at the mercy of docker.

    Currently using 15 add-ons myself.

  • Panron@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I started out running HA in a docker container on a NUC (everything configured in a docker compose file). Documentation around everything was pretty poor at the time (I’m not sure if this has improved since then), so I ended up feeling too confused on where to even begin expanding from vanilla HA.

    I ended up picking up a RPi 4 (and SSD and enclosure) and have been happily running HA OS since then on the Pi. If that ever fails on me, I may go back to a docker instance.

    I’d recommend you try whichever is the most convenient first (probably the docker approach, unless you already have the Pi on hand). Give it a month or two, try to setup up a few things you’re interested in, and then decide if you’re satisfied with that setup or want to try the other option.