- cross-posted to:
- gadgets
- technology
- tech
- cross-posted to:
- gadgets
- technology
- tech
- 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.
What are you talking about? This is simply not true.
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.
With plugins you mean add-ons like Z2M, Mosquitto or VSCode Server, right?
Correct, yes, the word I meant is addon, not plugin.
You don’t need a supervisor with docker. And you don’t need separate containers for plugins.
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.
So, add-ons, not plugins. You don’t need add-ons if you are not using HA OS, they’re irrelevant.
I’d be interested to see that file if you’re still willing. IMO separating everything into their own containers is a positive.
This is how I have mine set up: