Does ESPHome need Home Assistant?
No. The Device Builder runs on its own in Docker, as a desktop app or from pip, and builds firmware without Home Assistant. Home Assistant discovers finished devices over mDNS, assuming your network allows it.
ESPHome builds firmware from a YAML file that describes the sensors and switches wired to a board. It supports ESP32 and ESP8266 boards, plus RP2040 and BK72xx. The Device Builder runs in Docker, as a Home Assistant app or as a desktop app. The first flash goes over USB; later updates and configuration changes can go over the air.
The key facts for ESPHome.
| Requirement | ESPHome |
|---|---|
| Price | Free |
| Licence | MIT / GPL-3.0 |
| Web UI | Yes |
| Docker Containers | 1 (app only) |
| Architecture | x86 + ARM |
| Tech stack | Python |
| Docker | Yes |
| Linux package | Yes |
| Windows | Yes |
| macOS | Yes |
| Home Assistant | Yes |
No. The Device Builder runs on its own in Docker, as a desktop app or from pip, and builds firmware without Home Assistant. Home Assistant discovers finished devices over mDNS, assuming your network allows it.
ESP32, ESP8266, RP2040 and BK72xx boards, among the families the project supports. Ready-made configuration templates for specific devices are on devices.esphome.io.
On Linux, yes. Pass the serial device through with --device=/dev/ttyUSB0. Docker on macOS cannot pass USB devices, so make the first flash from the dashboard's web installer or a desktop install. Run the container with --net=host so the dashboard can discover devices over mDNS; on Docker Desktop, where host networking is unavailable, publish port 6052 instead and give each device a fixed address.
Connect Philips Hue, IKEA, Xiaomi, and more than 5,000 Zigbee devices to Home Assistant without a proprietary hub.
Connect, automate and monitor smart home devices privately on your own hardware with this FOSS platform.
evcc reads your inverter, meter, home battery and charger, then sets the power going to the car so it runs on surplus solar, the cheapest tariff hours or a charging plan you wrote. The charging controller ships as a binary or a container with a web UI, an MQTT and REST API, and official iOS and Android apps.
Run Homey's smart home platform on your own server and manage it with the official mobile app.
Run Mosquitto as the MQTT broker for your home network, and the devices on it get one place to publish sensor readings, switch states and commands, with Home Assistant or a script listening on the other end. It speaks MQTT 5.0 and 3.1.1, adds TLS and per-topic access control once you configure them, and keeps retained messages, which survive a restart with persistence on. It is one lightweight daemon with one text config file, released under the EPL-2.0 or EDL-1.0 licence.
Cronicle runs the shell commands and scripts you would put in cron, and puts the schedule, live log and run history on a web page. Jobs can be retried or chained into sequences. You can cap a job on CPU and memory, and spread work over several machines with failover.