Direct answer
For the Nest Hub (2nd gen), power, reset state, owner account, Bluetooth/local permission and supported home network should be proved. First, confirm the exact setup indicator and place the phone/controller nearby.
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 complete setup or pairing
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 owned by a previous account
What separates it Setup gets as far as finding the device and then fails at the claim step, often with a message about the device being unavailable or already in use rather than a network error. Second-hand units and warranty replacements are the usual case, but so is a unit you personally set up before and removed from the app without removing from the account.
How to confirm A factory reset does not clear cloud ownership on most platforms. Ask the previous owner to delete it from their account, or open a support case with the serial number — that is the only path that releases it.
- 2
Bluetooth or Local Network permission is denied to the app
What separates it The app never finds the device at all, or finds it and immediately loses it, on a phone sitting next to it. iOS in particular denies Local Network access silently after the first prompt is dismissed, and the app usually reports this as a device fault rather than a permission one.
How to confirm Open the phone's per-app permission screen and confirm Bluetooth and Local Network are both allowed. Toggling them off and on again forces a fresh grant; a reinstall does not always re-prompt.
- 3
The device never left its previous Thread or Zigbee fabric
What separates it The device shows as present but unresponsive, or joins and drops within minutes. A mesh radio that still holds credentials for a network it can no longer reach will keep trying to rejoin it instead of accepting a new one.
How to confirm Remove it from the previous controller before resetting the hardware. A hardware reset alone leaves stale fabric data on several Thread and Zigbee implementations.
- 4
Router client isolation or a captive portal is blocking the handover
What separates it Setup completes on the phone, the device joins, and then never appears online. Guest networks, hotel and campus networks, and some mesh 'device isolation' modes prevent the phone and the device from ever seeing each other again.
How to confirm Join both to the main network with isolation off. If the network requires a browser sign-in page, the device cannot complete it and will never be usable there.
- 5
The account region does not match the hardware region
What separates it Setup fails at the final account step with a generic error, on hardware bought in a different country. Regional variants of the same model can be locked to their own service region.
How to confirm Compare the region on the device label against the account's region setting. This is not something the app can fix; it needs the matching account region or the matching hardware.
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.
- The exact wording of the failure message and the step it appeared on — network selection, credential handover, account claim or final verification are four different failures with one label.
- The device's status indicator pattern at the moment of failure: colour, and whether it is solid, slow-blinking or fast-blinking. This is the only diagnostic the device itself emits.
- The full model identifier from the device label, not from the box or the retail listing. Regional variants and generations share retail names.
- Whether the device has ever been set up before, by anyone — including by you, on an account you no longer use.
- How many setup attempts have been made, because several platforms rate-limit repeated claim attempts and then fail for a reason unrelated to the original one.
Confirm the exact model and its setup prerequisites
ReversibleRead the model identifier from the device label and check it against GA01331. Generations that share a retail name frequently do not share a setup path, a supported band or a required hub.
Establish whether the device has a prior owner
ReversibleA device that was ever claimed by another account will fail setup at the ownership step regardless of how many times it is reset. Settle this before touching the network, because every other check is wasted if the answer is yes.
Grant Bluetooth and Local Network permission explicitly
ReversibleOpen the phone's per-app permission screen rather than trusting the in-app prompt. A denied Local Network grant on iOS produces a device-not-found error that reads exactly like a hardware fault.
Remove the device from any prior fabric before resetting it
Reset / data riskDelete it from the previous controller, hub or bridge first. A hardware reset clears local settings but leaves commissioning data on several implementations, and the device will keep trying to rejoin a network it can no longer reach.
Move the device and phone within a few feet of the router
ReversibleComplete setup at close range even if the device will live elsewhere. Setup transfers credentials at the weakest link in the chain, and a marginal signal fails it in ways that give no useful error.
Run the documented setup once, without retrying into a rate limit
ReversibleFollow the manufacturer's sequence a single time and let it either finish or fail cleanly. Repeated rapid attempts trigger claim rate limits on several platforms, after which the failure reason no longer reflects the original problem.
Verify local and remote control separately
ReversibleControl the device once on the home network, then once with the phone on cellular data with Wi-Fi off. Setup that produces local control but not remote control is an account or provider-service problem, not a pairing one.
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 complete setup or pairing. 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 previous account and the previous owner is unreachable — only the manufacturer can release it, and only against proof of purchase.
- !The hardware region does not match the account region — no configuration change resolves this.
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 "Fix issues during Google smart speakers or displays setup". Google's own speaker/display setup-troubleshooting article. Verified reachable and title-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.
Why does setup fail at the same point every time?+
A failure that lands consistently on one step is describing a real constraint, not a glitch. Failures at the network step point at band or credentials; failures at the account step point at ownership or region; failures partway through the transfer point at power. A truly random failure looks random — it moves.
Does a factory reset clear the previous owner?+
Usually not. A factory reset clears settings held on the device. Ownership is held in the provider's account system, and only the previous owner or the manufacturer's support team can release it. This is deliberate — it is what makes a stolen device useless.
The app cannot see the device at all. Is it faulty?+
Far more often it is a phone permission. Bluetooth and Local Network access are both required to discover a device during setup, and a denied Local Network grant on iOS produces exactly the symptom of absent hardware. Check the per-app permission screen before concluding anything about the device.
Why does setup fail on my guest network?+
Guest networks normally enable client isolation, which prevents the phone and the device from seeing each other. Setup may appear to complete and the device then never becomes controllable. Use the main network.
Can I set this up on hotel, campus or workplace Wi-Fi?+
Not on any network that requires accepting terms in a browser. The device has no browser and cannot complete a captive portal sign-in. Networks that register devices by MAC address may work if the administrator registers it first.
Do I have to remove it from my old hub before setting it up again?+
Yes, and in that order. Resetting the hardware first leaves commissioning data behind on several Thread and Zigbee implementations, and the device will then keep trying to rejoin a network it can no longer reach instead of accepting a new one.
Should I set it up in its final location or next to the router?+
Next to the router, then move it. Setup transfers credentials over the weakest link in the chain and fails ambiguously at marginal signal. Confirming it works at close range separates a setup problem from a placement problem.
How many times should I retry before something else is wrong?+
Once, cleanly, after each change you make. Repeated rapid attempts trigger claim rate limits on several platforms, and after that the error message describes the rate limit rather than your original problem — which is how people end up chasing a fault that no longer exists.
Setup completed but the device shows offline immediately.+
That splits cleanly: control it once on the home network, then once from cellular with Wi-Fi off. Local control working and remote failing is an account or provider-service issue. Neither working is a network join that did not actually complete.
Is a second-hand unit worth buying?+
Only with the seller present to remove it from their account, or with proof of purchase for a support release. Cloud ownership survives factory resets by design, and a locked device cannot be recovered by any sequence of button presses.
Does the app version matter?+
It can. Setup paths change between app releases more often than device firmware does, and an outdated app can fail against a newer device that shipped with newer firmware. Update the app before the fourth attempt, not after the fortieth.
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 setup or pairing?+
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 setup, pairing. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Keep setup codes private and do not reset shared security devices casually.
Answer for the exact device and software version shown above.