• 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.ca
      link
      fedilink
      English
      arrow-up
      22
      arrow-down
      2
      ·
      edit-2
      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

      • rappo@lemmy.world
        link
        fedilink
        English
        arrow-up
        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.

      • funkajunk@lemm.ee
        link
        fedilink
        English
        arrow-up
        9
        arrow-down
        11
        ·
        7 months ago

        each plugin needs its own docker container.

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

        • OutOfMemory@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          17
          arrow-down
          1
          ·
          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.

          • jkrtn
            link
            fedilink
            English
            arrow-up
            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.

            • OutOfMemory@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              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