Direct answer
For the Nest Hub (2nd gen), controller eligibility, setup code, prior fabric, Thread/Wi-Fi and multi-admin support should be resolved. First, identify the exact protocol/controller and confirm active hub eligibility.
What this covers
- Nest Hub (2nd gen) (GA01331)
- Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- The specific fault this record addresses: will not connect through Matter, HomeKit or another platform
What it does not cover
- ×The same symptom on a different Google Nest product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
The device is still commissioned to a fabric it can no longer reach
What separates it It appears in the old controller and works in none, or joins a new controller and drops out within minutes. A reset clears local settings on several implementations without clearing commissioning data.
How to confirm Remove it from every previous controller BEFORE resetting the hardware. Doing it in the other order is the single most common way this ends up unrecoverable without support.
- 2
No border router is present or it is offline
What separates it A Thread device commissions and then becomes unreachable, or never commissions at all. Thread accessories have no independent path and need an active border router on the network.
How to confirm Identify which device is acting as the border router and confirm it is online. This is not optional infrastructure and it is easy to remove by accident.
- 3
The platform does not support this device type
What separates it The device commissions successfully and some capabilities are missing on one platform. Standards cover a defined set of device types and attributes, and manufacturer-specific features fall outside them.
How to confirm Compare the capability list against what the standard defines for that device type. Missing extras is expected behaviour, not a fault.
- 4
The controller's own version is too old
What separates it Commissioning fails on one controller and succeeds on another. Support arrives in controller software releases, and an older hub simply does not know the device type.
How to confirm Check the controller's version against the manufacturer's stated requirement before changing anything on the device.
- 5
The device is on a network segment the controller cannot reach
What separates it Both are online and cannot find each other. IoT VLANs, guest networks and client isolation all break local discovery, which these protocols depend on.
How to confirm Put both on the same segment with isolation off for the test. Discovery here is local, not cloud-mediated.
- 6
Thread and Wi-Fi versions of the same product behave differently
What separates it Instructions that work for one unit fail on an apparently identical one. Manufacturers ship both radios under one retail name, and the commissioning path differs.
How to confirm Check the model identifier on the label rather than the retail name.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Every controller and platform this device has ever been commissioned to, including ones no longer in use.
- The exact protocol involved and the exact controller version, both read rather than assumed.
- Whether the device commissions and then drops, or never commissions at all — these are different failures.
- Whether a border router is present on the network and which device is acting as it.
- The model identifier from the device label, since Thread and Wi-Fi variants ship under one retail name.
- Which network segment each of the device and the controller is on, and whether client isolation is enabled.
Remove it from every previous controller before touching the hardware
Reset / data riskThis order is the whole game. A reset clears local settings without clearing commissioning data on several implementations, and a device that still believes it belongs to an unreachable fabric will keep trying to rejoin it rather than accepting a new one — a state that frequently needs manufacturer support to clear.
Confirm a border router is present and online
ReversibleA Thread accessory has no independent network path and cannot function without one. Identify which device is acting as border router — it is easy to remove or replace by accident, and its absence looks exactly like a broken accessory.
Check the controller's version against the requirement
ReversibleSupport for a device type arrives in controller software, not in the accessory. Commissioning that fails on one controller and succeeds on another is a version gap, and nothing done to the device will close it.
Put the device and the controller on the same network segment
ReversibleDiscovery here is local rather than cloud-mediated, so IoT VLANs, guest networks and client isolation all break it while leaving both devices apparently online. Test with isolation off before concluding anything.
Read the model identifier from the label, not the box
ReversibleManufacturers ship Thread and Wi-Fi variants under one retail name with different commissioning paths. Instructions that work on an apparently identical unit failing here is usually this.
Confirm control from both platforms before finishing
ReversibleA device that works on the new platform and has silently dropped off the old one is a half-completed job. Test both, and test one of them away from the home network.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- GA01331. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- Display
- A 7-inch touchscreen in a 4.7 in high by 7.0 in wide enclosure.
- No camera
- This model has no camera at all — unlike the Nest Hub Max, which does. Any instruction involving video calling, camera-based gestures or a camera shutter belongs to the Max and not to this device.
- Audio
- A full-range speaker and 3 microphones.
- Sensors
- Soli, Ambient EQ and a temperature sensor. Soli is a radar sensor — it is what supports presence and gesture features without a camera, and it is also why this model can behave as though it sees you when it has no camera.
- Power
- A DC power jack and a 15W power adapter. There is no battery, so it stops with the power and returns with it.
- Connectivity
- Wi-Fi, Bluetooth and Thread. The Thread radio matters: this device can act as infrastructure for Thread accessories in the home, so removing or replacing it can take other devices offline.
- Platform
- Matter compatible, with an ARM CPU carrying a machine-learning hardware engine for on-device processing.
- Power path
- Mains adapter into a standard outlet. Switched outlets and outlets on a circuit that trips are the two failure modes that present as device faults. Use the supplied adapter — third-party adapters that supply the right voltage at the wrong current are a common cause of intermittent restarts.
- Radio
- Thread mesh, which needs an active border router to reach anything beyond the mesh. Commissioning data survives a hardware reset on several implementations, so removal from the previous fabric has to happen before the reset, not after it.
- Microphone
- Carries a microphone with a hardware mute. A muted microphone is a physical switch state that no app setting overrides, and is the first thing to check for any voice or audio symptom.
- Symptom boundary
- This record covers Google Nest Nest Hub (2nd gen) when it will not connect through Matter, HomeKit or another platform. A different symptom on the same hardware, or this symptom on a different Google Nest product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !The device is locked to a fabric that no longer exists and will not accept a new commissioning after a documented reset. This generally needs the manufacturer.
- !The border router hardware has failed and every Thread accessory in the home depends on it.
- !The capability you need is not defined by the standard for this device type, which no configuration will produce.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Nest Help publishes this as "Set up, manage, and control Matter-enabled devices with Google Home". Genuinely cross-product Google Home Matter/multi-platform article, not device-specific. Verified reachable and content-matched via the Browser tool 2026-08-28. What that article does not carry is the model boundary — it is written for a product line, and GA01331 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
Where is the camera on the Nest Hub (2nd Gen)?+
There isn't one. This model has no camera — the Nest Hub Max does. Instructions involving video calls, camera gestures or a physical camera shutter are written for the Max, which is the most common source of confusion between the two.
How does it detect me if it has no camera?+
Soli, a radar sensor. It supports presence and gesture features without any camera, which is a genuine privacy difference from camera-based displays and also why the device can appear to see you when it cannot.
My Thread devices went offline when I unplugged the Hub.+
That is expected and it is the most important thing to know about this device. It carries a Thread radio and can act as infrastructure for Thread accessories, so removing, moving or replacing it can take other devices offline with it. It has no battery, so a power cut does the same.
Does it have a battery?+
No. It uses a DC power jack and a 15W adapter, so it stops with the power and comes back with it. Anything depending on it — including Thread accessories — stops too.
Can I use a different power adapter?+
Use the supplied 15W adapter. A DC jack that accepts a plug is not the same as a supply that delivers the right current, and an underpowered adapter produces restarts that read exactly like a failing device.
Does it work with Matter devices?+
Yes — it is Matter compatible and carries Thread, which is the combination that lets it act as a controller and a border router for Matter-over-Thread accessories rather than only as a display.
I reset it and now nothing can add it.+
That is the order problem, and it is the most common serious mistake on this symptom. A reset clears local settings without clearing commissioning data on several implementations, so the device still believes it belongs to a fabric it cannot reach and keeps trying to rejoin it. Removing it from the old controller first is what avoids this.
It joins and then disappears within minutes.+
That is the same disagreement seen from the other side — the device is being pulled back toward a fabric it still holds credentials for. It is not a signal problem, and improving the network will not change it.
Do I need a hub for this?+
For Thread, yes — an active border router, without which the accessory has no path to anything. It is genuine infrastructure rather than an optional convenience, and it is easy to remove by accident when replacing a speaker or a display.
Some features are missing on one platform.+
Standards define a fixed set of device types and attributes, and manufacturer-specific extras fall outside them. Missing extras on a cross-platform integration is expected rather than broken, and the manufacturer's own app remains the place those features live.
Both devices are online and cannot find each other.+
Discovery here is local rather than cloud-mediated, so an IoT VLAN, a guest network or client isolation will break it while leaving both perfectly online. Put both on the same segment with isolation off before investigating anything else.
The same instructions worked on an identical device.+
Check the model identifier on the label rather than the retail name. Manufacturers ship Thread and Wi-Fi variants of one product under one name, and their commissioning paths differ — two units that look identical can genuinely need different steps.
Is it worth using the manufacturer's app as well?+
Usually yes. The standard covers the common capabilities; the manufacturer's app covers everything else, including firmware updates and the settings that are not in the standard. Treating cross-platform control as a replacement rather than an addition is what produces most of the missing-feature complaints.
Does this answer apply to every Google Nest model?+
No. It is scoped to GA01331. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
What should I record before troubleshooting Matter or HomeKit?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing Matter, HomeKit. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Keep setup codes private and do not reset locks/alarms casually.
Answer for the exact device and software version shown above.