Home Assistant Sees Your Amazon Thread Network—Why Can't It Use It?

The Direct Answer: Yes for Routing, Usually No for Direct Setup

Home Assistant can often use a supported Amazon Echo or eero to reach Matter-over-Thread devices—Matter accessories that use the low-power Thread radio—without a Connect ZBT-2. The Amazon device supplies the border-router path from Thread to the normal home network. Home Assistant supplies the Matter controller, meaning the system allowed to control the accessory, and runs its own automations.

The confusing part is the word use. Home Assistant can use an Echo to route traffic to a device that is already on the Amazon Thread network. It usually cannot use an unknown Amazon Thread password to put a factory-new device onto that network directly.

That difference explains the common Home Assistant screen: the Echo appears under Other networks, but there is no key icon and no useful Make preferred button. Home Assistant heard the Echo announce itself on the local network. The announcement did not include the password-like Thread credentials.

Three Jobs That Look Like One “Hub”

A Thread border router is like a small network router. It moves encrypted packets between low-power Thread devices and the normal home network. It does not decide what the light, lock, or sensor should do.

A Matter controller is the system allowed to control the accessory. Alexa and Home Assistant can both be Matter controllers for the same physical device. Thread credentials are the saved network name and password the setup phone needs when it places a new device onto the Thread mesh.

An Echo can perform the first two jobs, but that does not mean Home Assistant receives the third. Amazon documents a Credential Locker for approved product makers and smart-home skills, but it is restricted developer material, not a homeowner button for exporting the Echo's Thread key.

First Check the Exact Echo or eero Model

Amazon's Matter-controller list is much larger than its Thread-border-router list. A box can control Matter-over-Wi-Fi and still lack the radio needed for Matter-over-Thread. Check the exact generation before troubleshooting the network.

The Practical Echo Path: Alexa First, Then Home Assistant

Use this path when the exact Echo is on Amazon's Thread-border-router list and both Alexa and Home Assistant should control the accessory. With eero, first confirm the model is on eero's Thread and Matter-controller lists and link the eero and Amazon accounts to activate Alexa Matter control.

1. Update the basics. Update Home Assistant Core, the Matter Server app, the Home Assistant Companion app, Alexa, the Echo or eero, and the accessory's software (firmware) where the maker provides an update path.
2. Keep setup on one normal home network. Put the phone, Home Assistant, and Echo or eero on the same LAN. Avoid guest Wi-Fi and device-isolation settings. In Home Assistant, leave IPv6 on Automatic unless the network is deliberately managed another way.
3. Add the factory-new device in Alexa. Scan its Matter code in the Alexa app. Alexa uses Bluetooth for the nearby setup step and places a Thread accessory onto the Amazon Thread network.
4. Create a new sharing code. In Alexa, open Devices, select the Matter device, choose Other Assistants and Apps, then Add another. Copy the newly generated 11-digit code. Amazon says it expires after 15 minutes.
5. Add it as already in use. In the Home Assistant Companion app, go to Settings > Matter > Add device, choose Yes, it's already in use, and follow the prompts with the fresh code.
6. Test both paths, then choose one automation brain. Confirm Alexa and Home Assistant can each control or read the device. Put the real automation in Home Assistant if that is the household's main system; do not build the same routine twice.

The QR code printed on the accessory or box is for its first setup or a factory reset. After the device belongs to Alexa, use the fresh time-limited sharing code. Matter multi-admin gives Home Assistant a separate encrypted controller relationship; it is not a cloud import of the Alexa device.

Why the Amazon Network Can Stay Under “Other networks”

Home Assistant discovers border routers through local network announcements called mDNS or DNS-SD. Those announcements tell Home Assistant that an Amazon Thread route exists. They do not reveal its secret network key.

Home Assistant can label a Thread network preferred only when it knows the credentials. However, a preferred label is not required for ordinary control of a Matter device that Alexa already put on the mesh and then shared to Home Assistant. The Echo routes the packets; Home Assistant talks to the device over local IPv6, the addressing Matter uses inside the home.

In plain English: Other networks is a setup limitation, not proof that routing is impossible. Do not spend hours trying to turn an Amazon network into a Home Assistant-managed OpenThread router. They are different ownership models.

eero Is Similar, but Its Credential Path Is Different

eero's current Thread documentation says its app writes Thread credentials into the iOS keychain or Android credential store when Google Play Services is available. Other apps may read them with permission. FireOS does not support this mobile-sharing feature. On a supported phone, it creates a possible direct-import path for the Home Assistant Companion app.

The caveat is important: Home Assistant's official copy-and-join instructions explicitly walk through Apple-created credentials on iPhone and Google-created credentials on Android. They do not promise that every eero app, phone version, and Home Assistant release will hand off the key correctly.

If the eero network appears in Home Assistant with a key icon, Home Assistant has its saved Thread network details—but the setup phone currently chooses which Thread network receives a new device. Confirm the eero credentials are also present and selected on that phone before testing direct setup with one inexpensive device. If the key is missing from either place, use Alexa-first sharing instead of repeatedly resetting the network.

Linking eero and Amazon accounts is required when eero will act as Alexa's Matter controller. It is optional when eero merely carries Thread traffic for a different controller or direct mobile credential sharing works. eero says the link may share Wi-Fi names and passwords plus Thread identifiers, passwords, and keys so supported Echo and eero products can form one Amazon-managed mesh. Use the Alexa route only if the household accepts that account relationship.

What Stays Local, and What Still Uses the Cloud?

This is why “local” needs a complete sentence. Standard Home Assistant Matter commands and automations can be local after setup while the Alexa experience and setup layer remain account-based. Test an internet outage before relying on an automation, and keep physical keys, local alarms, and manufacturer-approved safety controls for locks, leaks, heating, and other critical jobs.

Matter and HomeKit Are Not the Same Path

A Matter-over-Thread accessory can belong to Alexa, Home Assistant, Apple Home, Google Home, and SmartThings through Matter multi-admin when the exact device and platforms support its device type. Sharing control does not copy automations or merge Thread networks.

A HomeKit-over-Thread accessory is different. It uses Apple's HomeKit protocol over the Thread radio and may not support Matter at all. An Echo does not convert a HomeKit-only accessory into Matter. Use Apple Home or Home Assistant's HomeKit Device integration with the correct Thread credentials for that product.

Before buying, look for the actual Matter logo, not only a Thread logo or “works with Alexa” text. A Thread radio is the road; Matter or HomeKit is the language spoken on it.

If Alexa Sharing Still Times Out

1. Verify the exact border router. An ordinary Echo Dot 5th Gen or Echo Pop is not enough. Match the device to Amazon's current Thread list.
2. Confirm it is a native Matter device. A product connected through an Alexa cloud skill does not automatically have Other Assistants and Apps or a Matter sharing code.
3. Generate a new code. Do not reuse the box QR code. Start a fresh 15-minute sharing window in Alexa and immediately continue in the Home Assistant Companion app.
4. Check local IPv6. Home Assistant says ISP-provided IPv6 is not required, but IPv6 must work on the local network. Use bridged networking for a Home Assistant virtual machine so it receives the local routing announcements.
5. Remove isolation during setup. Keep the phone, Echo or eero, and Home Assistant on the same simple LAN. Guest networks, client isolation, blocked multicast, and strict VLAN rules commonly stop discovery.
6. Use the supported Home Assistant stack. Home Assistant OS with the Matter Server app is the supported route. The June 2026 Matter Server 9 upgrade moved Home Assistant to matter.js and Matter 1.5.1.
7. Download Matter diagnostics before resetting. In the Matter integration, open the device's menu and download diagnostics. That gives a useful record if a GitHub issue or forum post is needed.
8. Reset one accessory last. Do not delete Home Assistant's Thread storage, regenerate the whole eero network, or reset every Echo because one sharing attempt failed.

When You Should Buy Connect ZBT-2

Do not buy ZBT-2 merely because the Amazon network sits under Other networks. If Alexa-first sharing works and local Home Assistant control is stable, the Echo or eero is already doing the radio job.

Use a dedicated ZBT-2 in Thread mode when any of these are true:

• None of the Echo or eero models in the house is on the current Thread-border-router list.
• You want Home Assistant-first commissioning without an Alexa account or Alexa-first setup.
• You want Home Assistant to store the Thread credentials, run and diagnose its OpenThread border router, and migrate the radio through Home Assistant's supported flow.
• The Amazon sharing path is unreliable on the exact accessory and you want a documented Home Assistant route.
• You are starting a larger Home Assistant-first Thread rollout and want one clear owner before pairing dozens of devices.

Remember the two catches. Connect ZBT-2 must be dedicated to either Zigbee or Thread. And a new ha-thread network does not automatically merge with Amazon's network. If Amazon credentials cannot be imported, moving existing devices may require a planned reset and recommissioning.

Tara's Recommendation

If a compatible Echo—or an eero linked to Amazon and confirmed for both Thread and Matter control—already runs the home, keep the hardware you have. Pair each new device in Alexa, share it to Home Assistant with a fresh code, keep the automations in Home Assistant, and verify local control during an internet outage.

For a fresh Home Assistant-first home, use Connect ZBT-2 in Thread mode or another supported Home Assistant OpenThread path. Home Assistant Yellow's built-in radio uses Zigbee by default; switching it to Thread installs Thread-only firmware, so migrate existing Zigbee devices to another adapter or use a separate Thread adapter first. This ownership model avoids making Alexa the admission desk for every new Thread device.

For an eero household, check whether the setup phone and Home Assistant actually receive the mobile-shared credentials before choosing. A visible key icon in Home Assistant is only half the check. Whichever route wins, document the Thread owner, setup phone, Matter codes, and where automations live.

Frequently Asked Questions

Can Home Assistant use an Amazon Echo as a Thread border router without ZBT-2?

Often, yes. The exact Echo must include a Thread border router, the device must be on that Thread mesh, and Alexa must successfully share it to Home Assistant as another Matter controller. Echo and accessory combinations can still time out; if a fresh sharing code plus the IPv6, multicast, and simple-LAN checks above do not fix it, use a supported Home Assistant Thread route such as ZBT-2.

Why does the Amazon Thread network appear under Other networks?

Home Assistant discovered the Echo's border-router announcement but did not receive its Thread credentials. Discovery proves the route exists. It does not reveal the password.

Can I make an Echo Thread network preferred in Home Assistant?

Only when Home Assistant knows the credentials. Amazon does not document a homeowner export button for an Echo-created Thread key, so Alexa-first setup and Matter sharing are usually more reliable than trying to promote the network.

Is Echo Dot 5th Gen a Thread border router?

No. It can be a Matter controller, but it is not on Amazon's current Thread-border-router list. The 2025 Echo Dot Max is on the list; ordinary Echo Dot generations are not.

Is control still local through Echo or eero?

Standard Home Assistant Matter commands and automations can remain local after commissioning, and the border router forwards encrypted local traffic. Alexa voice, remote access, account setup, eero administration, firmware updates, and vendor-only features are not fully cloud-free.

Can one Connect ZBT-2 run Zigbee and Thread together?

No. Home Assistant says ZBT-2 must be dedicated to Zigbee or Thread. Use separate radios if the home needs both.

Related Tara Guides

Compare all major platforms in Tara's 2026 Thread border-router guide. Follow the full Matter multi-admin guide for two-app control. If Home Assistant reports missing Thread hardware, use the border-router error checklist. If coverage is weak, learn how to extend one Thread mesh without creating another.