You have a Hue Bridge for your lights, a SmartThings hub for your sensors, and an Echo with built-in Zigbee for voice control of a few extra plugs. Each hub manages a separate Zigbee network. They all want to use the 2.4GHz band. If they end up on the same channel, or even on adjacent channels, you start seeing drops on the weakest devices in each network. The fix is straightforward but the symptoms can be confusing because each hub looks fine in its own app.
The basic conflict
Zigbee uses channels 11 through 26 in the 2.4GHz band. Each channel is 2 MHz wide. Two hubs on the same channel share airtime, but more importantly, two hubs on adjacent channels (within about 5 MHz of each other) interfere because the radios overlap at the edges.
If your Hue Bridge is on channel 15 and your SmartThings hub is on channel 16, they will not collide directly but they will degrade each other. If both are on channel 15, they share airtime and both perform worse than either alone.
How to find what channel each hub is on
This is the part that varies by hub.
- Hue Bridge: open
http://<bridge-ip>/api/<your-api-key>/configin a browser. Look for thezigbeechannelfield. If you do not have an API key, generate one through the developer portal or use an app like Hue Essentials that exposes the channel. - SmartThings: in the app, go to your hub, scroll to advanced settings. The Zigbee channel is listed.
- Echo: not officially exposed. Amazon does not let you see or change it.
- Hubitat: Settings, Zigbee Details. Channel is shown.
- Home Assistant ZHA: Settings, Devices & Services, Zigbee Home Automation, configuration. Channel and network ID are shown.
Document each hub’s channel before changing anything.
Pick channels that do not fight
If you have two hubs, put them on channels at least 5 apart, ideally further. With three hubs, spread them across the band:
- Hub 1: channel 11
- Hub 2: channel 20
- Hub 3: channel 25
Avoid channels that overlap your Wi-Fi. If your Wi-Fi is on channel 1, do not put any Zigbee on 11. If your Wi-Fi is on channel 6, avoid Zigbee 15. If your Wi-Fi is on 11, avoid Zigbee 20.
If one of your Zigbee networks is an Echo and you cannot change its channel, the Echo defaults to channel 24 or 25 in most regions. Put your other hubs on the lower end of the band (11 to 15) to stay away from it.
The pain of changing channels
Most hubs require re-pairing all devices when you change the Zigbee channel, because the channel is part of the network key negotiation. Exceptions:
- Zigbee2MQTT allows in-place channel change with most devices migrating automatically over several minutes
- Hubitat allows channel change with the same caveat
- Hue Bridge has a “channel change” function that attempts to move devices automatically, with about a 70% success rate. Devices that do not move have to be re-paired
- SmartThings, Echo, Aqara: full re-pair required
Plan a Saturday afternoon if you are changing the channel on a SmartThings setup. Document each room and device first.
Mesh routing across hubs
Different Zigbee networks do not share mesh routing. A device paired to your Hue Bridge cannot route through a SmartThings-paired plug. They are entirely separate networks even on the same channel.
This means each network needs its own router coverage. A common mistake is having one network with great mesh density and another network with sparse devices that depend on a few weak routes. The sparse network looks unreliable, and the user thinks the hub is bad when the actual problem is just lack of nearby routers.
When to consolidate
If you have three Zigbee networks running in the same home, consolidation is usually worth it. Pick a primary hub that supports the broadest range of devices (Hubitat and Home Assistant are the strongest here), migrate everything to it over a weekend, and turn off the other Zigbee radios.
Consolidation also gives you a single mesh, which means router density is shared. Twenty plugs spread across one network give you much better coverage than twenty plugs split three ways.
The exception: Hue lighting
One common reason to keep a separate Hue network is the Hue Bridge’s group call support. The Hue Bridge can turn on twenty bulbs in a single Zigbee command, which is why “all kitchen on” feels instantaneous. Other hubs send individual commands per bulb, which can result in a noticeable stagger across many lights.
If you have a lot of Hue bulbs and care about fast group response, keep the Hue Bridge as the bulb hub and consolidate everything else.
Verifying the fix
After changing channels, watch your device status pages for several days. The metrics to track:
- Number of “not responding” events per day
- Response time for typical commands
- Battery sensor reporting cadence (door sensors should report consistently every few minutes)
A successful channel separation usually shows up as a noticeable drop in not-responding events within a couple of days.
The negotiation no one initiates
If you live in an apartment building with thin walls, you are sharing Zigbee airspace with every neighbor who has any smart device. There is no formal coordination, so most apartments quietly run on the default channel of whatever hub they bought, which means several units in the same floor often share a channel.
If you spot persistent drops that do not trace to anything in your own setup, the cause is often a neighbor whose hub came up after yours and landed on the same channel. Moving your hub to a less-popular channel is the unilateral fix. The broader mesh stability advice in our mesh stability guide applies here too because router density matters more in shared RF environments.
The neighbor announcement habit
If you live in a multi-unit building and add a new Zigbee device, choose its channel intentionally rather than letting it default. Most hubs default to channel 15, which means every default install in your building is on the same channel. Picking 11 or 25 spreads the load. The same coordination logic applies to Wi-Fi channels which we cover in our Wi-Fi channel guide.
