Nest Doorbell (battery) firmware update is stuck or failed

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.

Almost certainly not. Verification and writing produce no visible progress and routinely take much longer than the download. This is the symptom where intervening causes the damage — nearly every unrecoverable device on this fault was interrupted by someone who concluded it had hung.

Longer than you think, and the honest answer depends on the device — but the asymmetry is what matters. Waiting an extra hour costs an hour. Interrupting a write costs the device. Given that trade, wait.

A varying failure point is the network. An update is a large sustained transfer, and a link that is fine for control traffic can be inadequate for it. Move the device close to the router for the attempt. A failure at the same percentage every time would point at the package or at storage instead.

Check the charge level and whether it is on power. Several platforms refuse to begin below a threshold, and a battery device that sleeps partway through will fail repeatedly until it is charging throughout.

Staged rollouts are normal and deliberate — the provider releases in waves. The device is behaving correctly, waiting is the right action, and there is generally no supported way to force it forward.

No. A mismatched or modified image is the single most reliable way to turn a recoverable failure into an unrecoverable one, and it voids any support path you had. Official app only.

That is a regression rather than a failed update, and repeating the update will not undo it. Compare against the release notes and report it — rollback is generally not available on this class of hardware.

Stop power-cycling it. Repeated interruptions can compound a partial write, and each attempt reduces what a support team can recover. Record the version it was on and the stage it stopped at, and open a case.

Yes, for security fixes in particular — but do it when you can leave it alone, on power, near the router, and not when you are about to need the device. The update itself is low risk; being interrupted is the risk.

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 firmware, update. The ordered checks preserve that evidence.

Never interrupt critical-device firmware or use unofficial files.