A Complete Troubleshooting Guide With Real Solutions That Actually Work
You finally got your smart home running. Your Z-Wave locks are responding, your sensors are reporting, and everything inside Home Assistant feels smooth. Then you add an Aqara Zigbee hub to the mix. Suddenly, your Z-Wave devices start acting weird. Commands get delayed. Some devices go unavailable. Your Z-Wave JS integration throws errors you have never seen before.
I know exactly how that feels because I went through the same frustrating experience. I spent three full weekends diagnosing what seemed like a Z-Wave problem, only to discover that my brand new Aqara M2 hub was the real troublemaker.
In this guide, I will explain exactly why this happens, what is going on behind the scenes technically, and how to fix it step by step without replacing any of your hardware.
[📌 Image Suggestion 1: A diagram showing a typical smart home setup with both an Aqara Zigbee hub and a Z-Wave USB stick connected to a Home Assistant server, highlighting potential interference zones.]
Understanding the Core Problem: It Is Not What You Think
Here is the surprising truth. Zigbee and Z-Wave operate on completely different radio frequencies. Z-Wave runs on 908.42 MHz in North America or 868.42 MHz in Europe. Zigbee operates on 2.4 GHz. So logically, they should never interfere with each other directly.
But the interference you are experiencing is real. It is just not happening at the radio frequency level.
The actual problem falls into one or more of these categories:
- USB bus contention when both dongles share the same USB controller
- Electromagnetic interference (EMI) from nearby hardware
- CPU and resource competition on your Home Assistant host
- Software-level conflicts within Home Assistant itself
- Network congestion when the Aqara hub floods your local network
Let me break each one down so you can identify exactly which issue is affecting your setup.
USB Bus Contention: The Number One Hidden Cause
Why Sharing a USB Controller Destroys Z-Wave Performance
Most people run Z-Wave JS through a USB stick like the Zooz ZST39 or the Nortek HUSBZB-1. If you also added a Zigbee coordinator via USB, like a Sonoff Zigbee 3.0 dongle, alongside your Aqara hub, you might have two USB radios competing for bandwidth on the same internal USB bus.
Even if you are only using the Aqara hub over Wi-Fi and a single Z-Wave USB stick, the problem can still occur. Many single-board computers like the Raspberry Pi 4 share USB and Ethernet on the same bus. When the Aqara hub sends frequent updates over your network, it increases the load on that shared bus.
Real Scenario I Experienced
I was running Home Assistant OS on a Raspberry Pi 4. My Z-Wave stick was plugged into one of the USB 3.0 ports. The moment I added my Aqara M2 hub through the HomeKit Controller integration, my Z-Wave network started showing latency spikes of 2 to 5 seconds on every command.
The reason was simple. The Aqara hub was sending multicast mDNS packets constantly for HomeKit discovery. These packets were flooding through the Ethernet port, which on the Pi 4 shares the same VIA Labs VL805 USB 3.0 controller. Every burst of network traffic from the Aqara hub momentarily starved my Z-Wave stick of USB bandwidth.
[📌 Image Suggestion 2: A screenshot showing USB device tree on a Raspberry Pi 4, highlighting how Ethernet and USB ports share the same controller chip.]
Electromagnetic Interference at Close Range
How Physical Proximity Causes Problems
Even though Zigbee and Z-Wave use different frequencies, the Aqara hub contains radio transmitters that emit electromagnetic energy. When your Z-Wave USB stick is physically close to the Aqara hub, the broadband noise from the Aqara hub’s transmitter can desensitize your Z-Wave receiver.
This is especially true if:
- Your Z-Wave stick is plugged directly into the same device where the Aqara hub sits nearby
- You have both devices on the same shelf or desk without separation
- You are using unshielded USB cables or cheap USB extension cables
How Much Distance Do You Actually Need
Based on my testing and reports from the Home Assistant community, maintaining at least 3 feet (1 meter) of separation between your Z-Wave coordinator and the Aqara hub eliminates EMI issues for the vast majority of users. Using a high-quality shielded USB extension cable for your Z-Wave stick makes a massive difference even in tight spaces.
Software-Level Conflicts Inside Home Assistant
The Z-Wave JS Add-on and Resource Competition
Z-Wave JS runs as a separate process, either through the official Z-Wave JS add-on or through zwavejs2mqtt. It needs consistent, uninterrupted access to your Z-Wave USB stick’s serial port.
When you add an Aqara hub, Home Assistant has to manage additional integrations. Depending on how you integrate the Aqara hub, the resource impact varies:
| Integration Method | CPU Impact | Network Impact | Conflict Risk |
|---|---|---|---|
| Aqara Home (Cloud) | Low | Low | Low |
| HomeKit Controller | Medium | High (mDNS) | Medium-High |
| Zigbee2MQTT (with separate Zigbee stick) | High | Low | Medium |
| ZHA (with separate Zigbee stick) | Medium | Low | Medium |
The HomeKit Controller mDNS Storm
If you added the Aqara hub via the HomeKit Controller integration, you should know that the Aqara M1S, M2, and E1 hubs are notorious for generating excessive mDNS traffic. This is not a bug in Home Assistant. It is how the Aqara firmware implements HomeKit Accessory Protocol discovery.
Each Aqara device connected to the hub advertises itself separately over mDNS. If you have 20 Aqara sensors, that means 20 separate mDNS service records being broadcast and refreshed regularly. On a busy network, this can cause significant processing overhead in Home Assistant’s event loop, which indirectly delays Z-Wave command processing.
[📌 Image Suggestion 3: A Wireshark capture screenshot showing mDNS packets from an Aqara hub flooding the local network.]
Network-Level Interference: The Overlooked Factor
Wi-Fi Channel Overlap With Zigbee
Your Aqara hub connects to your network via Wi-Fi on the 2.4 GHz band. Your Aqara Zigbee devices also communicate with the hub on the 2.4 GHz band. While this does not directly affect Z-Wave, it creates an indirect problem.
When your Wi-Fi network experiences congestion or packet loss due to Zigbee-Wi-Fi overlap, the Aqara hub’s connection to Home Assistant becomes unstable. Home Assistant then spends extra resources trying to reconnect, poll, and re-authenticate the Aqara integration. This resource drain slows down all other integrations, including Z-Wave JS.
The Channel Conflict Map
Here is how Zigbee and Wi-Fi channels overlap:
- Zigbee Channel 11 overlaps with Wi-Fi Channel 1
- Zigbee Channel 15 overlaps with Wi-Fi Channels 1-6
- Zigbee Channel 20 overlaps with Wi-Fi Channels 5-8
- Zigbee Channel 25 overlaps with Wi-Fi Channel 11-12
- Zigbee Channel 26 has the least Wi-Fi overlap
The Aqara hub defaults to automatic Zigbee channel selection, which often lands on channel 11 or 15. If your router is on Wi-Fi channel 1 or 6, you have a direct collision.
[📌 Image Suggestion 4: A visual chart showing the Zigbee and Wi-Fi channel overlap on the 2.4 GHz spectrum, with conflict zones highlighted in red.]
Step-by-Step Troubleshooting Guide
Step 1: Confirm the Interference Is Real
Before changing anything, document the problem:
- Open Home Assistant and go to Settings → Devices & Services → Z-Wave JS
- Click on any device that has been acting unreliable
- Check the Last Seen timestamp and note any gaps
- Open Developer Tools → Logs and filter for
zwave_js - Look for messages containing “node not responding,” “timeout,” or “dropped”
- Write down when these errors occur and how frequently
Now temporarily power off your Aqara hub completely. Unplug it. Wait 30 minutes and monitor your Z-Wave network. If the errors stop or decrease significantly, you have confirmed that the Aqara hub is contributing to the problem.
Step 2: Physically Separate Your Devices
Move your Z-Wave USB stick away from the Aqara hub:
- Purchase a USB extension cable that is at least 3 feet long and shielded (I recommend the Sabrent or CableCreation brands)
- Plug your Z-Wave stick into the extension cable
- Place the stick at least 1 meter away from the Aqara hub, your router, and any other radio devices
- Elevate the Z-Wave stick if possible — placing it higher reduces ground-plane interference
Step 3: Fix the USB Bus Problem
If you are running on a Raspberry Pi or similar SBC:
- Check which USB controller your Z-Wave stick is connected to:Bash
lsusb -t - If your Ethernet and Z-Wave stick share the same bus, move the Z-Wave stick to a USB 2.0 port instead. USB 2.0 ports on the Pi 4 use a different controller
- If you are running on an x86 machine, check your USB topology and ensure the Z-Wave stick is on its own root hub
Step 4: Optimize the Aqara Hub Network Configuration
- Open the Aqara Home app
- Go to your hub settings
- If possible, assign your Aqara hub a static IP address through your router’s DHCP settings — this reduces ARP broadcast traffic
- Place your Aqara hub on a separate VLAN or IoT network if your router supports it
- Ensure your Aqara hub’s Wi-Fi is on a channel that does not overlap with its own Zigbee channel
Step 5: Reduce mDNS Traffic (If Using HomeKit Controller Integration)
- Consider switching from the HomeKit Controller integration to the Aqara integration (cloud-based but lighter on local network)
- If you must use HomeKit Controller, install an mDNS reflector or filter on your network to reduce broadcast storms
- In your router, enable IGMP snooping to prevent multicast packets from flooding all ports
Step 6: Upgrade Your Home Assistant Hardware
If you are still on a Raspberry Pi and running more than 30 total smart devices, it might be time to upgrade:
- Minimum recommended: Intel N100 mini PC with 8 GB RAM
- My current setup: Beelink S12 Pro running Home Assistant OS — zero USB contention issues, dedicated Ethernet controller, and enough CPU to handle multiple integrations simultaneously
[📌 Image Suggestion 5: A photo comparison showing a Raspberry Pi setup versus a mini PC setup, with Z-Wave stick and Aqara hub properly separated.]
Advanced Fixes for Persistent Interference
Switching to a Dedicated Zigbee Coordinator
If you are technically comfortable, the best long-term solution is to stop using the Aqara hub entirely for device communication:
- Purchase a dedicated Zigbee coordinator like the SONOFF Zigbee 3.0 USB Dongle Plus or Tube’s Zigbee Gateway
- Pair your Aqara Zigbee devices directly to this coordinator using Zigbee2MQTT or ZHA in Home Assistant
- Keep the Aqara hub only for devices that require it (like the Aqara camera or the Aqara G4 doorbell)
- This eliminates the Wi-Fi-based mDNS traffic and gives you direct local control
Adjusting Z-Wave JS Timeout Settings
In the Z-Wave JS control panel:
- Go to Settings → Z-Wave JS → Configuration
- Increase the command timeout from the default to 30 seconds
- Enable soft reset if your controller supports it
- Run a re-interview on devices that have been reporting as dead or unresponsive
Using a Z-Wave Long Range Controller
If you have a newer Z-Wave 800 series controller like the Zooz ZST39 LR, enable Z-Wave Long Range mode for distant devices. Z-Wave LR uses a different modulation scheme that is more resistant to interference from other electronics in your home.
My Personal Experience and What Finally Fixed It
Let me share my complete journey so you can learn from my mistakes.
The Setup:
- Raspberry Pi 4 (4 GB) running HAOS
- Nortek HUSBZB-1 (combined Z-Wave/Zigbee stick)
- Aqara M2 Hub added via HomeKit Controller
- 15 Z-Wave devices (locks, switches, sensors)
- 22 Aqara Zigbee devices on the Aqara hub
The Symptoms:
- Z-Wave door locks took 3 to 8 seconds to respond
- Two Z-Wave motion sensors showed as “dead” every morning
- Home Assistant logs showed constant
"node not ready"warnings - Everything worked fine before adding the Aqara hub
What I Tried (In Order):
- ❌ Rebooted everything — temporary fix, problem returned within hours
- ❌ Changed Z-Wave channels — no improvement
- ❌ Updated Z-Wave JS to latest version — no improvement
- ✅ Moved Z-Wave stick to USB 2.0 port with extension cable — 50% improvement
- ✅ Switched Aqara hub from HomeKit Controller to Aqara cloud integration — 30% improvement
- ✅ Moved to an Intel N100 mini PC — problem completely eliminated
The Root Cause: It was a combination of USB bus contention on the Pi 4 and mDNS flooding from the HomeKit Controller integration. Neither issue alone was catastrophic, but together they created enough latency to make my Z-Wave network unreliable.
[📌 Image Suggestion 6: A before-and-after performance chart showing Z-Wave response times with and without the fixes applied.]
Prevention Tips for Future Setups
If you are planning to run both Aqara Zigbee and Z-Wave in the same Home Assistant instance, follow these rules from the start:
- Never use a Raspberry Pi for mixed-protocol setups with more than 20 total devices
- Always use USB extension cables for radio dongles
- Keep at least 1 meter between any two radio devices
- Assign static IPs to all smart home hubs on your network
- Use VLANs to isolate IoT traffic from your main network
- Monitor your logs weekly for early signs of interference
- Choose one Zigbee management method — either the Aqara hub or a direct coordinator, not both managing overlapping devices
Frequently Asked Questions (FAQ)
Can Zigbee and Z-Wave truly interfere with each other since they use different frequencies?
They do not interfere at the radio frequency level. The interference happens at the USB bus, software, and network levels. The symptoms mimic RF interference, which is why most people assume it is a frequency conflict. In reality, it is a resource contention problem on your Home Assistant host.
Should I get rid of my Aqara hub and switch everything to Z-Wave?
Not necessarily. Aqara makes excellent Zigbee sensors that are affordable and reliable. The better approach is to either use a dedicated Zigbee coordinator with Zigbee2MQTT or ZHA and retire the Aqara hub, or keep the Aqara hub but optimize your setup following the steps in this guide.
Does this problem happen with all Aqara hubs or just specific models?
The mDNS flooding issue is most common with the Aqara M2 Hub and the Aqara M1S Hub when used via the HomeKit Controller integration. The Aqara E1 Hub tends to generate less traffic because it supports fewer devices. However, all Aqara hubs can contribute to USB bus contention if your hardware setup is not optimized.
Will using a Zigbee2MQTT setup instead of the Aqara hub fix the interference?
It can actually make it worse if you do not plan carefully. Running both a Zigbee coordinator and a Z-Wave coordinator on USB means two radios competing for USB bus time. Use separate USB controllers, extension cables, and preferably an x86 machine with multiple USB root hubs.
Is there a Z-Wave JS setting that can make Z-Wave more tolerant of delays?
Yes. You can increase the send and response timeouts in the Z-Wave JS configuration. You can also enable the “soft reset” feature and use the “healing” function to optimize your Z-Wave mesh. However, these are band-aids. The real fix is eliminating the source of the interference.
Can I run Aqara Zigbee and Z-Wave on the same USB dongle?
Yes, dongles like the Nortek HUSBZB-1 and the new SkyConnect include both Zigbee and Z-Wave radios. However, using the combined dongle alongside an Aqara hub means you now have two Zigbee coordinators, which can cause Zigbee channel conflicts. Pick one coordinator for Zigbee and stick with it.
Final Thoughts
The coexistence of Aqara Zigbee and Z-Wave in Home Assistant is absolutely achievable. Thousands of smart home enthusiasts run both protocols without any issues. The key is understanding that the interference is not about radio waves fighting each other. It is about your host machine’s limited resources being overwhelmed.
Fix the USB topology. Reduce unnecessary network chatter. Give your hardware room to breathe. And if you are still on a Raspberry Pi with a growing smart home, seriously consider upgrading to a mini PC. That single change transformed my experience from daily frustration to rock-solid reliability.
Your smart home should make life easier, not give you another problem to troubleshoot every weekend.
[📌 Image Suggestion 7: A clean photo of an optimized Home Assistant setup showing proper device separation, cable management, and a dedicated mini PC running the system.]