Nest Doorbell (battery) will not complete setup or pairing

Because it is not supposed to. Google states that with the Nest Doorbell (battery), your existing wired chime will not ring — the press notifies your phone and compatible Google speakers and displays instead. This catches out people who hardwired it specifically expecting the old chime to keep working, and no setting changes it.

Up to 10 feet, from four 850 nm infrared LEDs. That is a short range as published, and it is the single most useful fact about this model at night: a visitor perfectly visible in daylight at the gate can be effectively invisible after dark. It is a specification, not a fault.

No. Google states explicitly that whether it is installed on battery or on existing wiring, this model cannot record continuous 24/7 video history. Hardwiring it changes how it charges, not what it records — which is a common and expensive misunderstanding.

No. It uses a PIR sensor, which detects heat crossing its field, and glass blocks that. The same physics makes it less reliable in hot weather when the background temperature approaches body temperature — both are properties of the sensor, not settings.

Yes — 802.11a/b/g/n/ac on both 2.4 GHz and 5 GHz, with WPA3 supported and Bluetooth Low Energy for setup. Advice that Nest cameras are 2.4 GHz only does not apply to this model.

8–24VAC, 10VA, 50-60Hz. Wiring it powers the chime circuit and recharges the battery; the battery remains the device's power source and still has to be healthy.

It shoots 3:4 — portrait — at 960 x 1280 pixels, deliberately, so a parcel on the doorstep is in frame. It is why footage from this doorbell will not line up with a 16:9 Nest Cam pointed at the same scene, and why its 145° diagonal figure is not comparable with cameras that quote horizontal and vertical separately.

No. Google states it requires the Google Home app and a Google Account, and is not compatible with the Nest app or home.nest.com. Troubleshooting written for older Nest hardware routinely references screens that do not exist for this device.

Up to 3 hours of event video history. A Google Home Premium subscription extends that to up to 30 days, and an Advanced plan to up to 60. Events older than your tier are gone — which is worth knowing before an incident rather than after one.

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.

Full, on the supplied adapter. The Wi-Fi radio at full transmit power draws several times what the status light does, so a battery with enough charge to blink is not necessarily enough to negotiate a connection. Setup that fails intermittently on a part-charged device is usually this.

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 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 GA01318. 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.