Direct answer
For the Nest Cam (wired, 2nd gen), 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 (wired, 2nd gen) (GA01998)
- 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
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
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
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
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
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
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
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.
Look at the hardware mute indicator on the device
ReversibleNot 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.
Control the device in its own app
ReversibleWorking 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.
Ask the assistant to list the devices it knows
ReversibleUse 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.
Look for duplicate names and duplicate rooms
ReversibleTwo 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.
Test in a quiet room at close range
ReversibleWake-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.
Repeat the command as another household member
ReversibleVoice 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.
Relink the account rather than re-adding the device
Signs you outLinks 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
- GA01998. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- Power — plug-in WIRED (no battery on this model)
- The wired 2nd-gen Nest Cam plugs into mains power (USB-C adapter) — this version has no battery, so charging/runtime does not apply; a dead camera is a power/adapter/outlet issue. (Ring/Nest also make battery cams, but this is the wired one.)
- On-device AI
- Detects people, animals, vehicles and packages on-device; some features and event history need Nest Aware. Managed in the Google Home app.
- Recording needs Nest Aware
- Live view and alerts free; recorded history needs Nest Aware. It keeps a few hours of events locally during an internet outage and uploads later. 2.4/5 GHz Wi-Fi.
- Power path
- Mains adapter into a standard outlet. Switched outlets and outlets on a circuit that trips are the two failure modes that present as device faults. Use the supplied adapter — third-party adapters that supply the right voltage at the wrong current are a common cause of intermittent restarts.
- Wi-Fi
- Joins on 2.4 GHz. A phone on 5 GHz cannot hand credentials to it reliably during setup, and a router that steers clients between bands under one network name will produce intermittent joins that look like a hardware fault.
- 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 (wired, 2nd gen) 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 GA01998 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
My Nest Cam went offline — did I lose the footage?+
The wired Nest Cam has some on-device memory, so during a Wi-Fi or internet outage it keeps a few hours of event recordings locally and uploads them once it reconnects — so a brief outage usually does not lose events. For saved history beyond that, you need a Nest Aware subscription. If it is offline, check its power (it is plug-in, so confirm the adapter/outlet) and its 2.4/5 GHz Wi-Fi connection in the Google Home app. Reconnecting it restores live view and uploads the buffered clips.
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 GA01998. 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.
Answer for the exact device and software version shown above.