"ESP32" covers many chips, and only some have the IEEE 802.15.4 radio Zigbee needs.
| Chip | 802.15.4 (Zigbee/Thread) | Wi-Fi | Use for Zigbee |
|---|---|---|---|
| ESP32-H2 | yes | no | Zigbee end devices, routers, radio co-processor |
| ESP32-C6 | yes | yes | Zigbee devices; also Wi-Fi |
| ESP32 (classic), ESP32-S3, ESP32-C3 | no | yes | only as the Wi-Fi side of a gateway |
Roles
The ESP Zigbee SDK (on top of ESP-IDF) supports coordinator, router and (sleepy) end device roles.
- Sensor on battery → sleepy end device on an ESP32-H2 or ESP32-C6.
- Mains-powered actuator → router: it strengthens the mesh as well.
Zigbee ↔ Wi-Fi gateway
Espressif's gateway design combines a Wi-Fi SoC (ESP32, ESP32-S3, ESP32-C3, …) with an 802.15.4 SoC acting as radio co-processor (RCP). The SDK ships a gateway + RCP example. That's the route if you want your own coordinator that speaks Wi-Fi/MQTT instead of a USB adapter on a PC.
Practical notes
- Start from the SDK's examples for your role (end device, router, coordinator, gateway + RCP).
- The same 802.15.4 radio also serves Thread; decide which protocol your product uses, since the two networks are separate.
- Test your device against the stack your users run (Zigbee2MQTT, ZHA or vendor hubs). Standard clusters give you the best chance of working without custom converters or quirks.