this post was submitted on 20 Apr 2024
669 points (99.1% liked)

Technology

58975 readers
3733 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
669
The little smart home platform that could (www.theverge.com)
submitted 6 months ago by [email protected] to c/[email protected]
116 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
[–] [email protected] 19 points 6 months ago* (last edited 6 months ago) (4 children)

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

[–] [email protected] 4 points 6 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.

[–] [email protected] 2 points 6 months ago (1 children)

That's not true at all.

[–] [email protected] 5 points 6 months ago (1 children)

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.

[–] [email protected] 1 points 6 months ago (1 children)

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

[–] [email protected] 1 points 6 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] -1 points 6 months ago (1 children)

each plugin needs its own docker container.

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

[–] [email protected] 15 points 6 months 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.

[–] [email protected] 1 points 6 months ago (1 children)

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] 1 points 6 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

[–] [email protected] 4 points 6 months ago (1 children)

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

[–] [email protected] 1 points 6 months ago* (last edited 6 months ago) (1 children)

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] 1 points 6 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] 7 points 6 months ago (1 children)

With plugins you mean add-ons like Z2M, Mosquitto or VSCode Server, right?

[–] [email protected] 3 points 6 months ago

Correct, yes, the word I meant is addon, not plugin.