zlacker

[parent] [thread] 4 comments
1. akerl_+(OP)[view] [source] 2023-09-26 23:44:57
Yea; I run HomeAssistant via the official Docker container and have been pretty happy with it. It's only accessible on my local network, and my phone/laptop/etc use Wireguard to talk to it if I'm somewhere else.
replies(3): >>fortys+u >>XorNot+5a >>nunez+ch
2. fortys+u[view] [source] 2023-09-26 23:49:08
>>akerl_+(OP)
Just installed that, myself. Same way. Instantly worked. Kicking myself for not installing this sooner, it's pretty rad.
replies(1): >>nuclea+U6
◧◩
3. nuclea+U6[view] [source] [discussion] 2023-09-27 00:23:48
>>fortys+u
Once you’re kind of settled there take a look at NodeRED. Integrates really cleanly with Home Assistant and for most of the kinds of people on HN that are already technically inclined, it makes much more complex automations and integrations a piece of cake.
4. XorNot+5a[view] [source] 2023-09-27 00:43:55
>>akerl_+(OP)
Yep this is how I'm doing it. Combined with ESPHome I've got a nice, local-only automation system using sourceable off-the-shelf parts (but I'm so, so happy that Athom are making open-source flashed IoT devices - which go and live on my IoT network).
5. nunez+ch[view] [source] 2023-09-27 01:30:34
>>akerl_+(OP)
Note that you don't need the Community Store if you're running HA via Docker.

Every plugin that is in that store must have a custom_components folder.

Drop that into the bind-mounted volume holding HA's configuration.yaml and restart. HA will pick it up automatically, and you'll be able to install it in Integrations and Devices.

[go to top]