With a new ownership structure, Home Assistant is making its next big move
  • Home Assistant is now part of the Open Home Foundation, a non-profit aiming to fight against surveillance capitalism and offer privacy, choice, and sustainability.
  • The foundation will own and govern all Home Assistant entities, including the cloud, and has plans for new hardware and AI integration.
  • Home Assistant aims to become a mainstream smart home option with a focus on privacy and user control, while also expanding partnerships and certifications.
    • Lem453@lemmy.caEnglish
      0·
      7 months ago

      For others, beware that in a docker, each plugin needs its own docker container.

      I run everything in docker except for HA which I run in a VM (HaOS) which makes it super easy to use.

      Edit: by plugins I meant add-ons

      • funkajunk@lemm.eeEnglish
        0·
        7 months ago

        each plugin needs its own docker container.

        What are you talking about? This is simply not true.

        • OutOfMemory@sh.itjust.worksEnglish
          0·
          7 months ago

          No it’s true. I run ha in a docker container too, and it doesn’t support the plugin supervisor at all. You have to spin up your own plugin containers manually and configure the connection to them in the core ha instance, that’s what I did with piper/wyoming. I’d be happy to share a compose file if someone wants it.

          • Aux@lemmy.worldEnglish
            01·
            7 months ago

            You don’t need a supervisor with docker. And you don’t need separate containers for plugins.

            • turmacar@lemmy.worldEnglish
              0·
              7 months ago

              If you’re running HA in a docker, you need to run additional containers for add-ons. This is called out in the docs. Add-ons are only for HA OS or if you install it natively, with the supervisor (HA Supervised).

              If you are willing to dedicate a device to just HA you don’t need separate containers for the add-ons. For ease of use that makes a lot of sense, it’s, pretty plug and play.

              Personally the Pi I’m running it on can handle a lot more than just HA so a docker makes more sense, and just have the add-ons I’m using also defined in the docker compose file.

              • Aux@lemmy.worldEnglish
                01·
                7 months ago

                So, add-ons, not plugins. You don’t need add-ons if you are not using HA OS, they’re irrelevant.

        • JustEnoughDucks@feddit.nlEnglish
          0·
          7 months ago

          I think the wording is off.

          Many or most add-ons need their own docker containers, that is what the add-ons are.

          Every integration does not need its own docker container.

          • Aux@lemmy.worldEnglish
            01·
            7 months ago

            Well, the thing is, you don’t need add ons when running in Docker.