Nest Doorbell (battery) does not respond to voice control

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.

Check the hardware mute first, on the device itself. It is a physical switch that no app setting overrides, it is easy to knock, and it produces a device that behaves entirely normally in every other way and simply never reacts.

That exonerates the microphone, the wake word and the service entirely — the problem is the device link or the name. Ask the assistant to list what it knows and use exactly the name it reports back, which is often not what the manufacturer's app displays.

You almost certainly have two devices sharing a name or a room, which the assistant cannot disambiguate. This stays invisible until a command is ambiguous. Listing the devices the assistant knows finds it, and renaming one is the whole fix.

Account links expire — commonly on a password change or a platform migration. The device is not the broken part, so unlink and relink the account rather than removing and re-adding the device, which would discard its settings for nothing.

Wake-word detection degrades with noise and distance long before it fails completely, so this is acoustics rather than a fault. Testing close up in a silent room confirms it in one attempt, and the fix is placement rather than settings.

That is intent matching, not the microphone — the words were transcribed and matched to a different action. What the assistant said back is the diagnostic here, and the exact phrasing matters, so record the command verbatim rather than paraphrasing it.

Voice profiles and household membership gate both personal results and some device control. Running the identical command as each person is the test, and the answer is a membership setting rather than anything on the device.

Where a platform allows it at all, it normally requires a spoken code, and many restrict it entirely. That restriction is deliberate: a voice command is audible through a door and by anyone in the room. Voice should never be the only way to operate a lock.

Not as a first step. Removing and re-adding a device discards its name, room, automations and shares — all to fix a link between two accounts that unlinking and relinking would have repaired without touching the device at all.

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 voice control, Alexa, Google. The ordered checks preserve that evidence.

Do not disclose voice history or account credentials.