Direct Answer Snippet:
Zigbee network repairs can take unusually long when ZWave LR
devices are in range because Long Range mode introduces extendedrange transmissions,
long airtime usage, and increased CPU/RF scheduling load on multiprotocol hubs.
Although Zigbee and ZWave use different frequencies, ZWave LR traffic can
congest the hub’s radio processor or firmware scheduler, slowing Zigbee route
rediscovery, neighbor table rebuilding, and mesh healing operations.
Preliminary Diagnostic Steps
Before applying fixes, confirm that ZWave LR is affecting
Zigbee mesh repairs:
1. Check If Any Devices Are Using ZWave LR
Open your ZWave controller logs (ZWave JS, Hubitat,
SmartThings) and confirm:
* LR devices appear with longrange signal metrics
* Devices connect directly to the hub at extreme distances
* Highpower LR packets appear frequently
LR traffic is more resourceintensive than classic ZWave.
2. Review Hub Radio and CPU Workload
Multiprotocol hubs (e.g., SmartThings, Hubitat, Home
Assistant with combo sticks) may show:
* Radio queues backing up
* Long processing delays
* Overloaded firmware scheduler
* Increased radio switching/duty cycle
These delays directly impact Zigbee’s network healing.
3. Examine Zigbee Routing Diagnostics
Using ZHA, Zigbee2MQTT, or ConBee II logs, look for:
* High route discovery times
* Repeated neighbor table rebuilds
* Retry storms
* Low LQI spikes during ZWave LR activity
If these align with ZWave LR packets, crossprotocol
congestion is occurring.
4. Evaluate RF Environment Stability
Although ZWave LR is subGHz, highpower transmissions can
cause:
* RF desensitization
* Reduced Zigbee receive sensitivity
* Processor prioritization delays
Confirm using an SDR scan or hub diagnostics.
StepbyStep Technical Fix
Below are precise, advanced steps to eliminate Zigbee repair
delays:
1. Separate Zigbee and ZWave Radios Physically
Use:
* A dedicated Zigbee USB stick (Sonoff ZBDongleP/U, ConBee
II)
* A separate ZWave 700/800 LR stick
Avoid integrated dualprotocol radios—these are most prone to
congestion.
2. Reduce ZWave LR Transmission Frequency
Adjust configuration settings for LR devices:
* Increase report intervals
* Disable unnecessary sensor reports
* Reduce power reporting frequency
This lowers the scheduler load on the hub.
3. Move the Hub Away From LR Devices
Place LR devices at least 2–3 meters away from the Zigbee
hub during repairs.
Highpower LR packets can desensitize nearby radios.
4. Run Zigbee Network Repair Without ZWave Load
Before initiating a Zigbee heal:
* Temporarily disable ZWave polling
* Pause ZWave automations
* Power off LR devices if possible
This gives Zigbee exclusive access to the radio processor.
5. Optimize Zigbee Channel Selection
Choose a channel less sensitive to interference bursts:
* Zigbee 20
* Zigbee 21
* Zigbee 25
These channels show fewer issues on mixed environments.
6. Update Firmware for Both Protocols
Firmware updates often include improvements related to:
* Radio coexistence
* Task scheduling
* Packet prioritization
Make sure:
* Zigbee coordinator firmware is updated
* ZWave radio firmware supports LR optimizations
Preventing Future Conflict
1. Use Dedicated Controllers for Each Protocol
Best practice:
* Zigbee coordinator → one device
* ZWave LR controller → separate stick or hub
This eliminates shared RF stack bottlenecks.
2. Avoid Running ZWave LR in HighDensity Environments
If your Zigbee mesh has 50+ devices, LR can overwhelm the
hub’s processor.
3. Add More Zigbee Routers
Additional routers:
* Improve healing speed
* Reduce dependency on the coordinator
* Minimize delays during network rebuilds
Recommended devices: smart plugs, inwall switches.
4. Assign Static IPs for the Hub and Controllers
A Static IP ensures consistent network routing and prevents
delays during repair cycles.
5. Schedule Repairs During LowTraffic Hours
Latenight hours (1–4 AM) are ideal to avoid
* Packet congestion
* Active automations
* Competing ZWave LR traffic