Home Assistant SkyConnect was renamed Connect ZBT-1 with the same hardware, capabilities and support. ZBT-1 is now discontinued and succeeded by Connect ZBT-2. Existing working owners should check support and their actual unmet need before replacing a stable coordinator; a rename alone is not an upgrade.

Which name and generation?

Name on an offer/device What it identifies Decision
SkyConnect Original hardware renamed ZBT-1 Follow ZBT-1 documentation, not ZBT-2 hardware specifications
Connect ZBT-1 Same first-generation platform Discontinued sales do not mean automatic loss of existing support
Connect ZBT-2 Current successor with different radio/antenna hardware Evaluate the new generation only against a real requirement

The official rename announcement establishes the same-hardware relationship. The current ZBT-2 reference and FAQ establish the successor/discontinued context. Current ZHA documentation still lists supported ZBT-1/SkyConnect adapters.

One adapter, one selected protocol

Choose a dedicated Zigbee or Thread role with the supported firmware and setup. Home Assistant’s current FAQ says simultaneous Zigbee/Thread multiprotocol operation was inconsistent and is not its recommended home arrangement. A compatible radio is not a universal Matter gateway: Matter controller setup, Thread border-router/network credentials where relevant, and device compatibility are separate requirements. Matter over Wi-Fi is not the same radio requirement as Matter over Thread.

Existing-owner versus new-buyer checklist

Situation First action Avoid
Stable ZBT-1 Zigbee network Confirm supported firmware/backend and identify a specific unmet need Replacing it solely for the new name
New Zigbee network Check current supported coordinator and exact device compatibility A marketplace “SkyConnect” search treated as a current-generation offer
Move an existing ZHA network Take a current Home Assistant backup and the ZHA network backup; follow the adapter migration procedure Assuming a physical USB swap completes every migration
Zigbee2MQTT or another backend Use that backend’s exact documented adapter/backup procedure Applying ZHA migration steps without checking support
Add Thread while retaining Zigbee Plan a supported separate radio/network arrangement and credentials Assuming the existing Zigbee coordinator does both simultaneously

ZHA’s migration documentation covers supported adapter families and backup requirements. A ZHA backup is not a generic export for every backend, and a Thread network is a separate migration. Preserve credentials and backups privately; do not publish their contents as troubleshooting evidence.

A compatibility record before checkout

Record your Home Assistant installation type/version, backend, current adapter and firmware, exact devices, chosen protocol, backup date and the applicable migration page. Check that the receiver/USB placement follows the radio documentation. Resolve missing fields before disturbing a working network.

The existing tagged SkyConnect Amazon search is retained and remains a generation-check search, not verification that every result is the same adapter or that the original hardware is the best new purchase. Confirm exact generation, condition, included cable and support. We did not compare radio range, network stability or device responsiveness in-house.

Official references checked 1 October 2026. Use this as a documented compatibility decision, with no promised universal pairing, zero-effort migration or measured upgrade benefit.