Google Nest Hub 2nd Gen: Matter Support and Thread Border Router
Google Nest Hub 2nd Gen compatibility profile for Matter, Thread Border Router use, Google Home setup, Home Assistant limits, hub requirements, and alternatives.
Short answer
Google Nest Hub 2nd Gen can be a useful Google Home Matter controller and Thread Border Router, but it is not a general Home Assistant hub. For Home Assistant users, treat it as part of a Matter/Thread path that may help commissioning while still depending on Home Assistant Matter Server, Thread credentials, and multi-admin behavior.
Verified compatibility conclusion
Nest Hub 2nd Gen is a Google Home Matter controller and Thread Border Router. It can route Matter-over-Thread traffic on the LAN, but it is not a general Home Assistant hub and cannot replace Home Assistant Matter Server.
- Verified on
- 2026-07-19
- Evidence level
- Google support information + Home Assistant Matter and Thread documentation
Supported and unsupported features
| Feature | Verdict | What it means |
|---|---|---|
| Google Home Matter controller | Supported | Commissions and controls supported Matter devices in Google Home. |
| Thread Border Router | Supported | Provides Thread border routing for compatible Thread devices. |
| Use alongside Home Assistant | Supported | Home Assistant can use third-party border routers on the LAN; Matter devices still need to be shared to the Home Assistant Matter controller. |
| Configure Google Thread credentials from Home Assistant | Partial | Home Assistant can discover third-party Thread networks, but credential sharing and preferred-network behavior depend on the ecosystem and mobile device. |
| Replace Home Assistant Green, Yellow, or Matter Server | Not supported | Nest Hub does not run Home Assistant or its Matter controller service. |
Compatibility matrix
| Platform | Status | Required hubs | Page |
|---|---|---|---|
| Home Assistant | Partially compatible | Home Assistant Matter Server | Included on this page |
| Apple Home | Not supported | Apple home hub for Apple Home Thread devices | Included on this page |
| Google Home | Works | No extra hub identified | Included on this page |
| Alexa | Not supported | Compatible Echo Matter controller | Included on this page |
| Aqara | Not supported | Aqara Matter controller for Aqara Home devices | Included on this page |
Connectivity & Matter details
| Matter connection | Matter over Thread |
|---|---|
| Thread role | Thread border router |
| Needs Thread border router | No |
| Local control | Partial (some cloud) |
| Required hubs | No extra hub identified |
Known limitations
- Google Home focused
- Local features vary by Matter device type
Automation fit
Use this to decide whether the device is a good trigger, action, or support device for a real automation scene, and whether it is reliable enough for critical automations.
Works as trigger
partial
Works as action
partial
Local readiness
low
Cloud dependency
full
Trigger reliability
low
Maintenance risk
high
Network sensitivity
high
Critical automation
avoid
- Trigger type
- state
- Expected entities
- basic control entities
- Confirm entity exposure in Home Assistant before building automations.
- Add unavailable-state handling for long-running automations.
- Google Home account
- Matter accessories
- Home Assistant Matter path for HA use
Avoid using this for
- general Home Assistant hub replacement
- local-only automations
- assuming Google Thread credentials automatically move to HA
Recommended fallback
- manual override
- unavailable notification
Local control vs cloud or app dependency
| Connection path | Local behavior | Cloud or app dependency |
|---|---|---|
| Google Home | Matter and Thread traffic use local IP networking where supported | Google Home setup, account management, remote access, and hub updates remain Google-managed |
| Google Home → Home Assistant multi-admin | Home Assistant controls the shared Matter device through its own Matter fabric | Use a fresh Google Home sharing code; the Nest Hub itself is not imported as a Matter accessory |
| Third-party Thread Border Router on HA LAN | Routes encrypted Thread packets; the border router does not control the accessory | Home Assistant Matter Server and correct IPv6/mDNS connectivity are still required |
Hub, bridge, and firmware requirements
Nest Hub 2nd Gen is a Google Home Matter controller and Thread Border Router. It can route Matter-over-Thread traffic on the LAN, but it is not a general Home Assistant hub and cannot replace Home Assistant Matter Server.
Keep Nest Hub on the current Google production software. Google updates the hub automatically and does not provide a user-selectable minimum Matter/Thread firmware for this compatibility path.
Common setup and troubleshooting guides
Evidence sources
Compatibility changes with firmware, region, and platform releases. These sources were checked on 2026-07-19.
Need a final setup and reliability path?
$1.99 setup + reliability report
Send your scene, devices, hubs, and target ecosystem. We will return what to connect, what hub is missing, which features may not work, reliability risks, fallback checks, and what to buy or avoid.
Related setup paths
FAQ
Is Google Nest Hub 2nd Gen a Thread Border Router?
Yes, it can serve as a Thread Border Router in Google Home setups, but that does not automatically mean Home Assistant can use the same Thread credentials without the right Matter and network path.
Is Google Nest Hub 2nd Gen a Matter controller?
It can participate in Google Home Matter setup. For Home Assistant, you still need the Home Assistant Matter path and a valid multi-admin or commissioning flow.
Can Google Nest Hub 2nd Gen replace Home Assistant hardware?
No. It can help with Google Home, Matter, and Thread, but it does not replace Home Assistant Green, Yellow, Matter Server, or a dedicated Home Assistant installation.
Why does a Thread device work in Google Home but not Home Assistant?
The device may be attached to a Google-owned Thread network or Matter fabric. Use a fresh multi-admin share code and verify Home Assistant Matter Server before resetting the device.
Feedback
Help improve this compatibility data
Smart home compatibility changes quickly. Send a report, request a missing device, flag information that needs another review, or tell us if a paid setup diagnosis would save you time.
Describe your devices, hubs, blocker, reliability risk, and the report output that would save you time.
Tell us which device, hub, bridge, protocol, or ecosystem should be added next.
Flag outdated, incomplete, or unclear setup guidance so it can be reviewed.
Choose a gateway, bridge, interface, or conversion path for KNX, BACnet, Modbus, DALI, Matter, Zigbee, Z-Wave, MQTT, or Home Assistant.