Short Answer: Thread 1.4 Can Prevent Another Network, Not Magically Merge Two
Do not reset a working Thread home just because Home Assistant shows two networks. Thread 1.4 introduces secure credential sharing: one compatible border router can briefly produce a one-time administration code, and another compatible router can use it to join the same password-protected mesh. That helps a new router avoid creating an unnecessary second network.
It does not pour two existing meshes into one. Devices already joined to the old credentials stay there until a supported network-migration tool moves them or you reset and add them again. Matter multi-admin is separate: it lets Home Assistant, Apple Home, Google Home, Alexa, or SmartThings control the same Matter device, but it does not change that device's Thread network.
As of July 16, 2026, Home Assistant's OpenThread Border Router supports Thread 1.4, but Home Assistant's own documentation still warns that different vendors commonly form separate networks and that the phone's preferred credentials can decide where a new Matter-over-Thread device lands. The safe plan is one chosen mesh, one supported joining path, and resets only for devices that truly cannot migrate.
The plain-English rule: Thread 1.4 can hand a new router the key to an existing neighborhood. It does not move houses that were built in another neighborhood.
Three Layers That Look Like One Smart Home
The words around Matter and Thread are easy to blur together. Keeping these three jobs separate makes the setup much less mysterious.
- The Thread mesh is the local radio network. Its credentials include a network key, channel, and identifiers. A battery sensor joins one mesh at a time.
- A Thread border router connects that mesh to Ethernet or Wi-Fi. Home Assistant Connect ZBT-2, HomePod mini, Nest Hub, Echo Hub, Aeotec Smart Home Hub 2, and DIRIGERA are examples. A border router carries packets; it is not automatically the device's controller.
- A Matter controller gives commands. Home Assistant, Apple Home, Google Home, Alexa, and SmartThings each create their own trusted Matter group, called a fabric. One Matter device can trust several fabrics through multi-admin while staying on one Thread mesh.
Apple HomeKit is another control protocol. A HomeKit-over-Thread accessory can use the same radio technology as a Matter-over-Thread accessory, but HomeKit pairing does not turn it into Matter. Likewise, Home Assistant's HomeKit Device and HomeKit Bridge connection methods do not merge Thread credentials.
What Thread 1.4 Actually Changed
The Thread Group designed Thread 1.4 credential sharing for the moment when a phone or installer can see an existing network but cannot obtain its private credentials. A compatible border router can open a short, authenticated sharing session and show a nine-digit Thread Administration One-Time Passcode. The receiving app derives a temporary security key, securely retrieves the complete bundle of network password and settings—called the operational dataset—and can give it to another router or device.
This is not silent background merging. The router must advertise support, the owner must authenticate, the sharing session expires, and the receiving app must implement the flow. A product can run Thread 1.4 while its current homeowner app exposes only part of that capability.
The nine-digit administration code is also not a Matter code. A Matter setup or multi-admin code grants a controller access to one device. The Thread administration code grants temporary access to the mesh credentials. Do not post either one in screenshots, support threads, or a public password manager.
What the Major Platforms Officially Support in July 2026
This table separates published support from community experiments. “Thread 1.4” means the platform or product explicitly documents that version; it does not promise automatic cross-vendor convergence.
| Platform and concrete examples | Official support boundary | Local control and cloud dependency | Matter, HomeKit, and Home Assistant path | Main caveat |
|---|---|---|---|---|
| Home Assistant Yellow, Connect ZBT-1, or Connect ZBT-2 dedicated to Thread |
Home Assistant announced Thread 1.4 support in its updated OpenThread Border Router app on June 23, 2026. Home Assistant OS with the official Matter Server app—the Home Assistant software that talks to Matter devices—is the supported Matter setup. | Thread routing and normal Matter commands stay on the home network. Home Assistant Cloud is optional; remote access and outside voice services are separate choices. | Create a Home Assistant mesh, or use the documented phone-assisted import to join an Apple- or Google-created mesh. Share Matter devices separately with multi-admin. | The preferred-network feature is not complete. During phone setup, also called commissioning, the network saved as preferred on the phone can still override what the Home Assistant screen appears to prefer. |
| Apple Home HomePod mini, HomePod (2nd gen), Apple TV 4K (2nd gen), Apple TV 4K (3rd gen) Wi-Fi + Ethernet |
Apple officially lists these as Thread-enabled home hubs and supports compatible third-party border routers. Its homeowner documentation does not state a Thread version or promise a general Thread 1.4 merge button. | The Thread route and supported in-home Matter or HomeKit commands are local. Apple Account, iCloud Keychain, invitations, remote access, and some Home features use Apple services. | Home Assistant documents importing Apple Thread credentials with an iPhone, then joining its own OpenThread Border Router. Matter devices can be shared between Apple and Home Assistant; HomeKit-only devices follow HomeKit Device instead. | Do not infer Thread 1.4 credential-sharing support from a software version rumor. Use the Home Assistant flow Apple and Home Assistant actually document. |
| Google Home Nest Hub (2nd gen), Nest Hub Max, Nest Wifi Pro, Google TV Streamer (4K) |
Google documents a Thread Network SDK and new border-router management tools for a temporary credential-sharing key, called ePSKc. Its developer guide says apps must check whether the exact router exposes each capability. | Thread and supported in-home Matter traffic are local. Google Account, app setup, remote access, voice processing, and credential synchronization involve Google services. | Home Assistant officially supports importing a Google-created network with Android, making it preferred, and adding the Home Assistant border router to it. | A developer API is not proof that every Nest model exposes a homeowner-facing Thread 1.4 sharing screen today. Test the exact hub and phone path before changing the house. |
| Amazon Alexa and eero Echo (4th gen), Echo Hub, current Echo Show/Studio models, eero 6/7/Pro/Max/PoE families |
Amazon's official page updated May 1, 2026 lists these routers as Thread 1.1 or 1.3, not 1.4. Amazon also offers Credential Locker APIs to approved device makers. | The Thread radio transport is local. Alexa voice, routines, accounts, remote features, and the developer credential service depend on Amazon services, so do not assume every Alexa-driven automation survives a cloud outage. | Use Matter multi-admin to share a supported device with Home Assistant. Amazon does not document a homeowner workflow that exports an Echo or eero Thread mesh into Home Assistant. | Credential Locker is a restricted product-developer API, not a Home Assistant “download my Thread key” button. Do not assume Alexa/eero can join a mixed Thread 1.4 mesh yet. |
| SmartThings Aeotec Smart Home Hub 2; older SmartThings/Aeotec hubs vary |
Samsung's current Aeotec Smart Home Hub 2 product page explicitly lists Thread 1.4 and Matter 1.5. SmartThings also documents use of third-party border routers for some hub models. | Hub-connected Matter and SmartThings Edge work can run locally. Account setup, app management, remote access, notifications, and broader SmartThings services still use Samsung's cloud. | Share Matter devices between SmartThings and Home Assistant with multi-admin. Use only a SmartThings-documented credential or border-router joining flow for the radio mesh. | Thread 1.4 on the spec sheet does not prove that Aeotec Hub 2 can automatically absorb a Home Assistant, Apple, or Google mesh. The receiving and sending apps still need a common workflow. |
| IKEA DIRIGERA hub |
IKEA officially describes DIRIGERA as a Thread border router and Matter hub for its current system. Its public homeowner guide does not publish a universal Home Assistant credential-import procedure or a Thread version. | Basic supported control can remain inside the home. App accounts, remote access, connections to other services, and firmware—the device's internal software—may use internet services. | Pair native IKEA Matter-over-Thread devices in IKEA Home smart, then share each supported Matter device to Home Assistant; or pair them directly to Home Assistant without DIRIGERA. | Community users have joined DIRIGERA with a nine-digit Thread 1.4 passcode through advanced Home Assistant terminal commands. That is not the same as an official, durable homeowner workflow. |
The Safe Setup Order for One Home Assistant Mesh
- Inventory before changing anything. In Home Assistant, open Settings > Devices & services > Thread > Configure. Write down every network, which routers appear under it, and which network has a key icon. Discovery alone does not mean Home Assistant knows the credentials.
- Choose the target mesh. If a healthy Apple or Google network already carries working locks, sensors, and lights, keep it. For a new Home Assistant-first home, let Home Assistant create the first mesh with a dedicated Thread radio.
- Update and preserve recovery information. Update Home Assistant, the Matter Server app, the OpenThread Border Router app, phones, and hubs. Make a Home Assistant backup and privately save every device's permanent Matter QR or numeric code. Do not publish raw Thread datasets.
- Use the documented credential direction. For an Apple target, use an iPhone to send credentials to Home Assistant. For Google, use Android to import credentials. Make that network preferred, then install or configure Home Assistant's OpenThread Border Router so it joins instead of forming a second mesh.
- If Home Assistant owns the mesh, sync the phone. On Android, use Companion app > Troubleshooting > Sync Thread credentials. On iPhone, use Send credentials to phone from the Thread integration. A phone that knows another preferred network can commission the next device into the wrong mesh.
- Verify before removing anything. Refresh the Thread page and Matter Server network view. Confirm the new border router appears under the intended network, then test several powered and battery devices after a normal hub restart.
- Share controllers separately. If Apple Home, Google Home, Alexa, or SmartThings also needs control, generate a fresh Matter sharing code from the controller that already owns the device. This adds another controller; it does not alter Thread.
If You Already Have Two Thread Networks
First ask whether the two networks are actually causing a problem. Home Assistant can control Matter devices across more than one reachable Thread mesh because the border routers expose local IPv6 routes—the local network addresses Thread uses. Separate meshes lose the coverage and failover benefits of one dense mesh, but they do not automatically make device control invalid.
If you want one network, choose the survivor. Add compatible border routers to that mesh through an official import, join, or one-time-passcode flow. Then move end devices one at a time. A border router learning new credentials does not rewrite the credentials already stored in a sensor, plug, or lock.
Use a vendor's supported Thread network migration when it exists. Otherwise, a device on the retiring mesh may need a factory reset and fresh setup on the chosen network. Preserve names and automation notes, but expect Home Assistant to create a new device record or control item, called an entity. Move a harmless light or plug first, not a lock, alarm component, thermostat, leak shutoff, or other safety-sensitive device.
Six Things That Do Not Merge Thread
- Setting a network as preferred: this influences future onboarding; it does not move devices already on another mesh.
- Matter multi-admin: it shares controller permission, not Thread credentials or radio membership.
- Adding the same device to Apple and Home Assistant: two Matter fabrics can still reach one unchanged Thread attachment.
- Buying another border router and powering it on: without shared credentials, it may create another network instead of strengthening the first.
- Giving two networks the same visible name: matching names do not make their hidden keys and identifiers equal.
- Factory-resetting the last working router first: that can destroy the easiest path to the credentials and leave every endpoint stranded.
What Stays Local, and What Still Uses Cloud?
Thread itself is a local IP radio network. A supported Matter command from Home Assistant can travel from the Home Assistant Matter controller, across Ethernet or Wi-Fi, through a border router, and to a Thread device without an internet round trip. Home Assistant Cloud is not required for ordinary local Matter control.
The surrounding ecosystem can still use cloud services. Apple uses Apple Account and iCloud Keychain for home membership and encrypted Matter records. Google uses Google Play services and account-backed home setup. Alexa voice and routines rely heavily on Amazon services. SmartThings and IKEA use their apps for account, remote, notification, support, or firmware paths. Credential synchronization may therefore need an account even when the light command itself stays local.
Thread 1.4 also improves optional internet connectivity for Thread products. That capability does not force every sensor to use a vendor cloud, and it does not make a cloud-dependent product local. Judge the controller, app, firmware path, and product policy separately.
Reliability and Safety Boundaries
Do not test a new migration method first on a front-door lock, alarm, heating control, water shutoff, or device that protects people or property. Keep physical keys, manual controls, required alarms, and manufacturer recovery instructions available. Move one non-critical device, test it through a router reboot and internet outage, then continue.
A single shared mesh can improve radio coverage only when devices can actually hear one another. Thread 1.4 does not overcome poor router placement, 2.4 GHz interference, broken local IPv6 addressing, blocked multicast discovery—the local announcements hubs use to find one another—or an unsupported virtual-machine network. Solve those fundamentals before treating credential sharing as a signal-strength fix.
Tara's Recommendation
For a new Home Assistant-first installation, use Home Assistant OS, the official Matter Server app, and one dedicated Thread radio such as Connect ZBT-2. Keep Zigbee on a separate coordinator—the adapter that runs the Zigbee network. Sync the Home Assistant credentials to the setup phone before adding the first Matter-over-Thread device, then share selected devices outward for family apps or voice control.
If Apple or Google already runs a stable Thread home, preserve that mesh and use Home Assistant's documented import-and-join path. For Alexa/eero, SmartThings, or DIRIGERA, keep a working network intact unless both platforms expose a supported credential-sharing procedure for the exact software versions in the house. Matter multi-admin is usually the safer way to add Home Assistant control while the market finishes implementing Thread 1.4.
Document four things at handoff: which platform created Thread, which routers share that network, which phone holds its preferred credentials, and where each automation runs. That page of notes is more useful than another hub bought on hope.
Frequently Asked Questions
Does Thread 1.4 automatically merge existing Thread networks?
No. It standardizes a secure way to share credentials so a compatible new border router can join an existing mesh. It does not combine two already-formed networks or move their devices.
Can Home Assistant join an Apple or Google Thread network?
Yes, through Home Assistant's documented phone-assisted path. Import Apple credentials with an iPhone or Google credentials with Android, make that network preferred, and then add Home Assistant's OpenThread Border Router.
Does Matter multi-admin merge Thread networks?
No. Multi-admin lets several Matter controllers operate one device. It does not copy Thread credentials, move the device to another mesh, or combine radio networks.
Do Amazon Echo and eero border routers support Thread 1.4?
Amazon's official Thread page updated May 1, 2026 lists its current Echo and eero border routers as Thread 1.1 or 1.3, not 1.4. Do not assume they can use the new cross-vendor one-time-passcode flow yet.
Is the nine-digit Thread joining code a Matter sharing code?
No. The Thread 1.4 administration code briefly authorizes access to the mesh credentials. A Matter sharing code adds another Matter controller to a device. Keep both private and use each only in its matching screen.
Will devices need to be reset when moving to one Thread mesh?
Not when you are only adding another compatible border router to the same credentials. Devices already on a separate mesh do not move automatically, so use a supported network-migration feature or expect to reset and recommission those devices one at a time.