Google Nest · voice control

Nest Cam (battery) does not respond to voice control

Nest Cam (battery) does not respond to voice control: microphone/wake, account linking, device name/room and provider service should be separated. Scoped to GA01317, with the model boundary and safe stop points made explicit.

Direct answer

For the Nest Cam (battery), microphone/wake, account linking, device name/room and provider service should be separated. First, test a basic local assistant command and inspect mute status.

What this covers

  • Nest Cam (battery) (GA01317)
  • Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
  • The specific fault this record addresses: does not respond to voice control

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

    The microphone is muted at the hardware switch

    What separates it The device is otherwise entirely normal and simply never reacts. Almost every voice device has a physical mute that no app setting overrides, and it is easy to knock while cleaning.

    How to confirm Look at the device for the mute indicator rather than checking the app. This costs five seconds and is the single most common cause.

  2. 2

    The device name does not match what is being said

    What separates it Other commands work and one device never responds. Assistants match on the name and room recorded in the linked account, which can differ from what the manufacturer's app shows.

    How to confirm Ask the assistant to list the devices it knows about, and use exactly the name it reports. A name with a number, a duplicate, or a room prefix is a common mismatch.

  3. 3

    The account link has expired or was never completed

    What separates it Voice control stopped on a date, or has never worked, while the manufacturer's own app is fine. Links expire on password changes and on some platform migrations.

    How to confirm Unlink and relink the account rather than re-adding the device. The device is not the broken part.

  4. 4

    Two devices share a name or a room

    What separates it The wrong device responds, or nothing does because the assistant cannot disambiguate. Duplicate names are created easily and are invisible until a command is ambiguous.

    How to confirm List the devices the assistant knows and look for repeats. Renaming one is the whole fix.

  5. 5

    Ambient noise or distance rather than the microphone

    What separates it It responds when the room is quiet and not when music is playing or several people are talking. Wake-word detection degrades with noise long before it fails outright.

    How to confirm Test in a quiet room at close range. Working there and failing elsewhere is an acoustics problem, not a fault.

  6. 6

    The requesting person is not a recognised member

    What separates it One household member is refused and another is not. Voice profiles and household membership gate personal results and some device control.

    How to confirm Compare the same command spoken by the owner and by the member.

  7. 7

    The action itself is not exposed to voice

    What separates it The device responds to some commands and reports that it cannot do others. Not every capability is exposed through every assistant, and security actions in particular are commonly restricted or require a spoken code.

    How to confirm Check the assistant's documented capability for that device type rather than assuming parity with the manufacturer's app.

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 words spoken, verbatim. Paraphrasing a failing command loses the thing that made it fail.
  • The state of the hardware mute indicator, read at the device.
  • Exactly what the assistant said back, if anything — a refusal, a wrong device, silence and a misheard word are four different failures.
  • The device's name as the assistant reports it, not as the manufacturer's app shows it.
  • Whether the same command works for another household member.
  • Whether the room was quiet, and how far away the speaker was.
  • Whether other commands to the same device work, which separates the link from the phrasing.
Try in this order0 of 7 completed
  1. Look at the hardware mute indicator on the device

    Reversible

    Not in the app — on the hardware. Almost every voice device has a physical mute that no software setting overrides, it is easy to knock while cleaning, and it produces a device that is perfectly normal in every other respect and simply never reacts.

  2. Control the device in its own app

    Reversible

    Working there and failing by voice puts the fault in the assistant link, not in the device. This is worth establishing before touching any voice setting, because the two are commonly confused.

  3. Ask the assistant to list the devices it knows

    Reversible

    Use exactly the name it reports back. Assistants match on the name and room held in the linked account, which can differ from what the manufacturer's app displays — and a mismatch there is silent.

  4. Look for duplicate names and duplicate rooms

    Reversible

    Two devices sharing a name means the assistant either picks the wrong one or refuses to pick at all. This is invisible until a command is ambiguous, and renaming one device is the entire fix.

  5. Test in a quiet room at close range

    Reversible

    Wake-word detection degrades with background noise and distance long before it fails outright. Working close up in silence and failing across a noisy room is acoustics, and no setting change addresses it.

  6. Repeat the command as another household member

    Reversible

    Voice profiles and household membership gate personal results and some device control. One person refused and another accepted is a membership question rather than a device one.

  7. Relink the account rather than re-adding the device

    Signs you out

    Links expire on password changes and platform migrations, and the device itself is not the broken part. Unlinking and relinking preserves the device's own settings, where removing and re-adding it discards them.

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
GA01317. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
Camera
A 1/2.8-inch 2-megapixel sensor with 6x digital zoom, 16:9 aspect ratio — landscape, unlike the portrait 3:4 Nest Doorbell. Two Nest devices pointed at the same scene will frame it very differently.
Field of view
130° diagonal, which is narrower than the Nest Doorbell's 145°.
Video
Up to 1080p at 30 FPS with HDR, 24/7 live view, night vision with HDR, H.264 encoding.
Motion detection
A single motion sensor with a 110° horizontal field of view, effective up to 25 ft (7.5 m). The 25-foot figure is the one that matters: beyond it, detection is outside specification regardless of how sensitivity is set.
Night vision
Up to 20 ft (6.10 m) of illumination from six high-power 850 nm infrared LEDs — twice the reach of the Nest Doorbell (battery), which is specified at 10 feet.
Video history
Up to 3 hours of event-based history included, extendable to up to 60 days with a Google Home Premium subscription. Continuous Video Recording — up to 10 days of 24/7 history — requires BOTH that the camera is used plugged into continuous power AND a Google Home Premium Plus subscription. On battery alone it is not available.
Power
A built-in rechargeable 6 Ah, 3.65V lithium-ion battery. The camera uses a proprietary magnetic connector for power rather than a standard USB port, so a generic cable is not a substitute and a poor magnetic seating is a real cause of a camera that will not charge.
Wi-Fi
802.11a/b/g/n on 2.4 GHz and 5 GHz, with WEP, WPA, WPA2 and WPA3 supported, plus Bluetooth Low Energy. Dual-band hardware.
App
Requires the Google Home app and a Google Account. Google states it is not compatible with the Nest app or the home.nest.com site.
Power path
Internal or removable battery. Every capability that costs current — night vision, higher stream quality, longer recordings, frequent events — is paid for in runtime, so a change in behaviour after a settings change is usually a power consequence rather than a fault. Cold weather reduces usable capacity sharply.
Siting
Rated for outdoor installation. Water ingress at the cable entry, corrosion at the contacts and temperature at the extremes of the rated range all present first as intermittent electrical faults, not as visible damage.
Service tier
Some capabilities are subscription-gated. A feature that stops working on a date with no other change is worth checking against the plan's renewal before it is treated as a fault.
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 Cam (battery) when it does not respond to voice control. 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 microphone does not respond at close range in a silent room with the mute confirmed off, which points at the microphone hardware.
  • !Account linking fails repeatedly with a provider-side error that neither app can resolve.
  • !Voice is being relied on as the only way to operate a lock, alarm or access device — it should never be the sole path.
  • !The assistant consistently misidentifies who is speaking in a way that exposes personal results to the wrong person.

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 "Google Nest camera and doorbell help". Official Google Nest camera and doorbell setup, video, notification and subscription help. What that article does not carry is the model boundary — it is written for a product line, and GA01317 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

How far can the Nest Cam (battery) actually detect motion?+

Google specifies a single motion sensor with a 110° horizontal field of view, effective up to 25 ft (7.5 m). Beyond that distance detection is outside specification, and no sensitivity setting extends it — which is the answer to most 'it misses people at the end of the drive' reports on this model.

How far does its night vision reach?+

Up to 20 ft (6.10 m), from six high-power 850 nm infrared LEDs. That is twice the published reach of the Nest Doorbell (battery) at 10 feet, so the two models genuinely are not interchangeable for a dark approach.

Why will it not charge with my USB cable?+

It uses a proprietary magnetic connector rather than a standard USB port, so a generic cable is not a substitute. A magnetic connector that is not seated squarely is also a real cause of intermittent charging on this camera, and it looks exactly like a failing battery.

Can the Nest Cam (battery) record continuously?+

Only under two conditions together: it must be used plugged into continuous power, and you need a Google Home Premium Plus subscription. That gives up to 10 days of 24/7 history. On battery power alone, continuous recording is not available no matter what plan you hold.

Does it work on 5 GHz Wi-Fi?+

Yes — 802.11a/b/g/n on both 2.4 GHz and 5 GHz, with WPA3 supported. Generic advice that smart-home cameras are 2.4 GHz only does not apply here.

Why does the picture look different from my Nest Doorbell?+

Different sensors and different shapes. This camera is 2 MP, 16:9 landscape, 130° diagonal; the Nest Doorbell (battery) is 1.3 MP, 3:4 portrait, 145° diagonal. Pointed at the same scene they produce genuinely different framing and detail, and neither is faulty.

How much history do I get for free?+

Up to 3 hours of event-based video history. A Google Home Premium subscription extends it to up to 60 days. Anything older than your tier is gone, which is worth understanding before you need to retrieve something.

Can I use the old Nest app?+

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 — so older Nest troubleshooting references screens this device does not have.

It has completely stopped responding to voice.+

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.

Other commands work but this one device never responds.+

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.

The wrong device responds.+

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.

Voice control worked and then stopped with no changes.+

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.

It only works when the room is quiet.+

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.

It hears me but does the wrong thing.+

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.

My partner can control it and I cannot.+

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.

Can I use voice to unlock the door?+

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.

Should I re-add the device to fix voice control?+

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.

Does this answer apply to every Google Nest model?+

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

What should I record before troubleshooting voice control or Alexa or Google?+

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

When should I stop and use qualified service?+

Do not disclose voice history or account credentials.

Change recordSept. 1, 2026 — Built out with researched, cross-checked per-model specifications and model-specific guidance. Aug. 17, 2026 — Published with explicit GA01317 applicability, a voice-control diagnostic boundary and first-party support provenance.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device