Start a Project
CirkitLab
All notes
ESP32

ESP32-C6 Thread Border Router and Zigbee Guide

2026-09-12

You added Wi-Fi to a coin-cell sensor and now it lasts a week. Or your Thread mesh works on the bench and dies in the metal enclosure. Both are classic C6 vs H2 mistakes.

ESP32-C6 combines Wi-Fi 6, BLE 5 and 802.15.4 on one RISC-V chip. ESP32-H2 is the 802.15.4 plus BLE part with no Wi-Fi. Both run Thread and Zigbee 3.0 through ESP-IDF v5.x and v6.0 and the esp-zigbee-sdk. C6 also works as a Thread border router with Wi-Fi uplink using OpenThread examples.

C6 is also the radio half of most ESP32-P4 camera designs, where it talks to the P4 over SDIO. Our ESP32-P4 guide covers that pairing from the video side.

TL;DR: C6 for mains-powered border router or Wi-Fi + Thread device. H2 for battery Thread/Zigbee end device. Routers never sleep. End devices poll. Keep 15 mm antenna clearance.

C6 vs H2: pick by power, not price

Item ESP32-C6 ESP32-H2
CPU 160 MHz RISC-V HP + 20 MHz LP 96 MHz RISC-V
Wi-Fi Wi-Fi 6 20 MHz, TWT, OFDMA None
BLE BT5 LE, 2M + Coded PHY BT5.3 LE + Mesh
802.15.4 Yes, 250 kbps, Thread + Zigbee Yes, 250 kbps, Thread + Zigbee
Memory 512 KB HP SRAM + 16 KB LP, 320 KB ROM 320 KB SRAM + 4 KB LP, 128 KB ROM
Flash In-package FH4/FH8 or external SiP 2/4 MB
GPIO 30x, ADC 7ch 19x, ADC 5ch
Use Border router, Wi-Fi+Thread gateway Battery end device, RCP radio

Do not put Wi-Fi on a coin cell. Wi-Fi TX is hundreds of mA; 802.15.4 is tens of mA with sleepy polling. C6 fits a mains-powered border router or a Wi-Fi plus Thread end device. H2 fits a battery Thread or Zigbee end device where Wi-Fi would waste power.

Product pages: ESP32-C6 and ESP32-H2. Datasheets: C6, H2. Note both share one antenna for BT + 15.4 — you cannot do both at full rate simultaneously.

Matter mapping: C6 alone = Matter Wi-Fi or Matter Thread endpoint. H2 + Wi-Fi SoC = Thread Border Router or Matter-Zigbee bridge. See ESP Matter for C6 and ESP Zigbee SDK.

Border router pattern that works

On C6 the full OpenThread stack and the app run on the same chip. The ot_br example gives IPv6 between Thread and Wi-Fi. Keep the router mains-powered. Routers never sleep.

Two valid architectures from ESP Thread BR docs:

  1. Single C6 native BR: examples/openthread/ot_br, esp_openthread_border_router_init() + backbone netif. Simplest BOM, good for home gateway.
  2. Host + RCP: Wi-Fi SoC (ESP32/S3) + H2 as radio coprocessor (ot_rcp) over UART/SPI. Better for high traffic — SPI preferred for latency, UART at 460800 if you must. Linux ot-br-posix works the same way.

Features you get: bidirectional IPv6, SRP/service discovery, multicast forwarding, NAT64, TREL, web GUI, RCP OTA.

End devices use sleepy polling:

otLinkSetPollPeriod(instance, 1000); /* poll parent every 1 s */

Longer poll means longer battery but slower downstream. Espressif demos this as ot_sleepy_device/light_sleep vs deep_sleep. Pattern: poll every 1-5 s for sensors, 100-300 ms only during commissioning. SSED (synchronized) saves more if parent supports it.

If you need ultra-low BLE instead of Thread, compare with our nRF54L15 BLE guide — same polling math, different stack.

Full OpenThread API is in ESP-IDF OpenThread guide.

Zigbee 3.0 notes

ESP Zigbee SDK supports Coordinator / Router / Sleepy End Device, Touchlink, Gateway + RCP + CLI. Use SDK v2.x for new designs (proprietary stack, actively developed), v1.x LTS is ZBOSS bugfix only. Recommended ESP-IDF is v5.5.x in current guides; C6 support started at v5.1.

Zigbee vs Thread decision:

  • Already have Hue / Aqara / Tuya ecosystem? Zigbee.
  • Want IP end-to-end + Matter? Thread.
  • Battery door sensor reporting twice a day? Either works — H2 sleepy end device, same layout rules.

Layout checks that fail most

Keep antenna clearance per Espressif guidelines, at least 15 mm from metal in all directions including enclosure. No clocks under the antenna. USB or switching rails crossing the 802.15.4 feed detune it. We check return loss on a VNA before blaming software.

From C6 layout guide and H2 layout guide:

  1. Module PCB antenna outside base-board edge, feed at edge. If recessed, cut out base board both sides + below.
  2. No copper / routing / components under antenna + 15 mm clearance.
  3. 50-ohm trace, outer layer, no vias, short, 135-degree bends, solid GND reference + stitching vias.
  4. CLC match network near pin (0201 zigzag) + extra CLC at PCB antenna. Budget a VNA tune pass.
  5. Keep crystal, DDR, high-clock, USB, UART far from antenna. Surround UART with GND copper/vias.
  6. Dense ground copper + vias on base board near antenna. Test throughput/range on final enclosure, not open bench.

Metal box? Use external IPEX antenna outside the box. On-board antenna inside metal is a -15 dB attenuator you cannot fix in firmware.

Bring-up checklist

  1. Power: 3.3 V clean, 500 mA peak for C6 Wi-Fi TX. Scope droop on TX burst.
  2. Flash: confirm FH4/FH8 vs external, correct flash_size in menuconfig.
  3. RF: VNA return loss <-10 dB in band, then RSSI walk-test.
  4. Thread: form network with ot_cli, attach 5 nodes, test parent loss + reattach.
  5. BR: ping IPv6 Thread -> Wi-Fi, test SRP discovery, NAT64 to IPv4 cloud.
  6. Power: PPK2 capture for H2 sleepy (target <30 uA average at 5 s poll).
  7. Cert: plan Thread 1.3 / Zigbee-compliant pre-test early if you logo.

FAQ

Can C6 do Wi-Fi and Thread at once? Yes as border router / endpoint, but one antenna shared. Heavy Wi-Fi iperf + Thread streaming will contend. For product, keep Thread polling modest when Wi-Fi is busy.

C6 or H2 + ESP32 for border router? Single C6 for cost and size. Host+RCP for performance or when you already have ESP32-S3 app code.

Can ESP32-C6 be a Zigbee router or repeater? Yes. A mains-powered C6 flashed with the ESP Zigbee SDK router example repeats Zigbee traffic like any 802.15.4 router. Zigbee routing is table-based, not self-healing mesh instantly — one rule of thumb: one powered router node per floor or every ~10 m indoors. H2 works identically; C6 pins you to nothing since both hold the same 802.15.4 radio.

ESP32-C6 vs S3 for the border router role? S3 has no 802.15.4 radio at all — an S3 border router always needs an H2/C6 as RCP radio. Pure C6 wins for cost and BOM. Pick S3 as host only for more RAM/USB or when the S3 already runs your app; pairing S3 + H2 over SPI with ot_rcp is the documented pattern.

Thread 1.3 or 1.4? Silicon datasheets state Thread 1.3. ESP Thread BR SDK is Thread 1.4 Certified Component as a solution. Do not claim silicon itself is 1.4 — cite the SDK cert.

Linux gateway instead of a C6 application SoC? If the gateway runs a UI or Modbus stack, use Embedded Linux on AMC SoCs — see our T113 / RK3566 / RK3588 bring-up checklist and add an H2/C6 as the 802.15.4 radio over UART/SPI.

Why does range drop indoors? Antenna detuned by enclosure, 0 dBm default TX, or router placed low behind metal. Fix layout + raise to +10 dBm class if allowed, add one more router node per 10 m.

References

  1. ESP32-C6 product — https://www.espressif.com/en/products/socs/esp32-c6
  2. ESP32-H2 product — https://www.espressif.com/en/products/socs/esp32-h2
  3. C6 datasheet — https://documentation.espressif.com/esp32-c6_datasheet_en.html
  4. H2 datasheet — https://documentation.espressif.com/esp32-h2_datasheet_en.html
  5. ESP Zigbee SDK — https://docs.espressif.com/projects/esp-zigbee-sdk/en/latest/esp32h2/introduction.html
  6. ESP Matter C6 — https://docs.espressif.com/projects/esp-matter/en/latest/esp32c6/introduction.html
  7. ESP Thread Border Router — https://docs.espressif.com/projects/esp-thread-br/en/latest/
  8. ESP-IDF OpenThread — https://docs.espressif.com/projects/esp-idf/en/stable/esp32c6/api-guides/openthread.html

Send us your floor plan and antenna choice. We reply with a layout review and a firmware estimate.

Building something similar?

Send your specs. We reply with scope and cost.

Start a Project