How to add Zigbee without replacing your router

Most people don’t need to replace their router to add Zigbee to their smart home. That’s a myth pushed by companies selling expensive all-in-one hubs. You likely already have everything you need.

Plug a USB Zigbee coordinator into the machine running Home Assistant - the Sonoff dongle is cheap and works, the Connect ZBT-2 is the official pick - put it on a USB extension cable, and add a mains-powered plug or two to extend the mesh. You don’t need a new router.

Why Zigbee is worth adding

Zigbee runs in the 2.4 GHz band, separate from your home’s Wi-Fi traffic, and Zigbee devices form their own mesh - they relay messages for each other to extend range without any cloud dependency. (Because Zigbee shares the 2.4 GHz band with Wi-Fi, it’s worth keeping your Zigbee channel and your Wi-Fi channels apart to avoid interference, but it doesn’t run on your router.)

For Home Assistant users, Zigbee means local control. Your automations keep running even when the internet goes down - which is the whole point of a local-first setup.

The trade-offs? Zigbee devices need a coordinator (the radio that runs the network), and that coordinator should sit somewhere reasonably central. Range can be a challenge in larger homes, but the mesh helps a lot.

The simplest path: USB Zigbee coordinator

The easiest way to add Zigbee without touching your router is a USB coordinator dongle plugged into the machine running Home Assistant. This is what most Home Assistant setups do.

The Sonoff Zigbee 3.0 USB Dongle Plus is the budget pick - cheap and well supported in both ZHA (Zigbee Home Automation) and Zigbee2MQTT. I haven’t run this one; the pick rests on the spec sheet and other owners’ write-ups. For the full field, see the best Zigbee coordinators for Home Assistant. Sonoff makes it in two variants, a “P” model (Texas Instruments chip) and an “E” model (Silicon Labs chip); both are common, so check which firmware your setup expects.

The Home Assistant Connect ZBT-1 is Home Assistant’s own official coordinator. It supports Zigbee and is Thread-capable, which makes it a good choice if you also plan to use Matter-over-Thread devices down the road. It runs one of those at a time, though: the stick takes either the Zigbee firmware or the Thread firmware, so a Zigbee coordinator and a Thread border router running at once means two radios. It has since been succeeded by the Connect ZBT-2; the ZBT-1 is discontinued but still supported, so new buyers should pick the ZBT-2.

For a coordinator you can place anywhere on your network (not just next to the server), look at the SMLIGHT SLZB-06 family - these are Zigbee coordinators that connect over Ethernet or Wi-Fi/PoE, letting you mount the radio in a central spot away from interference. For more on where to put it, see Zigbee coordinator placement for large houses and Zigbee channel selection and Wi-Fi interference.

If you’re running Home Assistant on a small device like a Raspberry Pi, placement matters. USB 3.0 ports and SSDs emit 2.4 GHz noise, so use a short USB extension cable to get the dongle a foot or two away from the host. That one cheap cable fixes most “Zigbee is flaky” complaints.

Alternative: dedicated Zigbee hub

If you’d rather not deal with USB dongles, a dedicated Zigbee hub connects to your existing network over Ethernet or Wi-Fi and bridges devices to Home Assistant.

The Philips Hue Bridge is the most common entry point. It integrates cleanly with Home Assistant over its local API, but it’s really designed around Hue and Friends-of-Hue devices.

The Aqara hubs support Aqara’s sensors and offer some local control, and the SONOFF iHost is a more open hub that can run Zigbee alongside other tooling.

The trade-off with any dedicated hub is that you’re adding another box to your network. A USB coordinator plugged straight into your Home Assistant host is simpler and has lower latency.

Extending range

The most common real-world limit is range. If your coordinator is far from a device, you’ll get dropouts.

For most homes the mesh solves this, because mains-powered Zigbee devices act as routers (repeaters) and extend the mesh, while battery-powered devices are end devices that only talk to their parent and do not relay traffic for others. So to fill a dead zone, add a mains-powered device - a smart plug, an in-wall switch, or a powered bulb - in that area, and it strengthens the mesh for everything nearby. Adding more battery sensors does not extend range.

A simple Zigbee smart plug (Third Reality, Sonoff, Innr, and others) is a cheap, effective repeater for a dead zone. For very large homes you can run a coordinator placed centrally over Ethernet (like the SLZB-06 mentioned above) rather than trying to run two separate Zigbee networks.

What about Hubitat or HomeKit?

If you’re not using Home Assistant, the options differ.

Hubitat Elevation users (the Hubitat Elevation C-8 and the standard C-8 Pro that replaced it) have built-in Zigbee and Z-Wave radios - no dongle needed, though you’re on Hubitat’s platform rather than Home Assistant’s. The exception is Hubitat’s Thread Special Edition of the Pro: its Thread radio replaces the Zigbee one, so it cannot pair Zigbee devices at all.

HomeKit has fewer native local options. The Hue Bridge is the cleanest path for HomeKit-exposed Zigbee lighting; Aqara hubs work but lean on the cloud for some features. There’s no tidy “add Zigbee to your existing router” story in pure HomeKit.