What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Short answer: Choose the ESP32-C6 when the Matter product needs an integrated 2.4 GHz Wi-Fi connection as well as Thread-capable 802.15.4. Choose the ESP32-H2 for a Bluetooth Low Energy and 802.15.4 device that does not need Wi-Fi on the chip. Both can be used for Matter-over-Thread, but neither chip should be assumed to be a complete Thread Border Router by itself.
A Border Router is a system that connects Thread to a Wi-Fi or Ethernet backbone. In Espressif’s documented design, an ESP32-H2 supplies the 802.15.4 radio while a separate Wi-Fi host handles the backbone. That architectural distinction matters more than the chip names when you select hardware.
ESP32-C6 and ESP32-H2 at a glance
The two chips overlap on Bluetooth LE and IEEE 802.15.4, the radio used by Thread and Zigbee. Their decisive difference is Wi-Fi integration.
| Capability | ESP32-C6 | ESP32-H2 | What it means for Matter |
|---|---|---|---|
| Wi-Fi | Integrated 2.4 GHz Wi-Fi 6 | Wi-Fi is not listed in Espressif’s integrated feature overview | The C6 can be the networked controller for a Matter-over-Wi-Fi product. An H2 design needs another network interface or host if Wi-Fi is required. C6 product overview; H2 product overview |
| Thread/Zigbee radio | IEEE 802.15.4 | IEEE 802.15.4 | Both families are suitable platforms for Matter Thread devices when the firmware and board design support that role. Espressif Matter Programming Guide, release v1.4.2 |
| Bluetooth | Bluetooth 5 LE | Bluetooth 5 LE | Bluetooth LE is part of the documented radio set on both chips and can be used by supported Matter commissioning flows. |
| Typical product role | Wi-Fi Matter device, Thread Matter device, or one component in a larger gateway | Thread Matter device or 802.15.4 radio co-processor paired with a networked host | The finished role is determined by the selected transport, firmware, antenna design and complete system architecture. |
| Border-router implication | Has both Wi-Fi and 802.15.4 in one device, but the reference design and concurrent-radio behavior still need validation | Commonly used as the 802.15.4 radio side of a two-chip design | A radio list does not prove that a production-ready Border Router is implemented. |
Espressif’s feature pages are the right place to verify the silicon capabilities for the exact revision you are designing with. Board modules can add memory, antennas and interfaces, but they cannot add an integrated Wi-Fi radio to an H2.
#1 Best Overall
- Enhanced Connectivity: Combines 2.4GHz Wi-Fi 6 (802.11ax), Bluetooth 5(LE), and IEEE 802.15.4 radio connectivity, allowing you to apply the Thread and Zigbee protocols.
- Matter Native: Supports building Matter-compliant smart home projects thanks to its enhanced connectivity, achieving interoperability
- Security Encrypted on Chip: Powered by ESP32-C6, it brings enhanced encrypted-on-chip security to your smart home projects via secure boot, encryption, and Trusted Execution Environment (TEE)
- Outstanding RF performance: Has an on-board antenna with up to 80m BLE/Wi-Fi range, while reserving an interface for external UFL antenna
- Leveraging Power Consumption: Comes with 4 working modes, with the lowest being 15 μA in deep sleep mode, while also supporting lithium battery charge management.
What Matter means by Wi-Fi and Thread
Matter is an application layer. It can run over more than one local network transport, so “Matter support” does not identify the radio a product uses. A Matter-over-Wi-Fi device joins the home’s Wi-Fi network directly. A Matter-over-Thread device joins a low-power Thread mesh and reaches the home network through a Thread Border Router.
Matter over Wi-Fi
A Wi-Fi Matter product needs a Wi-Fi-capable SoC or a separate Wi-Fi host, plus firmware that implements the Matter Wi-Fi transport and the device’s application. The ESP32-C6 contains the relevant 2.4 GHz Wi-Fi radio, so it can provide that network link without an additional Wi-Fi chip. The C6 still needs an appropriate antenna, power supply, board layout and software configuration; the presence of the radio alone does not complete a product.
Matter over Thread
Thread uses IEEE 802.15.4 rather than Wi-Fi. Espressif’s Matter guide explicitly lists ESP32-H-series devices and ESP32-C6 among the 802.15.4 platforms that can build Matter Thread devices. The same C6 therefore has two possible Matter network paths: Wi-Fi or Thread. The H2 has the 802.15.4 path and Bluetooth LE, but no integrated Wi-Fi path in the documented feature set.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Why Bluetooth LE appears in both designs
Bluetooth LE is a separate radio capability from the Matter network transport. It can be involved in commissioning when the framework and product flow support it; after commissioning, the device’s operational traffic uses the selected Wi-Fi or Thread network. Do not treat “has Bluetooth” as evidence that a chip can reach the home IP network without Wi-Fi, Ethernet or a Border Router.
Where the ESP32-C6 fits
The ESP32-C6 is the more flexible single-chip choice when a product may need both conventional Wi-Fi connectivity and 802.15.4. Its documented feature set combines 2.4 GHz Wi-Fi 6, Bluetooth LE and 802.15.4. That combination can reduce the number of chips in a Matter endpoint and lets one hardware family cover a Wi-Fi version and a Thread version of a product.
Use C6 for a Matter-over-Wi-Fi endpoint
For a mains-powered sensor, controller or appliance that is intended to join the customer’s Wi-Fi network directly, the C6 supplies the required integrated radio. You still select a Matter Wi-Fi firmware target, configure credentials and commissioning, and validate the antenna and regulatory design on the chosen module or board. A C6 development board is useful for proving the software path, but its RF layout and power behavior are not automatically representative of a finished enclosure.
Use C6 for a Matter-over-Thread endpoint
The 802.15.4 radio makes the C6 eligible for Thread designs too. In this role, the product does not use the C6’s Wi-Fi transport for normal Matter operation; it joins a Thread network and relies on a Border Router elsewhere in the home. This can be useful when one product family needs a Thread model while another variant uses Wi-Fi, but firmware, antenna routing and radio scheduling must be tested for the selected role.
Rank #2
- ESP32-C6-DevKitC-1 development board using the universal module ESP32-C6--1 with 16 MB SPIflash
- ESP32-C6 development board has complete Wi-F, low-power Bluetooth and other functions
- ESP32-C6--1 uses an onboard PCB antenna, and the module has a built-in ESP32-C6 chip, which has good functionality
- The ESP32 USB Type-C interface of the ESP32-C6 chip supports USB 2.0 full-speed mode and can also be used as the power supply interface of the development board. It can burn firmware to the chip, communicate with the chip through the USB protocol, and can also be used for debugging
- ESP32-C6-DevKit most of the pins of the module on the board have been led out to pin headers on both sides. Developers can easily connect various peripheral devices through jumpers according to actual needs. The development board can also be plugged into a breadboard for use
Do not infer Border Router behavior from the feature list
Having Wi-Fi and 802.15.4 in one package is not the same as having a validated Border Router implementation. Border routing requires software that manages the Thread interface, the IP backbone and the control plane between them. It also raises radio-coexistence and antenna-isolation questions. Treat the C6 as a possible building block, not an automatic gateway.
Where the ESP32-H2 fits
The ESP32-H2 is focused on low-power Bluetooth LE and 802.15.4 applications. Espressif’s H2 product overview lists Bluetooth LE and 802.15.4 features but does not list an integrated Wi-Fi radio. Consequently, an H2-only board cannot join a Wi-Fi network as a Matter-over-Wi-Fi endpoint.
Use H2 for a Thread Matter device
An H2 is a natural fit for a Thread sensor, switch or other 802.15.4 endpoint when the home already has a compatible Thread Border Router. The device’s application firmware must implement the Matter device type and Thread networking, and the board must provide a suitable 802.15.4 antenna path. The absence of Wi-Fi can be an advantage for a focused, low-power design because the product is not carrying an unused network radio, but actual energy and range depend on the complete hardware and firmware implementation.
Pair H2 with another SoC when Wi-Fi is needed
If an H2-based product must communicate with a Wi-Fi backbone, add a Wi-Fi-capable host or network interface. Espressif’s Matter documentation describes combining an ESP32-H device with a Wi-Fi SoC to build a Thread Border Router. In that arrangement, the H2 handles the 802.15.4 side while the host provides Wi-Fi, IP connectivity, system services and the software bridge.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11H2 is not a Wi-Fi substitute
Adding Bluetooth LE support, a USB connection or an application processor does not turn the H2 into a Wi-Fi endpoint. The design must include a separate Wi-Fi radio or Ethernet path if the product needs direct IP-backbone access. Document that interface in the system architecture before selecting a module or writing commissioning code.
Can either chip be a Thread Border Router by itself?
A Thread Border Router connects a Thread network to a backbone such as Wi-Fi or Ethernet. It is a system role, not simply a property granted by the presence of an 802.15.4 radio.
| Architecture | Thread side | Backbone side | Design interpretation |
|---|---|---|---|
| Single-chip concept | 802.15.4 in the same SoC | Wi-Fi in the same SoC, where available | Possible as a hardware concept with C6, but implementation, firmware support, RF scheduling and reference design must be verified. Do not assume a finished Border Router from the chip specification. |
| Two-SoC Border Router | ESP32-H-series radio co-processor | Separate Wi-Fi host SoC | Matches Espressif’s documented architecture and isolates the two network functions more clearly. |
| Wi-Fi plus Ethernet variant | 802.15.4 radio co-processor | Wi-Fi host with an optional Ethernet interface | The Ethernet accessory still depends on the main board; it is not an independent Border Router. |
Espressif’s documented reference hardware
Espressif’s Thread Border Router hardware guide describes a two-SoC board: an ESP32-S3-WROOM-1 acts as the Wi-Fi host and an ESP32-H2-MINI-1 acts as the 802.15.4 radio co-processor. The H2 is therefore not being used as a stand-alone Wi-Fi gateway in that reference architecture. An optional Sub-Ethernet daughter board uses a W5500 and depends on the main board; it cannot operate independently. See the ESP Thread Border Router hardware platforms page for the supported arrangement and board dependencies.
Rank #3
- Equipped with a high-performance 32-bit RISC-V processor with clock speed up to 160 MHz, and a low-power 32-bit RISC-V processor with clock speed up to 20MHz
- Supports 2.4GHz Wi-Fi 6 (802.11 b/g/n) and Bluetooth 5 (LE), with onboard antenna
- Built in 320KB ROM, 512KB of HP SRAM, 16KB LP SRAM and 4MB Flash memory. Onboard 1.47inch LCD display, 172×320 resolution, 262K color
- Adapting multiple IO interfaces, integrates full-speed USB port. Onboard TF card slot for external TF card storage of pictures or files
- Supports accurate control such as flexible clock and multiple power modes to realize low power consumption in different scenarios. Built-in RGB LED with clear acrylic sandwich panel for cool lighting effect
What this means for a product team
If you are building a Border Router, start with a complete reference architecture and its software support rather than selecting a chip from a radio table. You need a backbone interface, an 802.15.4 radio path, host-to-radio communication, Thread Border Router software, secure commissioning and a way to update both sides. A Thread end device does not become a Border Router merely because it contains 802.15.4.
Recommended Free Tools
Radio coexistence: the caveat behind “both radios in one chip”
Espressif’s ESP-IDF 6.1 H2 coexistence guide explains that supported radio functions share one 2.4 GHz RF module and use time-division multiplexing. Some combinations can be unsupported or unstable. The guide warns that competing Wi-Fi or Bluetooth traffic can increase Thread or Zigbee packet loss when a single RF path is shared, and it recommends a dual-SoC approach with separate antennas for Wi-Fi-based Border Router or gateway products. Read the ESP32-H2 RF Coexistence guide for the combinations and constraints documented for that release.
This is design guidance, not a universal performance benchmark. Packet loss, latency and recovery behavior depend on traffic patterns, antenna placement, enclosure materials, channel selection, firmware scheduling and the surrounding 2.4 GHz environment. A C6’s integrated radios may be attractive for a compact endpoint, but a gateway that must maintain a reliable Thread mesh while serving busy Wi-Fi clients deserves dedicated RF paths or a validated reference design.
What Espressif’s Matter documentation says
Espressif’s Matter Programming Guide, release v1.4.2, separates Wi-Fi-capable platforms from 802.15.4 Thread platforms. It states that Wi-Fi-enabled ESP32, ESP32-C and ESP32-S SoCs or modules can build Matter Wi-Fi devices, while ESP32-H series, ESP32-C5 and ESP32-C6 devices with 802.15.4 can build Matter Thread devices. The guide also describes combining an ESP32-H device with a Wi-Fi SoC to build a Thread Border Router.
“SoCs and modules(ESP32-H series, ESP32-C5, and ESP32-C6) with 802.15.4 can be used to build Matter Thread devices.” — Espressif Systems, ESP-Matter Programming Guide, release v1.4.2
Recommended: Fix Windows Errors and Clear Junk Files in Minutes - Free Scan →Recommended: Crashes or Glitches? A Free Driver Scan Usually Finds the Culprit →Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
The wording is important: C6 appears in both the Wi-Fi-capable ESP32 family and the 802.15.4 Thread list, while H2 appears in the 802.15.4 family and needs another network interface for Wi-Fi-backed roles.
Arduino-ESP32 support and commissioning paths
The current Arduino-ESP32 Matter documentation lists the C6 with Wi-Fi as its default network and documents Matter-over-Thread support. It lists the H2 with Thread as its default network and no Wi-Fi. The same documentation provides factory-fresh Thread commissioning examples for both C6 and H2, alongside Wi-Fi commissioning examples for Wi-Fi-capable targets. Consult the Arduino ESP32 Matter guide for the framework’s current target matrix and example flow.
Rank #4
- ESP32-C6-DevKitC-1 development board using the universal module ESP32-C6--1 with 4 MB SPIflash
- ESP32-C6 development board has complete Wi-F, low-power Bluetooth and other functions
- ESP32-C6--1 uses an onboard PCB antenna, and the module has a built-in ESP32-C6 chip, which has good functionality
- The ESP32 USB Type-C interface of the ESP32-C6 chip supports USB 2.0 full-speed mode and can also be used as the power supply interface of the development board. It can burn firmware to the chip, communicate with the chip through the USB protocol, and can also be used for debugging
- ESP32-C6-DevKit most of the pins of the module on the board have been led out to pin headers on both sides. Developers can easily connect various peripheral devices through jumpers according to actual needs. The development board can also be plugged into a breadboard for use
Use those entries as framework-version-specific support information, not as a promise that every board, Arduino core release or ESP-IDF configuration exposes identical menus and APIs. A practical validation sequence is:
- Confirm the exact chip or module selected by the board definition, rather than assuming that a similarly named board uses the same silicon.
- Select the network transport documented for that target: Wi-Fi for a C6 Wi-Fi design, or Thread for a C6 or H2 802.15.4 design.
- Build the framework’s matching Matter example and verify that the commissioning path shown by the example matches the intended transport.
- For Thread, provide a functioning Thread Border Router on the test network before diagnosing the endpoint’s Matter application.
- Repeat the test after changing framework or core versions, because the table and example behavior are tied to the documented release.
Which chip should you choose?
| Your product requirement | Better starting point | Why | What must still be checked |
|---|---|---|---|
| Direct Matter connection to a 2.4 GHz Wi-Fi network | ESP32-C6 | It includes the required Wi-Fi radio and also has 802.15.4 if a Thread variant is later needed. | Wi-Fi Matter firmware, antenna design, regulatory requirements, power budget and board support. |
| Thread-only sensor, switch or actuator | ESP32-H2 or ESP32-C6 | Both provide 802.15.4; H2 avoids carrying an integrated Wi-Fi feature that the endpoint does not use. | Thread firmware, Border Router availability, sleep behavior, antenna performance and commissioning support. |
| One product family with Wi-Fi and Thread variants | ESP32-C6 as the common silicon candidate | The same family can cover the two transports, reducing divergence in some hardware and software plans. | Validate radio scheduling, memory, certification and whether the chosen module is appropriate for each variant. |
| Dedicated Thread Border Router or gateway | Validated multi-SoC architecture, often an H2 radio co-processor plus Wi-Fi host | Separating the backbone and 802.15.4 functions addresses the system and coexistence requirements described by Espressif. | Host-to-RCP protocol, Border Router software, separate antennas, Ethernet options and complete-board support. |
| 802.15.4 radio co-processor for another processor | ESP32-H2 | Its documented feature focus matches a Thread/Zigbee radio role without requiring integrated Wi-Fi. | RCP firmware, transport between processors, update strategy and host operating environment. |
Practical build paths
Path 1: Matter-over-Wi-Fi endpoint with C6
- Choose a C6 module or development board with an antenna arrangement suitable for the final product class.
- Use the Matter Wi-Fi target documented for your framework release and confirm that the board definition exposes the C6 Wi-Fi interface.
- Implement the device’s Matter cluster and application behavior independently of the transport-specific commissioning code.
- Commission the device through the Wi-Fi flow shown by the framework example, then test reconnection after access-point restarts and power cycles.
- Before production, repeat testing with the final enclosure, antenna, power supply and regional radio configuration.
Path 2: Matter-over-Thread endpoint with H2
- Select an H2 board or module with a verified 802.15.4 antenna path; do not expect a Wi-Fi network interface from the H2 itself.
- Build the Thread Matter target documented for the SDK or Arduino release you use.
- Put a compatible Thread Border Router on the same test network before commissioning the endpoint.
- Use the framework’s Thread commissioning example to validate joining, operational addressing and Matter device behavior.
- Test sleep and wake timing, mesh reattachment and recovery from Border Router outages on the final hardware.
Path 3: Border Router with an H2 radio co-processor
- Define the backbone first: Wi-Fi, Ethernet or both, including how the host obtains IP connectivity.
- Assign the H2 to the 802.15.4 radio role and select a Wi-Fi-capable host SoC with documented support for the required RCP and Border Router software.
- Provide separate, well-characterized antenna paths where the reference design calls for them.
- Integrate host-to-radio transport, Thread Border Router services, secure provisioning and coordinated firmware updates.
- Exercise simultaneous backbone traffic and Thread mesh traffic; do not approve the design from idle commissioning tests alone.
Selection checklist before committing to a board
- Transport: Is the finished product a Matter-over-Wi-Fi endpoint, a Matter-over-Thread endpoint or a Border Router?
- Backbone: If Thread is used, where does Wi-Fi or Ethernet connectivity come from?
- Silicon: Does the selected device actually list the required integrated radio, or is a second SoC required?
- Framework: Does the exact ESP-IDF, ESP-Matter or Arduino-ESP32 release document the target and commissioning path?
- RF layout: Are antenna placement, isolation and coexistence constraints addressed for the enclosure and traffic pattern?
- Board role: Is the board an endpoint, an RCP, a host or a complete reference Border Router?
- Lifecycle: Can both the application processor and radio co-processor be updated and recovered in the field?
- Testing: Have you tested commissioning, reconnection, interference, power cycles and backbone loss on production-intent hardware?
Common mistakes and how to avoid them
Mistake: treating Matter as synonymous with Wi-Fi
Matter can use Wi-Fi or Thread. Start by naming the intended transport, then select silicon and firmware that implement it. A Thread endpoint still needs a Border Router somewhere in the deployment.
Mistake: claiming that H2 has Wi-Fi
Espressif’s H2 feature overview does not list integrated Wi-Fi. If a design brief says “H2 with Wi-Fi,” interpret that as an H2 paired with another Wi-Fi-capable component and document the component explicitly.
Mistake: assuming C6 must be used for Thread
C6 can build Matter Thread devices because it contains 802.15.4, but H2 can also serve that endpoint role. The choice depends on whether the product needs C6’s Wi-Fi capability, a common platform across variants or the H2’s focused radio role.
Mistake: calling a Thread endpoint a Border Router
An endpoint joins a Thread mesh; a Border Router connects that mesh to the IP backbone. Keep the roles separate in hardware diagrams, firmware packages, commissioning plans and product documentation.
Mistake: promising simultaneous-radio performance from specifications alone
Feature presence does not establish throughput, latency or packet-loss behavior under concurrent traffic. Follow Espressif’s coexistence guidance and validate the exact board, antenna and firmware combination under realistic Wi-Fi, Bluetooth and Thread load.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteMistake: treating a framework table as a permanent guarantee
The Arduino-ESP32 support matrix and examples describe documented framework behavior. Recheck them when changing core, SDK, board definition or release, and run the commissioning flow on the actual target.
Bottom line
For integrated Wi-Fi plus Thread capability, the ESP32-C6 is the direct fit. For a Thread or Zigbee-focused design that does not need Wi-Fi on the chip, the ESP32-H2 is the focused option. Both can support Matter over Thread, but a complete Thread Border Router requires a backbone interface, Border Router software and a validated system architecture; Espressif’s documented design uses an H2 radio co-processor with a separate Wi-Fi host.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
