Home Assistant ZBT-2 vs ZBT-1: buy, keep, or migrate in 2026?

Some links on this site may be affiliate links. As an Amazon Associate I earn from qualifying purchases. How this works.

The Home Assistant Connect ZBT-2 has a clear job: connect Zigbee devices or provide a Thread radio for a Home Assistant setup. At a $49 US recommended MSRP on the manufacturer’s page, it is a reasonable starting point for a new network. For an existing network that already works, my recommendation is less exciting: keep your current coordinator until you can name the problem an upgrade will solve.

This matters because buying the newer radio doesn’t automatically fix a sparse mesh, interference from USB 3.0 equipment, awkward router placement, or a device that has poor compatibility with your integration. And it doesn’t give you Zigbee and Thread at the same time. Those two misunderstandings are behind a surprising amount of unnecessary shopping.

Evidence checked 23 October 2026. This is a documentation-based buying and migration guide, not a hands-on product review. We did not test radio range, latency, reliability, battery life or migration success on our own network. Home Assistant’s $49 is a recommended US MSRP, not a confirmed in-stock checkout price. Community reports below are useful questions to investigate, not laboratory measurements.

The buying decision, without the protocol maze

Your starting point	What I would do	Why
New Home Assistant setup; Zigbee sensors or buttons planned	Consider one ZBT-2 dedicated to Zigbee	Home Assistant recommends it for new Zigbee networks and maintains the official firmware.
ZBT-1 / SkyConnect works reliably	Keep it	ZBT-1 production ended, but Home Assistant says software support continues.
Existing Sonoff, ConBee or another Zigbee coordinator works reliably	Keep it, check support before replacing	Moving a network takes preparation; a different antenna is not guaranteed to improve your house.
Need Zigbee and Matter-over-Thread devices	Plan separate radios or an existing compatible Thread border router	A single ZBT-2 cannot operate both networks together.
Home Assistant server is far from the best radio location	Consider coordinator placement first; evaluate a supported network-attached alternative	ZBT-2 is a USB device, not a built-in PoE/Ethernet coordinator.
Buying because the spec sheet says “4× faster”	Don’t use that as a speed promise	The cited fourfold difference is the adapter’s serial baud rate, not fourfold automation speed.

For choosing the computer underneath Home Assistant, see our Green vs Raspberry Pi 5 vs mini PC guide. This guide is about the radio, not the host. They’re separate purchases and problems.

What actually changed from ZBT-1 to ZBT-2?

The old Connect ZBT-1, originally called SkyConnect, used a Silicon Labs MG21 Zigbee/Thread chip and an internal antenna. The ZBT-2 uses an MG24 chip and a larger external antenna and base. Home Assistant lists 115,200 baud for ZBT-1 and 460,800 baud for ZBT-2 on the USB-to-radio side. The newer adapter includes an ESP32-S3 as a USB-serial bridge and a 1.5 m USB-C cable for placement away from a computer. These are manufacturer specifications, not measurements from Considered Gear. Official product specifications and comparison.

Home Assistant says its own testing found improvements in responsiveness. That is worth noting, but it isn’t a matched, independently repeated result for your devices, house, firmware or integration. More baud rate doesn’t make a battery sensor wake up four times as often or guarantee four times the radio range. The developer’s November 19, 2025 launch explanation specifically distinguishes adapter speed from fourfold device response time.

ZBT-1 is not obsolete in the sense that it suddenly stops working. Home Assistant has ended production of ZBT-1 but explicitly says its software support continues. If a working ZBT-1 already reaches your devices, swapping it is a choice, not a maintenance requirement. Home Assistant launch notes.

One adapter, one radio protocol at a time

Zigbee and Thread both commonly operate at 2.4 GHz, but they are not interchangeable networks. Matter is a smart-home application standard that can use Thread or Wi-Fi. ZBT-2 can be set up for Zigbee or Thread; it cannot reliably run both simultaneously. Home Assistant explicitly decided not to implement a simultaneous multiprotocol mode on ZBT-2, citing stability issues observed with earlier testing. ZBT-2 FAQ.

If your house contains Zigbee buttons plus Thread-based Matter devices, don’t order one ZBT-2 believing it replaces every radio. You might use your current Zigbee coordinator and a separate Thread radio, or use a compatible Thread border router that is already in the house. If your Matter devices are Wi-Fi devices, a new Thread USB radio may not be needed for those devices at all. The Home Assistant Thread integration documentation explains the network setup and requirements.

That also answers a common follow-up: ZBT-2 is not a standalone Thread border router you can plug into power and put anywhere. It supplies the radio within a supported Home Assistant/OpenThread Border Router configuration. Home Assistant’s product FAQ says standalone border-router operation independent of Home Assistant is not built in. Check your installation type and the OpenThread Border Router setup before buying specifically for Thread.

ZHA or Zigbee2MQTT changes the migration plan

A new radio does not require changing Zigbee software. ZHA and Zigbee2MQTT are different ways to operate a Zigbee network, and their backup and migration procedures are not the same. Replacing a coordinator is not the moment to casually change from one integration to the other.

For a current ZHA network: Home Assistant documents network backups and a migration flow under Settings → Connectivity → Zigbee → Migrate. Its instructions cover supported migrations across Silicon Labs, Texas Instruments and ConBee/RaspBee families, with prerequisites for the old coordinator and particular ConBee firmware. The official sequence creates a backup, connects the new adapter, selects migration, and offers automatic or advanced backup selection. Devices may take time to rejoin; some may need power cycling. Read the current ZHA migration steps on your installed version before touching the live network.

For Zigbee2MQTT: Do not assume the ZHA wizard applies. Zigbee2MQTT’s FAQ says backup-and-restore support is currently implemented for zstack and ember adapters; moving between families can be more difficult and re-pairing may be required. Its Silicon Labs adapter documentation lists the ZBT-2 under adapter: ember, with 460800 baud and hardware flow control (rtscts: true). Those are configuration-reference values, not instructions to paste blindly over a functioning installation. Check the adapter firmware and latest docs first. See the Zigbee2MQTT migration FAQ and EmberZNet adapter guide.

For Thread, use Home Assistant’s Thread migration instructions rather than a Zigbee backup tutorial. It notes that Thread network information is managed by Home Assistant, not simply stored on a replaceable USB radio. Verify your host installation, selected firmware, and OpenThread Border Router configuration first.

The migration checklist that saves a weekend

1. Write down the current setup. Is it ZHA or Zigbee2MQTT? Which radio, firmware, network channel, host and USB path does it use? Count devices so you can check them afterward.
2. Make recoverable backups. For ZHA, follow its coordinator/network backup procedure as well as your usual Home Assistant backup. For Zigbee2MQTT, preserve its configuration and coordinator backup if supported. Copy them off the host and make sure you can access them. A whole-Home-Assistant backup is not proof that every Zigbee adapter can restore its network.
3. Check the compatibility route before disconnecting anything. Confirm source/target adapter family, firmware and the migration path in the relevant project’s documentation. If the path is unsupported, budget for re-pairing rather than guessing that it will all transfer.
4. Place the new radio properly. Avoid jamming a 2.4 GHz coordinator beside USB 3.0 devices, drives and a metal server chassis. Home Assistant recommends a USB extension cable and a USB 2.0 port or powered USB 2.0 hub for interference avoidance. Radio placement can matter more than a feature sheet.
5. Follow one migration procedure, then verify. Check battery sensors, mains-powered routers, automations, bound switches, and any devices in distant rooms. Allow time for routing and joining. Don’t conclude success just because the adapter appears in a dashboard.
6. Keep the old adapter available. Do not reset, sell or overwrite your old setup until the new network is stable and fresh backups are possible. A rollback might require more than plugging in the old stick if you changed network parameters.

The steps above are a planning checklist, not a universal firmware flashing recipe. In particular, don’t borrow firmware versions from an old forum post: a workaround reported in late 2025 may no longer be relevant in October 2026.

When the new dongle won’t fix the problem

A coordinator sees only one part of a mesh. Home Assistant’s ZHA documentation explains that mains-powered Zigbee router devices can help extend coverage and capacity. If a far-away battery sensor keeps disappearing, placement, router availability, and interference deserve attention before the coordinator goes into a shopping cart.

For a USB-connected ZBT-2, the supplied cable helps you move its antenna away from noisy ports or a cramped rack. That is useful if the computer lives in a cabinet. But it is still USB-connected. If the ideal radio location is on the other side of a house, evaluate the support and maintenance tradeoffs of a network-attached coordinator instead. Do not treat Ethernet or PoE as inherently better radio performance; they are ways to place a coordinator where it belongs. Home Assistant’s official product FAQ says ZBT-2 has no built-in PoE and currently no announced PoE edition.

Likewise, buying a ZBT-2 will not make a Zigbee-only sensor into a Matter/Thread sensor. If your real decision is which new smart-home protocol to invest in, begin with our Zigbee, Thread, Matter and Wi-Fi explainer before choosing hardware.

The owner reports are mixed—and that’s useful

The discussion has lasted longer than the launch announcement. Hackster.io’s November 2025 coverage independently summarized the one-protocol limit while identifying the higher serial throughput as a manufacturer claim, not a fourfold real-world speed benchmark. Matter Alpha’s November 2025 hands-on account describes a straightforward setup on Home Assistant OS but also notes that virtual machines can require additional USB setup. Those findings are theirs, not testing we performed.

A November 23, 2025 Home Assistant Reddit thread asked why owners with reliable Zigbee networks should replace their coordinators at all. A February 28, 2026 follow-up included people reporting both improvement and little change, along with some migration friction. A September 10, 2026 buyer question showed the recurring Zigbee-versus-Matter confusion: one purchased radio, two different device types. These are dated discussions and self-selected anecdotes, not population-wide failure rates or benchmark results. They are evidence of the questions buyers keep asking.

What I’d actually buy

New Zigbee-only Home Assistant setup: I’d put the ZBT-2 on the shortlist because it’s official, Home Assistant maintains its firmware, and it has a straightforward ZHA setup path. Check local availability, taxes and shipping rather than treating the stated MSRP as a guaranteed offer.

Existing reliable ZBT-1 or third-party coordinator: I’d leave it connected. Home Assistant continues ZBT-1 software support, and a working mesh already has something more valuable than an attractive benchmark: devices that respond. Put the money toward a real coverage or reliability problem, if one exists.

Mixed Zigbee and Thread plans: I’d inventory the actual devices and existing border routers first. Then I would dedicate a radio to each required network rather than experimenting with multiprotocol on a controller that stores important home automations.

Remote rack or complex virtualized host: I’d choose where the radio should physically live, then choose the adapter connection. Don’t force a USB-only radio into the wrong location just because it is the official recommendation for new ZHA networks.

If you decide to shop, compare Zigbee coordinator families and their firmware support—not just their antennas. Check the exact chipset, ZHA or Zigbee2MQTT compatibility, return conditions and whether you actually need Thread. There is an optional category search below; it is not a verified offer or a recommendation to replace a working coordinator.

The best upgrade is the one that fixes an identified problem. If the lights respond, the buttons work, and your backups are sound, you can keep the radio you own.

Sources and what has not been measured

Primary documents checked 23 October 2026: ZBT-2 specifications and FAQ; November 19, 2025 ZBT-2 release announcement; Home Assistant ZHA documentation; Home Assistant Thread documentation; Zigbee2MQTT migration FAQ; Zigbee2MQTT EmberZNet adapters; Hackster.io product reporting; Matter Alpha first-hand account.

No hardware was provided or tested for this guide. We did not independently measure radio signal, USB response speed, batteries, device rejoin success, energy use, genuine retail stock, reader search volume, rankings, clicks or affiliate revenue. Check current documentation and product options before buying; firmware, integrations and retailer inventory may change.