670
The little smart home platform that could (www.theverge.com)
submitted 2 years ago by to c/technology@lemmy.world
115 comments fedilink hide all child comments
 
  • 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.
you are viewing a single comment's thread
view the rest of the comments
[–] 15 points 2 years ago (3 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 4 points 2 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years 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

  • permalink
  • fedilink
  • source
  • parent