Supported Adapters

All officially supported adapters are listed on this page. Note that before an adapter can be used with Zigbee2MQTT it has to be flashed with a coordinator firmware (some adapters come preflashed).


Want to migrate to a different adapter? Read this

The adapters below are recommended because they use powerful chips, can handle large networks and are well-supported.

Based on Texas Instruments CC2652/CC1352 chip:

(in order of first appearance)


The adapters below are well-supported but use outdated chips.


The adapters below are experimental, don't use these if you want a stable setup.

  • ZiGate

    Initial development started on experimental (alpha stage) support for various ZigGate adapters (based on NXP Zigbee chips like JN5168 and JN5169). This include all ZiGate compatible hardware adapters with ZigGate 3.1d firmware or later.
    If Zigbee2MQTT fails to start, try adding the following to your configuration.yaml

    adapter: zigate

  • Silicon Labs EZSP v8

    Initial development started on experimental (alpha stage) support for various adapters based on Silicon Labs EM35X and EFR32MG SoC families with EmberZNet NCP 6.7.8 firmware or later via EZSP version 8 (EmberZNet Serial Protocol) interface. This include all hardware based on SoCs/Modules from Silabs EFR32MG21/MGM210 and EFR32MG12/MGM12 series
    If Zigbee2MQTT fails to start, try adding the following to your configuration.yaml

      adapter: ezsp


Before buying an adapter, please read the notes below!

  • Want to migrate to a different adapter? This may require repairing all your devices in some cases, see FAQ
  • Network adapters connected via WiFi might have reduced stability as the serial protocol does not have enough fault-tolerance to handle packet loss or latency delays that can normally occur over WiFi connections. If cannot use a locally connected USB or UART/GPIO adapter then the recommendation is to use remote adapter that connected via Ethernet (wired) to avoid issues.
  • What are the differences between the various CC2652/CC1352 chips?
    • Chips ending with P have a power amplifier which support up-to 20dBm vs 5dBm on adapters ending with R/RB.
    • Chips starting with CC1352 support the sub-1 GHz frequency (which is not relevant for Zigbee since it uses 2.4 GHz), CC2652 only supports 2.4 GHz. So for Zigbee2MQTT purposes there is no difference between CC1352 and CC2652.
    • Chips ending with RB don't require a crystal on the PCB, this only makes a difference for the manufacturing process.

Flashing CC1352/CC2652/CC2538 based adapters

Adapters based on CC1352 or CC2652 chips can be flashed by putting them in the bootloader. See your adapter manual on how to do this. After you have done this one of the following tools can be used to flash it.

Flashing an existing adapter

The above flashing tools can be used to upgrade the firmware on an existing adapter without needing to repair devices. See the FAQopen in new window for information on what does and does not require repairing of devices.

Is your OS unable to find your device?

If you're asking yourself "Why won't my dongle or adapter show up?" when you are using (for example) Flash Programmer 2, chances are that your OS can't communicate with your device over VCP (Virtual COM Port), causing your dongle not showing up as a flashable device. To fix this problem, be sure to install a USB-to-UART bridge VCP driver like the one at Silicon Labsopen in new window or FTDI Chipopen in new window.


Besides serving as a coordinator some adapters can also be used as a Zigbee router (check if there is a router firmware by clicking on your adapter). To factory reset/pair:

  • Texas Instruments CC2531: press the S2 button for 5 seconds.
  • Texas Instruments CC2530: power on/power off the device three times (power on, wait 2 seconds, power off, repeat this cycle three times).
  • Adapters based on CC2652/CC1352: single press (one of the) buttons on the device