[davemp]

There’s like 10 replies telling me it’s not actually that complex then describe an equally or more complex solution that’s probably missing some of the security or features I have. I guess I wrote “complicated to set up” when I meant “complicated stack”.

A heavyweight blob of python running in a container talking to other containers running node-js on a Linux VM on a Linux host behind layers of networking to toggle 1 bit of information over a UHF link is really complex even if it only took 1 button click. My solution just removes the linux VM.

I’m not even saying I struggled, it took me like 1-4hrs depending on if you include the non HA stuff. I can clone the repo I made, populate the secrets/gateway, and type ‘make’ to rebuild my setup on a new machine. Everything is “zero-trust” with signed SSL certs, dynamic DNS+wireguard to tunnel in from a stable url, and room for more services. It’s cool, but it’s only toggled 1 light for years.

[Spivak]

Well sure, with those requirements running any piece of software will be complicated. None of the complexity has anything really to do with HA.

My pretty minimal stack:

- Intel NUC running Ubuntu LTS.

- Zigbee dongle I bought off Aliexpress.

- Zigbee2MQTT installed via package manager configured to use the Dongle.

- One single container running HomeAssistant with net=host

That's it. Has worked for years. Whenever I feel like it I ssh into the box, docker pull the latest image, rerun my two line bash script to recreate the container and go on my merry way.