ESPHome now speaks Zigbee. The popular firmware for hobbyist microcontrollers has gained a native Zigbee component that, for the first time, lets you build your own Zigbee end devices and pair them directly with Home Assistant via Zigbee2MQTT or ZHA. The project deliberately calls it “initial support”: the feature is here, but still early and experimental.
What is new
Until now, ESPHome almost always connected homemade sensors to Home Assistant over Wi-Fi or Bluetooth (BLE). Zigbee changes the game: the radio network runs as a mesh in which devices relay each other’s signals, and it is far more frugal on power – ideal for battery-powered sensors meant to last for years unplugged. Nordic’s nRF52 platform came first (ESPHome 2026.1.0); support for ESP32 followed shortly after in mainline (2026.5.0) and has been refined ever since.
What you need
Important: not every ESP32 qualifies. Zigbee requires an 802.15.4 radio, meaning models such as ESP32-C6 or ESP32-H2; the classic Wi-Fi ESP32 is left out. The nRF52 allows a maximum of eight endpoints, the ESP32 considerably more. If you run the devices through Zigbee2MQTT, you need at least version 2.8.0; alternatively, ZHA works too. Fittingly, the August 2026.8.0 release added automatic rejoin after network failures and further Zigbee polish.
Why it matters
For the DIY smart-home scene this is a bigger step than it sounds. Zigbee end devices used to come from vendors or from complex one-off projects. With ESPHome, the familiar YAML workflow now reaches the Zigbee ecosystem as well – no Wi-Fi baggage, but mesh and long battery life. Plenty is still a work in progress, yet the direction is clear. We collect background on Zigbee, ZHA and Zigbee2MQTT in our smart-home section.
Sources: the ESPHome Zigbee component documentation, Zigbee2MQTT discussion #29916 (Koenkk), the Espressif esp-zigbee-sdk discussion #809, and the ESPHome 2026.8.0 blog post.
