Nest Thermostat will not complete setup or pairing

Usually not — Google states it is designed to work without one. But Google also names the exceptions: a heating-only or cooling-only system, or one using a zone controller, may need a C wire or another power-supply accessory. So the honest answer is that it normally does not, and your specific system may.

Probably not. The display sits behind a mirrored glass lens and reads as a plain mirror when asleep — that is the intended appearance. The motion sensor is what wakes it, so a thermostat in a corridor nobody walks down will appear dead far more often than one in a living room.

Yes, and on this model that is a real first step. It uses 2 AAA 1.5V alkaline cells for backup, user-replaceable — unlike Nest's rechargeable thermostats where a low-power symptom means a wiring investigation rather than a trip to the shop.

No. Google states it works with multi-zone systems but requires one thermostat per zone. A single unit controlling several zones is not a configuration this model supports, and trying to make one do it is the source of a lot of unexplained behaviour.

It works with most 24V systems — furnaces, air conditioners, boilers and heat pumps, forced air or radiant. Specifically: conventional systems with one stage of heating and cooling plus a second stage of either, and heat pumps with one stage of heating and cooling plus aux or emergency heat. Systems outside that are where compatibility problems come from.

Yes — 802.11b/g/n at 2.4 GHz and 802.11a/n at 5 GHz, plus Bluetooth Low Energy. It is dual-band, unlike much smart-home hardware.

Less than 1 kWh per month, per Google's specification. The thermostat's own consumption is not a meaningful factor in a heating bill either way.

Yes — it is Matter certified, so it can be controlled from Google Home and other Matter platforms. Capabilities exposed through Matter are those the standard defines; anything beyond that stays in the Google Home app.

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.

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.

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.

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.

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.

Matter setup codes are consumed per commissioning attempt, and a partially completed attempt can use one. Generate a fresh code from the device's own app rather than rescanning the printed label.

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.

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.

That is a power symptom. A thermostat drawing from the heating circuit rather than a dedicated common wire can hold enough charge for the display and not enough for sustained radio use. Check whether a C wire is landed, and read the thermostat's own voltage diagnostic rather than judging by the screen being lit.

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.

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.

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.

No. It is scoped to GA01334. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.

Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.

A reset can erase accounts, networks, maps, schedules or preferences without distinguishing setup, pairing. The ordered checks preserve that evidence.

Keep setup codes private and do not reset shared security devices casually.