Introduction

If you own a Google Nest Hub (2nd Gen) and run Home Assistant, you likely already have everything needed to build a Thread-based smart home — no extra dongle required. Many enthusiasts assume a SkyConnect or ZBT-1 USB stick is mandatory for Thread devices. That’s not true if your Nest Hub already serves as a Thread Border Router on your network.

This guide walks through the complete setup: from understanding Thread vs. Matter, to configuring your Nest Hub as Home Assistant’s primary Thread Border Router, to pairing a real IKEA Matter-over-Thread bulb. By the end, you’ll have a fully local Thread mesh controlled by both Google Home and Home Assistant simultaneously — no cloud dependency for local operation.

We’ll cover VLAN considerations, the critical Preferred Thread Network setting, and practical troubleshooting. If Thread seemed intimidating, this guide makes it approachable.

Understanding the Architecture

Before touching any configuration, let’s clarify how the pieces fit together. The Thread and Matter ecosystem involves several distinct roles — understanding who does what makes troubleshooting far easier.

Google Nest Hub 2 as Thread Border Router

The Google Nest Hub (2nd Gen) contains a Thread radio and automatically acts as a Thread Border Router (TBR). A border router bridges the low-power IEEE 802.15.4 Thread mesh to your home’s IP network — without one, Thread devices can only talk among themselves. The Nest Hub handles this routing transparently, creating a Thread network identified by a PAN ID like NEST-PAN-D60B.

Home Assistant as Matter Controller

Home Assistant acts as a Matter Controller via the Matter Server add-on. While the Nest Hub routes Thread traffic at the network layer, Home Assistant handles the application layer: discovering Matter devices, commissioning them, and sending commands. Think of it this way: the Nest Hub provides the road (Thread), and Home Assistant drives the car (Matter).

Google Home as Commissioner

Google Home serves as the Matter Commissioner — the entity that initially onboards a new Matter device onto your Thread network. When you scan a Matter QR code in the Google Home app, it handles secure pairing, assigns network credentials, and adds the device to Google’s Matter fabric. After that, Matter Multi-Admin lets you share the device with Home Assistant.

The Role of the Companion App

The Home Assistant Companion App on your phone is the critical bridge in this setup. Because your phone can detect Thread networks advertised over mDNS, the Companion App discovers the Nest Hub’s Thread network and relays its credentials to your Home Assistant server — which may lack direct Thread radio access.

Thread Credentials

Thread networks use credentials — network key, PAN ID, channel, extended PAN ID — that allow devices to join the mesh. When you „Send credentials to Home Assistant” via the Companion App, you copy these parameters into Home Assistant’s Thread integration. With shared credentials, Home Assistant knows which Thread network its Matter devices live on and communicates through the Nest Hub’s border router.

Prerequisites

Before starting, verify every item on this list. Missing one component blocks the entire setup.

• Home Assistant OS (or Supervised) — version 2024.5 or newer. Core and Container installations also work but require manual add-on management.
• Matter Server add-on — installed and running from the Home Assistant add-on store. Without it, Home Assistant cannot speak Matter.
• Thread integration — added via Settings → Devices & Services → Add Integration → Thread. This gives Home Assistant awareness of Thread networks.
• Google Home app — installed and logged into the same Google account linked to your Nest Hub.
• Home Assistant Companion App — installed on your phone (Android recommended for best Thread detection).
• Google Nest Hub (2nd Gen) — powered on, connected, running latest firmware. First-gen Nest Hub lacks a Thread radio.
• At least one Matter-over-Thread device — like an IKEA TRÅDFRI Matter bulb, to validate the end-to-end flow.

How Thread and Matter Are Different

The most common confusion in smart home tech: Thread and Matter are not the same thing. Thread is the network — the road. Matter is the application protocol — the car. A Thread device can work without Matter (using HomeKit over Thread), and Matter devices can use Wi-Fi or Ethernet. Matter over Thread combines low-power mesh networking with universal interoperability.

Border Router vs Matter Controller

Another key distinction: the Thread Border Router and Matter Controller are separate functions. They can run on the same hardware or on different devices. Here’s the breakdown.

Google Nest Hub vs Dedicated OTBR (SkyConnect/ZBT-1)

Should you use your Nest Hub or buy a dedicated OpenThread Border Router? Both work, but serve different use cases.

If you already own a Nest Hub 2, the answer is simple: use it. You save money, eliminate USB port usage, and get a zero-maintenance Thread Border Router that Google updates automatically. For a deeper look at smart home hub options, check our smart home category.

Step-by-Step: Setting Up the Nest Hub as Your Thread Border Router

Now the practical configuration. The process takes about 15 minutes if your Nest Hub is already running.

Step 1: Verify the Nest Hub firmware is up to date

Open the Google Home app, select your Nest Hub (2nd Gen), tap the settings gear, and scroll to „Device information.” Your firmware should be on the latest Fuchsia-based build. Install any pending updates before proceeding — outdated firmware causes Thread commissioning failures. Confirm the device is listed as „Nest Hub (2nd Gen)”; the first-gen model lacks a Thread radio entirely.

Step 2: Install the required Home Assistant integrations

Navigate to Settings → Add-ons → Add-on Store and install the Matter Server add-on. Start it and enable „Watchdog” for auto-restart. Then go to Settings → Devices & Services → Add Integration and add both Thread and Matter integrations. The Thread integration won’t show networks yet, but it must be present before importing credentials.

Step 3: Identify the Thread network in the Companion App

Open the Home Assistant Companion App and go to Settings → Companion App → Thread. The app scans for Thread Border Routers advertising via mDNS. If your Nest Hub is on a reachable network, you should see an entry under „Other networks” labeled NEST-PAN-D60B from Google Nest Hub #673B.

If nothing appears, force-close and reopen the Companion App, ensure your phone is on the same network as the Nest Hub, and wait 30 seconds for mDNS advertisements. Android detection is generally reliable; iOS may be inconsistent due to Apple’s mDNS handling.

Step 4: Make NEST-PAN your preferred network

Tap the NEST-PAN entry and select „Make Preferred Network.” This tells Home Assistant which Thread network to associate with all future Matter-over-Thread devices. Without this setting, Home Assistant cannot determine which Thread credentials to use during commissioning — the single most common setup pitfall.

After setting the preferred network, the dashboard shows details including channel, PAN ID, and border router count — confirming Home Assistant now references the correct network.

Step 5: Send credentials to Home Assistant

Still in Thread settings, tap „Send credentials to Home Assistant.” A permission dialog appears: „Allow Home Assistant to access your home network?” Tap Allow. This transfers the Thread network’s operational credentials — network key, PAN ID, extended PAN ID, and channel — from your phone to your Home Assistant server.

Once imported, check Settings → Devices & Services → Thread in Home Assistant’s web interface. The NEST-PAN network should appear with „Preferred network” status. The Telepathy panel shows extended PAN ID and operational parameters matching what the Companion App displayed.

Real-World Example: Pairing an IKEA Matter over Thread Bulb

Let’s put theory into practice with an IKEA TRÅDFRI Matter-over-Thread bulb, using Google Home as commissioner and sharing with Home Assistant — including a real VLAN setup.

Step 1: Connect your phone to the IoT VLAN

In my setup, IoT devices live on a separate VLAN. Matter commissioning uses mDNS and IPv6, both needing to reach your phone. Temporarily connect your phone’s Wi-Fi to the same VLAN/SSID where your Nest Hub resides. This ensures mDNS discovery works during pairing. We’ll cover permanent cross-VLAN operation later.

Step 2: Pair the bulb in Google Home first

Reset the IKEA bulb by toggling it six times (on-off-on-off-on-off) until it blinks. In the Google Home app, tap Add → New device, scan the Matter QR code, and follow the prompts. Google Home commissions the bulb onto the Nest Hub’s Thread network. After pairing, the bulb appears in Google Home under your chosen room.

Step 3: Open Linked Matter Apps

Navigate to the newly paired bulb in Google Home, tap settings, and scroll to „Linked Matter apps and services.” You’ll see the bulb with its Vendor ID (6006 for IKEA) and a „Link apps” button — this is Matter Multi-Admin in action.

Tap „Link apps” and select Home Assistant. Google Home generates a time-limited pairing code — complete the next step promptly.

Step 4: Home Assistant discovers the device

Open your Home Assistant web interface. If Matter integration is running and Thread credentials are imported, Home Assistant detects the new device and shows „New Matter device discovered.” Click Configure, enter the pairing code from Google Home, and assign a room. If discovery doesn’t happen, go to Settings → Devices & Services → Matter → Add Device and paste the code manually.

Step 5: Import Thread credentials into Home Assistant

If you skipped the Companion App credential import earlier, you can also import credentials directly from a commissioned Matter device. In the Companion App’s Thread settings, tap the device under „Thread devices” and select „Import credentials to Home Assistant.” This is an alternative path when the Companion App cannot directly detect the Nest Hub’s network.

Step 6: Preferred Thread Network becomes available

With credentials imported, the NEST-PAN-D60B network appears in Thread settings. Set it as preferred. Home Assistant now knows which Thread network to use for all future Matter-over-Thread devices. The bulb responds to commands from both Google Home and Home Assistant simultaneously — voice-control it via Google Assistant, and Home Assistant’s dashboard reflects the state change instantly.

Why Preferred Thread Network Matters

The Preferred Thread Network setting is not optional — it’s essential for multi-controller Thread environments. Without it, Home Assistant doesn’t know which Thread network to use when discovering new Matter devices. You might have multiple Thread networks (Nest Hub, Apple TV, Echo), and Matter devices join only one. Setting the preferred network tells Home Assistant exactly where its devices live.

Skipping this step produces the error „No Thread network available” even though your Nest Hub runs perfectly. This is the single most common pitfall in the entire setup — and it’s almost always fixed by explicitly setting the preferred network in the Companion App.

How Matter Multi-Admin Works

Matter Multi-Admin lets you share a single device across multiple controllers — like Google Home and Home Assistant — without re-pairing or factory-resetting. When you use „Linked Matter apps” in Google Home, you invoke Multi-Admin: the original commissioner generates an onboarding payload that Home Assistant uses to join the device’s existing Matter fabric.

Both controllers maintain independent control paths to the same device. Commands arrive via the shared Thread network and are processed by the device’s Matter layer. State changes report to all connected controllers — no polling, no cloud relay, no single point of failure. If Google’s cloud goes down, Home Assistant still controls the bulb locally via Matter over Thread.

VLAN Considerations

Many Home Assistant enthusiasts run segmented networks with IoT devices on a separate VLAN. Thread and Matter can work across VLANs, but require specific network configuration.

mDNS Between VLANs

Thread Border Routers advertise via mDNS with service type _meshcop._udp. If your phone is on VLAN 10 and the Nest Hub on VLAN 20, mDNS must forward between them. Solutions include Avahi mDNS reflector, mdns-repeater, or the mDNS gateway on UniFi/OPNsense. Without forwarding, the Companion App cannot detect the Nest Hub’s Thread network. For more networking guidance, see our smart home networking guides.

IPv6 Requirements

Thread uses IPv6 exclusively. Each Thread device gets a unique IPv6 address, and Matter messages travel over IPv6 UDP. Your router must support IPv6 on the IoT VLAN and route IPv6 between VLANs. If IPv6 is disabled on your network, Thread devices cannot communicate. Home Assistant itself needs IPv6 connectivity to reach the Nest Hub’s border router.

Multicast Forwarding

Beyond mDNS, Matter uses IPv6 multicast for device discovery (DNS-SD over IPv6). Ensure your router forwards IPv6 multicast between the VLANs where your Home Assistant server, Nest Hub, and phone live. On OPNsense, enable „Allow IPv6” on firewall rules. On UniFi, enable „Multicast Enhancement” on relevant Wi-Fi networks.

Temporary Same-VLAN Placement

The simplest approach during initial setup: temporarily place your phone and Home Assistant on the same VLAN as the Nest Hub. This eliminates networking complexity while importing credentials and pairing your first device. Once Thread credentials are stored in Home Assistant, cross-VLAN communication works as long as basic IPv6 routing functions — because communication goes through the Nest Hub’s border router, which already bridges both networks.

Firewall Considerations

Thread uses UDP ports 5540 (commissioning), 5353 (mDNS), and 5542 (operational traffic). Matter commissioning also uses TCP on ephemeral ports. Create a „Matter” firewall alias covering these ports and apply it to relevant VLAN interface rules. Don’t restrict outbound TCP from Home Assistant to the IoT VLAN.

Troubleshooting

Even with careful setup, issues arise. Here are the most common problems and solutions, drawn from real debugging sessions. For more help, browse our Home Assistant troubleshooting collection.

Preferred Thread Network Missing

This almost always means Thread credentials haven’t been imported. Go to Companion App → Thread settings and tap „Send credentials to Home Assistant.” If that button is also missing, ensure your phone is on the same network as the Nest Hub, force-quit the Companion App, reopen it, and wait 30 seconds.

Home Assistant Cannot See Thread Network

The Thread integration shows an empty list after importing credentials. This happens when the Companion App and Home Assistant server are on different networks and credential transfer failed. Verify your Companion App is connected to Home Assistant (Settings → Companion App → Connection). Try sending credentials again.

Commissioning Fails

Google Home commissioning fails with a generic error. First, ensure the device is in pairing mode (IKEA bulbs: six power toggles). Second, move your phone closer to the Nest Hub — Thread commissioning uses Bluetooth LE for initial pairing, and range matters. Third, ensure Bluetooth is enabled. If the device was previously paired to another Thread network (like Apple HomePod), factory-reset it first.

Device Only Appears in Google Home

You paired the device in Google Home, but Home Assistant never discovers it. Go back to Google Home, open „Linked Matter apps and services,” and ensure Home Assistant appears in the linked apps. If not, tap „Link apps” and redo the pairing flow. Also verify the Matter Server add-on is running and the preferred network is set correctly.

Thread Credentials Missing

The Companion App shows „No Thread credentials” despite a visible Thread network. Clear the Companion App’s cache (Android: Settings → Apps → Home Assistant → Storage → Clear Cache), then re-scan and re-import credentials.

Companion App Cannot Import Credentials

The „Send credentials” button is grayed out or unresponsive. On Android, ensure the Companion App has „Nearby devices” permission for Thread scanning. On iOS, Thread scanning is limited — use the alternative import method through a commissioned Matter device instead.

Multiple Thread Networks Detected

Seeing multiple Thread networks is normal if you have several border routers (Nest Hub, Apple TV, Echo). Choose the Nest Hub’s network as preferred. If you want to consolidate, disable Thread on other border routers: Apple Home → Settings → Home Hubs → disable; Alexa app → disable Thread feature.

Best Practices

• Keep firmware updated. Thread and Matter protocol improvements arrive via firmware. Check quarterly for Nest Hub and device updates.
• Document Thread network details. Note the PAN ID, extended PAN ID, and channel. Having these values simplifies recovery if you rebuild Home Assistant.
• Use a dedicated IoT VLAN. Once working, isolating IoT devices improves security and network management. See our smart home networking articles for VLAN setup guides.
• Avoid overlapping Thread networks. If you have Apple TV, Echo, and Nest Hub all as Thread Border Routers, they create separate incompatible meshes. Pick one ecosystem and disable Thread on the others.
• Test local control regularly. Disconnect internet briefly and verify Home Assistant still controls Thread devices. This confirms Matter local control works correctly.
• Back up before major changes. Matter and Thread configurations live in the .storage directory. A pre-change backup lets you revert if a firmware update breaks something.
• Monitor the Telepathy panel. In Home Assistant’s Thread integration, the Telepathy view shows active devices, routes, and link quality. Use it to diagnose mesh health.

Frequently Asked Questions

Conclusion

The Google Nest Hub (2nd Gen) is far more than a smart display — it’s a production-ready Thread Border Router that anchors your low-power smart home mesh. By combining it with Home Assistant’s Matter Server, Thread integration, and the Companion App, you get a fully local, multi-controller Thread environment without spending extra on hardware.

The setup follows a clear pattern: verify firmware, install integrations, detect the network, make it preferred, import credentials. Once done, every Matter-over-Thread device paired through Google Home can be shared with Home Assistant via Matter Multi-Admin. Both platforms control the device locally over Thread — no cloud relay, no vendor lock-in, no single point of failure.

If you’ve been putting off Thread, there’s never been a better time to start. Your Nest Hub is ready. Your Home Assistant is ready. And now, with this guide, you are too. Ready for more? Check out our complete smart home guide library for advanced automation ideas. Happy automating!