Can Zigbee and Thread Share One USB Gateway?
Can Zigbee and Thread Share One USB Gateway?
You already have Zigbee door sensors and switches at home, and you’re preparing to add Matter over Thread devices. When shopping for a USB adapter, it’s easy to see a chip described as “supporting Zigbee, Thread, and multiple protocols” and conclude that one adapter is enough.
Three capabilities need to be distinguished: the hardware can run both protocols; the firmware lets you switch between them; and a running system can serve both networks at the same time.
These are not the same promise. Whether sharing is worthwhile depends on how the specific adapter, firmware, and platform support it.
This article uses Home Assistant’s official documentation and Connect ZBT-1 as examples. It does not represent every multiprotocol product, and no throughput, latency, or stability tests were performed.
A Chip Supporting Both Protocols Does Not Mean Both Work at Once
Home Assistant’s Thread documentation explains that Thread and Zigbee use the same IEEE 802.15.4 radio technology, but Thread provides IP network connectivity. Thread itself does not define how to control a light or sensor; it also needs an application-layer protocol such as Matter or HomeKit.[1]
A shared radio foundation gives compatible chips the potential to run different protocols, but it does not automatically put devices using those protocols on the same network.
A Zigbee sensor does not become a Thread device simply because a Thread border router is nearby. An existing Zigbee network still needs an appropriate coordinator and software support.
Before buying, clarify each of these claims separately:
| Product description | What else needs to be confirmed |
|---|---|
| Supports Zigbee and Thread | Does it require choosing between different firmware, or can both run simultaneously? |
| Supports multiple protocols | Which firmware and platform does this refer to, and is the feature still experimental? |
| Supports Matter | Does this mean it is a controller or bridge, provides Thread networking, or is itself a Matter device? |
The wireless chip’s name alone cannot tell you what the complete system will be able to do.
Connect ZBT-1’s Official Position Is Clear
Home Assistant Connect ZBT-1 was formerly called SkyConnect. The official product page says the two have identical hardware and capabilities, and lists the status of multiprotocol support.[2]
As of the review for this article, the official page still labels the multiprotocol firmware that lets one radio connect to Zigbee and Thread simultaneously as experimental and does not recommend using it. The documentation explains that although it works in some cases, technical limitations identified during testing lead to a worse user experience. The focus is therefore on dedicated Zigbee and Thread firmware.[2]
This supports a specific conclusion: if you are building an everyday system according to the official ZBT-1 recommendation, you should not treat running both networks on one radio as the default approach.
It does not support the broader claim that no chip or platform can ever run multiple protocols reliably. Other solutions must be judged by their own hardware and maintenance status; one product page cannot settle the question for an entire industry.
The product page also notes that ZBT-1 has been discontinued, continues to receive software updates, and points to a successor product. It is used here to explain the technical choice, not to recommend buying an older model.
Flashing It with Thread Firmware Does Not Add a Feature to Your Existing Zigbee Network
With a dedicated-firmware setup that requires choosing one protocol, switching to Thread means assigning that radio a different job. Your existing Zigbee devices still need a Zigbee network; flashing the adapter with Thread firmware does not migrate them automatically.
If the adapter currently serves as your home’s Zigbee coordinator, stopping its service and then flashing its firmware may affect control of your existing devices. Before replacing it, check your platform’s backup and migration procedures and whether the target coordinator supports the required recovery method.
Do not assume all Zigbee adapters are interchangeable without disruption, or equate an ordinary Home Assistant backup file with a verified wireless-network migration procedure. For more on what backups cover, see the difference between a successful backup and a successful restore.
If you only want to try one new Thread device, changing an otherwise stable Zigbee network first will usually broaden the scope of troubleshooting.
One Host Can Manage Both Networks Without Using One Radio
A useful distinction is between “managed by the same Home Assistant instance” and “handled by the same radio.”
A dedicated adapter can continue serving Zigbee while another supported Thread border router provides Thread connectivity. Devices on both networks can still participate in Home Assistant automations; their underlying networks simply remain separate.
A Thread border router does not have to be a USB device plugged into the Home Assistant host. The official documentation lists third-party border routers and explains that Home Assistant can use the network connectivity they provide. The specifics of commissioning still depend on the device’s application-layer protocol and conditions involving the phone, among other factors.[1]
Nor does having a speaker with Thread automatically mean everything is ready. You still need to check the Thread network credentials, phone commissioning requirements, Matter controller, and network reachability between the device and controller.
If you already have multiple Thread border routers, you also need to determine whether they belong to the same Thread network. For more on that, see how multiple border routers relate to networks and redundancy.
Separate Radios Do Not Automatically Eliminate Wireless Problems
Dedicated radios can reduce the complexity of asking one device to fill multiple roles, but two adapters still operate in a real wireless environment.
The official Connect ZBT-1 page specifically explains why it includes a USB extension cable: noise near USB 3.0 devices or ports can interfere with 2.4 GHz wireless devices, including Zigbee and Thread. Symptoms may include pairing failures, disconnections, or timeouts.[2]
So if things become unstable after adding an adapter, do not immediately conclude that the protocols are incompatible. Check placement, connections, and power first, then troubleshoot the wireless environment according to each platform’s documentation. This article did not measure channel occupancy and does not prescribe channel combinations or separation distances for every home.
It is also unwise to replace an adapter, change firmware, change channels, and migrate a network all in one adjustment. Changing one thing at a time makes it easier to identify what caused an improvement or regression.
Inventory the Roles Before Deciding Whether to Add Hardware
Start by listing your devices: what manages Zigbee, what provides Thread border routing, what serves as the Matter controller, and which connection method the device you plan to add actually uses.
If an existing device already provides suitable Thread networking, you may not need another USB adapter. If that capability is missing, evaluate dedicated options supported by your current platform instead of buying based solely on the words “multiprotocol.”
For acceptance checks, verify separately that existing Zigbee devices remain controllable, the new Thread device can be commissioned and used, the system recovers after relevant components restart, and you can return to the previous configuration if something goes wrong. These are suggested checks, not results of tests already performed.
Saving a USB port certainly has value. But when one adapter takes on a core role in two networks, the costs of configuration, troubleshooting, and recovery also matter. The answer should come from what the complete system supports.
References
Reviewed on November 11, 2026. The Home Assistant documentation page showed version 2026.11.1.
- Home Assistant: Thread, covering the differences between Thread and Zigbee, the border router’s role, third-party devices, and commissioning prerequisites.
- Home Assistant: Connect ZBT-1, covering dedicated firmware, the experimental status of multiprotocol support, USB interference, and product maintenance status.
AI-generated concept illustration, not a test photograph or network topology diagram.
Discussion
Share a question or your experience. Comments appear after moderation. Your email is never displayed publicly. Comment privacy
Loading comments…