Guide for Zigbee interference avoidance and network range/coverage optimization

This guide contains basic yet essential steps that should be applicable to all types of Zigbee setups but it has been specifically written for Zigbee solutions in mind that use a Zigbee Coordinator USB adapter, (e.g. applies to Home Assistant ZHA integration, Zigbee2MQTT, and deCONZ/Phoscon).

Note that this is partially posted in the forum for discussion and feedback since having problems getting this ZHA documentation pull request reviewed and approved → Update zha.markdown with tips on improving Zigbee network range by Hedda · Pull Request #18864 · home-assistant/ · GitHub (comments in that also has more external references that contain many other troubleshooting tips).

Zigbee interference avoidance and network range/coverage optimization

Sources of interference for radios can lead to transmission/reception loss or connection problems and show symptoms such as errors/failures when sending and receiving Zigbee messages/signals that can cause significant degradation in performance or even prevent devices from communicating at all. Below are some basic but essential tips for getting a good setup starting point to achieve better signal quality, improved coverage, and extended range.

Following all these optimization tips below should significantly improve the reception of your Zigbee radio adapter. The below insights describe working around the well-known limitations of low-power/low-bandwidth 2.4 GHz digital radios. It can that way resolve or avoid many known issues caused by interference or poor placement of your Zigbee radio adapter or devices.

All electric devices/appliances, especially computers and computer peripherals, generate electromagnetic interference (also known as EMI/EMI/RMI, or signal noise in layman’s terms), which can jam or interfere with signals transmissions on the 2.4 GHz radio band frequency, and degrade the wireless communication with your Zigbee adapter/devices.

For example, interference from USB 3.0 ports and unshielded USB peripheral cables are especially infamously known to affect 2.4 GHz radio reception for low-power/low-bandwidth devices. Therefore you should always place your Zigbee adapter far away as possible from any potential sources of EMI/EMI/RMI, preferably by using an adequately long shielded USB extension cable connected to a USB 2.0 port.

Zigbee technology also uses mesh networking (a type of network topology/architecture), which means that most mains-powered devices are a “Zigbee Router” that can act as a signal repeater and range extended by transmitting data over long distances by passing data messages through the Zigbee network mesh of intermediate devices to reach more distant Zigbee devices. Thus the key to a great and healthy Zigbee network is to add/have many “Zigbee Router” devices relatively close to each other in order to achieve good coverage and range. So you more or less just need to add/have several mains-powered Zigbee devices in the network that act as “Zigbee Router” devices.

Simple actions that will improve most Zigbee setups and common root causes of interference

  • Zigbee adapter hardware:
    • Bad performance from old/outdated/obsolete Zigbee adapter hardware or poor Zigbee adapter antenna:
      • Buy and use a supported Zigbee USB adapter based on newer/modern chip hardware.
        • Consider a Zigbee adapter that has an external antenna.
        • While older adapters might work, they could have obsolete hardware or old firmware, which prevents reliable operation.
    • Poor or outdated Zigbee adapter firmware on the Zigbee adapter:
      • Update to a later Zigbee chip firmware on the Zigbee adapter. Updating firmware is usually straightforward if the manufacturer or the chip maker provides one.
  • Zigbee adapters are RFI sensitive and can be very susceptible to all types of EMI/EMF interference:
    • Poor placement of the Zigbee adapter or wrong orientation of the Zigbee adapter antenna:
      • Use a long USB extension cable to place the Zigbee adapter away from interference and obstacles.
        • Ensure the USB extension cable is adequately shielded (thick cables usually have this).
          • A USB extension cable makes orienting the Zigbee adapter/antenna easier.
      • Try different physical placement and orientations of the Zigbee adapter or its antenna:
        • The optimal placement of the Zigbee adapter is close to the middle of the house as possible.
        • Try to place the Zigbee adapter at some distance away from walls, ceilings, and floors.
        • Try different orientations of the adapter’s external antenna (or the whole Zigbee adapter).
    • USB 3.0 ports/computers/peripherals are known culprits of RFI/EMI/EMF disruption. (See Ref. 1 and 2).
      • Make sure to only connect the Zigbee USB adapter to a USB 2.0 port (and not to a USB 3.x port).
        • If your computer only has a USB 3.x port then buy and connect the adapter via a powered USB 2.0 hub:
          • Using via USB 2.0 hub will in practice convert USB 3.0 to a USB 2.0 port and thus avoid USB 3.0 EMF.
            • A USB 2.0 hub that uses an external power supply will ensure power requirements are fulfilled.
      • Shield any unshielded computers/peripherals/devices by adding all-metal enclosures/chassis/casings.
        • Single-board-computers and USB 3.x hard drives are especially known as sources of EMF/EMI/RFI.
          • Be aware metal casings can decrease the performance of internal/built-in Zigbee adapters.
        • Also, be sure to use adequately shielded USB cables for any such peripherals/devices too.
    • 2.4 GHz RF Interference (RFI) from Wi-Fi Routers and Wi-Fi Access Points or other devices:
      • First of all, try to place your Zigbee adapter away from Wi-Fi access points or sources of WiFi.
      • Place Zigbee adapters far away from electrical/power wires/cables, power supplies, and household appliances.
      • Zigbee could have overlapping frequency ranges with Wi-Fi, see the section above on defining Zigbee channel use.
    • Add more and decrease the distance between Zigbee devices in Zigbee network mesh to get better range and coverage:
      • Zigbee uses mesh networking and depends on having many “Zigbee Router” devices to extend range and coverage:
        • Recommendation is to add additional mains-powered Zigbee devices known to be good Zigbee Router devices.
          • Add more Zigbee Router devices and reduce their distances to extend network mesh coverage and range.
            • Note that not all mains-powered devices have firmware that makes them act as a Zigbee Router device.
            • Some brands/models of Zigbee Router devices are known to only work well with the same brand of devices.
        • Buy a few known good dedicated Zigbee Router products (for example the “IKEA Tradfri Signal Repeater”).
          • Search community forums for more “Zigbee signal repeater” or “Zigbee range extender” Zigbee Router tips.
        • Buy a few additional new Zigbee USB adapters to use after re-flashing them with Zigbee Router firmware.
          • Reflash/reuse modern Zigbee USB adapters to act as Zigbee Router devices by changing Zigbee firmware.

Additional general Zigbee tips not mentioned in the above linked pull request:

  • Texas Instruments CC2652P or CC1352P based adapters are recommended for Zigbee2MQTT (Z2M also support ConBee/RaspBee and Silicon Labs adapters but they are not recommended).
  • While both ZHA and Zigbee2MQTT do support older Zigbee Coordinator adapters based on the old Texas Instruments CC253x (CC2530 and CC2531) they are not recommended any longer, so spare yourself the potential grief and instead just buy a newer Zigbee Coordinator adapter from the start.
  • Migration from an older Zigbee Coordinator adapter to a new Zigbee Coordinator adapter (with later firmware) a is a nice feature that both ZHA and Zigbee2MQTT have but if you are having problems with your Zigbee network after migration then it is generally recommended to cut your losses instead or troubleshooting and so just reset the new Zigbee Coordinator adapter to factory settings and join/pair devices manually one by one after factory resetting each device.
  • Be sure to factory reset devices that have previously been paired/added to another Zigbee gateway/hub/bridge as otherwise, they might not show up during the search when trying to join/pair/add the Zigbee device.
  • Before adding any devices, check that you have enough Zigbee router devices close to the new device that you want to add if it is not in the same room or within 10 feet from the Zigbee Coordinator adapter.
    • Zigbee router devices are mains-powered devices that are also known as Zigbee signal repeaters or range extenders, and if you do not have any, invest and add some mains-powered devices that will work as Zigbee routers. You use routers to increase the both the range and coverage as well as total number of Zigbee devices that can be used in a Zigbee network. The total number of Zigbee devices that you have on a Zigbee network depends on a few things, but you should know that Zigbee coordinator hardware and firmware only play a larger role in Zigbee networks with a lot of devices. More important is how many directly connected devices (“direct children”) versus how many routers are connected to your Zigbee coordinator.
    • Aim to start out with mains-powered devices before adding battery-operated devices as a “weak” Zigbee network mesh (e.g., the device is too far from the Zigbee coordinator or a Zigbee router) may prevent some devices from being paired. Zigbee router devices are also needed to increase the maximum of devices that can be connected to your Zigbee mesh network.
  • If possible try to pair your Zigbee devices in their intended final location, (and not pair it next to the Zigbee coordinator and then need to move it after).
    • Pairing a Zigbee device next to the Zigbee coordinator and then moving it later can result in dropped/lost connections or other issues.
      • If the device you want to add is not brand new and as such never paired before then you always have to make sure to first manually reset the device to its factory default settings before you will be able to add/pair it.
  • Cheap devices like those manufactured by Tuya and Aqara/Xiaomi are infamously known for not following the standard Zigbee specifications and can have issues pairing and sometimes even cause stability issues in a Zigbee network, especially when used either as a Zigbee Router or when it connects via an other Zigbee Router instead of connecting directly to the Zigbee Coordinator.
    • Note that some Zigbee devices are also not fully compatible with all brands of Zigbee router devices. Xiaomi/Aqara devices are for example known not to work with Zigbee router devices from Centralite, General Electrics, Iris, Ledvance/OSRAM, LIGHTIFY/Sylvania, Orvibo, PEQ, Securifi, and SmartThings/Samsung. Better results can usually be achieved by using mains-powered devices IKEA and Nue/3A Home or dedicated DIY routing devices based on Silicon Labs EFR32MGxx, Texas Instruments CC253x/CC26x2, or XBee Series 2/3 Zigbee radios.
  • Both ZHA and Zigbee2MQTT require handlers/converters for non-standard Zigbee clusters and attributes so be prepared to either code your own handler/converter or open a new device support request if buying a newly released device or old odd devices that are not commonly used so no one has previously coded handlers/converters for it if it does not follow standard Zigbee clusters and attributes specifications.
  • Some battery-operated Zigbee devices are known to have problems with pairing if they have Low battery voltage.
    • Some people have reported replacing the battery on their newly received Xiaomi/Aqara devices solved pairing issues.
  • If joining/pairing do not work properly due to the interview failing try to join/pair the device again and be patient as the pairing of some Zigbee devices may require multiple attempts and you may sometimes need to try again and again.
    • Some devices, like example those from Xiaomi/Aqara, are also known to not be 100% compliant with the standard Zigbee specifications for joining/pairing and may therefore require many paring attempts over 10-20 minutes or even more.
    • If joining/pairing fails try resetting the device to factory default settings.
    • If joining/pairing still fails you can try pairing the device closer to the Zigbee Coordinator adapter but be aware that depending on the device you might not be able to then move it further away as it could be that it will then not automatically re-pair to a Zigbee router device so manual re-pairing will be nessesary.
  • General tip to new Zigbee users is that, while there is no official list of supported devices, some ZHA users take comfort that blakadder maintains an unofficial Zigbee Device Compatibility Repository which anyone can submit compatibility reports to, it can be found at and currently contains independent compatibility lists and device pairing tips for several home automation gateway/bridge/hub software, including but not limited to open source Zigbee implementations such as; ZHA, Tasmota, Zigbee2MQTT, deCONZ, Zigbee for Domoticz, and ioBroker.

PS! Many of the above tips will also apply to Thread and Bluetooth based adapters/devices as well.


Instead of a USB connected coordinator the use of an Ethernet connected coordinator like those available from Tubes store can get your coordinator even further away from EMI sources.

1 Like

Yes that is indeed another way to move your Zigbee Coordinator further away from possible sources of interference and place it in a more ideal location like the very centre of your house, (and I personally recommend TubeZB and ZigStar network-attached Zigbee Coordinator solutions for some situations where simply using a long USB extension cable is not enough to get the adapter in an ideal placement).

However, a network-attached Zigbee Coordinator solution does introduce additional complexity and introduce your LAN as another SPOF (Single-Point-Of-Failure) for your Zigbee network setup, and I therefor personally believe that in most use bases it will be easier to just use either up to 5 meters / 15 feet shielded USB extension cable or if even longer USB extension distance is needed you can achieve up to around 30 meters by using inexpensive “USB Ethernet RJ45 Extender Adapter” converters which easily and practically convert any single CAT5e/CAT6 shielded Ethernet cable with RJ45 connectors into a very long USB extension cable, (note that 30 meters or 100 feet is the recommended maximum length for USB 2.0 data traffic over a passive cable). See for example these USB extension solutions:



One other great use-case for ethernet-based Zigbee adapters is that if you run a virtualized environment (VMware vsphere for example) you could move the HA virtual machine around on different servers during maintenance, set up high availability or replication. Not something that would have a big user base but for people already running virtual environments it’s a big plus.

1 Like

Another possible more advanced flexible solution to get USB or serial adapters into a virtual machine if you need more virtual machines or different types of USB/serial adapter virtualization can to either use a genetic Serial to TCP/IP network proxy application for example which could be a DIY software-based like “ser2net” on a Raspberry Pi Zero other Serial to Ethernet converter server (such as commercial Serial-Over-IP and USB-Over-IP hardware appliance solutions that do the same, like products from Silex Connectivity Solutions and Digi connectivity solutions such as their AnywhereUSB series as examples). Zigbee2MQTT has a guide for ser2net here that for the server side also works for ZHA:

Home Assistant Operating System running in a Virtual Machine on a virtualization hypervisor actually has quite a large userbase according to the current analytics statistics which say 34%+ today, though I suspect that most people do not run Home Assistant in a redundant environment with the option to do live-migration of the virtual machine to other hardware for maintenance (e.i. VMotion in VMware vSphere):


1 Like

Yeah, but if you consider replication, high availability and so on these are often licenced features (vmware vpshere licence for example). Hence my comment about the not so large user-base :slight_smile:

Off-topic as not related to interference, stability or range/coverage but another very important general tip is by the way to be sure to store/copy your Zigbee network backups to another secondary storage location so that you can restore backups in case your Zigbee setup becomes corrupt or primary storage fails completely and you need to reinstall ZHA or Zigbee2MQTT and then want to restore your Zigbee network, (if you are using ZHA then the Zigbee network backups should be part of Home Assistant’s Backup). Zigbee network backups are important since not all Zigbee network data is stored locally on the Zigbee Coordinator adapter (at least not for Zigbee 3.0 networks).

Common tip to achieve off-site backups is to backup Home Assistant’s Backups to Google Drive (cloud):

Possibly off topic but:

Does anyone know where, in a home assistant backup, the ZigBee coordinator backup is?

If I needed to restore a ZigBee coordinator backup to a new coordinator then where would I find the backup?

Zigbee database (zigbee.db) is part of the standard Home Assistant core backup but not exactly sure now that you ask if a complete backup is also done automaically of Zigbee network of APS keys or NWK address tables that are stored in NVRAM on the Zigbee Coordinator adapter, but that is anyway probably more on-topic if asked in this other thread instead →

Note that it is at least easy to download latest backup in JASON format via the ZHA GUI (and also option there to migrate to a other adapter which automatically runs a procedure for backup and restore).

Thank you for the guide @Hedda !

I have one question which is not specifically pointed out in the guide.
Is there any problems using a USB 3.0 extension cable when it is connected to a USB 2.0 port?

There is no problem since USB cables are backwards compatible, in fact it is usually better since USB 3.0 cables are normally betted shielded. USB 3.0 cables have the same numbers of wires/pins so in practice the only difference is just that they are better shielded. Shielded cables are better to use for radios and long cable lenghts.

Other than better shielding USB 3.0 cables also have lower resistance and use thicker gage so can therefor be rated to transfer more power and higher data rates but that only matter to USB 3.0 devices and not to USB 2.0 devices.

Thank you,
I know of the backwards compatibility (since it is what I am currently using). It was mostly if a usb 3 cable connected to usb 2 port could create EMF interference similarly to if it was connected to a usb 3 port. But I guess not :slight_smile:

My external SSD is connected to usb 3 port though. I have shielded that cable in tinoil to minimize the interference.

Hi, few days ago I’ve tried to ask something similar on reddit, might go off topic here a bit but it’s related.

From what I read here, I should move the dongle few meters away to deal with Zigbee, but what about other devices interfering with each other:

I am about to make a setup with HA running on r4 pi 8gb. I plan to stack two sonoff 4ch pro’s and several mini r3’s (controlling SSR’s located in the fuse box, which in turn control heating and water boiler) alongside router, switch and pi4 in a large in-wall media box, say 500x500mm
Are there EMI issues here with router-sonoff or sonoff-sonoff or sonoff-pi4 and what would you recommend?


First of all, are any of those really Zigbee devices? (Sonoff also make WiFi devices and if they are WiFi devices and not Zigbee devices then it is off-topic here in this specific thread).

If they are Zigbee devices then there should be no problem as long as you have a Zigbee Router devices (such for example an IKEA Trådfri Signal Repeater) close enough but not too close to those devices and still got good connection to the Zigbee network mesh as a whole, like in the same room but not right next to all those sources of EMF.

So the general recommendation is to build out your Zigbee network mesh by adding more Zigbee Router devices.

Thank you @Hedda for this very comprehensive write-up. Much appreciated!

Does anyone have constructive feedback on how to rewrite this pull request for ZHA documentation?

I have already rewritten it many times and now I’m no longer sure how to proceed (or if I even want to).

Unfortunately, PR is also still locked and I am having trouble to get a message to frenck about that fact: