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.
    • @[email protected]English
      23•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

      • funkajunkEnglish
        11•7 months ago

        each plugin needs its own docker container.

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

        • @[email protected]English
          17•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.

          • @[email protected]English
            7•7 months ago

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

            • @[email protected]English
              1•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.

              • @[email protected]English
                3•7 months ago

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

          • @[email protected]English
            1•7 months ago

            I’d be interested to see that file if you’re still willing. IMO separating everything into their own containers is a positive.

            • @[email protected]English
              1•7 months ago

              This is how I have mine set up:

              homeassistant: image: ghcr.io/home-assistant/home-assistant:stable container_name: homeassistant volumes: - /data/homeassistant:/config - /etc/localtime:/etc/localtime:ro - /run/dbus:/run/dbus:ro ports: - “127.0.0.1:8123:8123/tcp” - “127.0.0.1:1400:1400/tcp” restart: “unless-stopped” privileged: true network_mode: host

              ha-whisper: image: docker.io/rhasspy/wyoming-whisper:latest container_name: “ha-whisper” volumes: - /data/homeassistant/addons/whisper:/data command: --model base --language en --beam-size 2 restart: “unless-stopped” networks: default: ipv4_address: 172.18.0.101

              ha-piper: image: docker.io/rhasspy/wyoming-piper:latest container_name: “ha-piper” volumes: - /data/homeassistant/addons/piper:/data command: --voice en_US-lessac-medium restart: “unless-stopped” networks: default: ipv4_address: 172.18.0.102

        • JustEnoughDucksEnglish
          5•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.

            • JustEnoughDucksEnglish
              1•7 months ago

              There are a few add-ons that are very handy that don’t have a docker equivalent. Namely the google cloud backup.

              I also agree that you generally don’t need add-ons and hopefully if someone is running HA on docker, they don’t need them, but for a few select ones, it is “needed”

      • @[email protected]English
        4•7 months ago

        Yeah. I ran it in docker for years and it was such a hassle compared to HAOS. The switch to VM was best decision I made regarding HA.