Direct answer
For the Nest Doorbell (battery), trigger, conditions, controller/hub, permissions and action chain should be tested separately. First, review activity history and trigger the action manually.
What this covers
- Nest Doorbell (battery) (GA01318)
- Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- The specific fault this record addresses: routine, schedule or automation is not running
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 trigger never fired
What separates it Nothing appears in the activity history at the expected time. Running the action manually works perfectly, which is what convinces people the automation is broken when the action is the one part that is fine.
How to confirm Check the history first. No entry means the trigger, not the action — and every minute spent on the action is wasted.
- 2
A condition was false at the moment it fired
What separates it The history shows the automation evaluated and did nothing. Conditions on presence, time of day, sunset, another device's state or a household member's location fail silently by design.
How to confirm Remove conditions one at a time and re-run. A routine that works with no conditions and fails with one identifies that condition exactly.
- 3
Time zone or location is wrong on the home, not the phone
What separates it Everything runs, at the wrong time — often by a whole number of hours, or with sunrise and sunset offset. The home's location is a separate setting from the phone's, and it defaults to wherever it was created.
How to confirm Check the home or hub's own time zone and address rather than the phone's. Sunset-based automations firing at a consistently wrong hour is this and almost nothing else.
- 4
Presence detection is the trigger and it is unreliable
What separates it Arriving and leaving automations fire late, early, twice, or not at all — and worse for one household member than another. Geofencing depends on the phone's location permission, its background activity allowance and its power state.
How to confirm Compare each member's phone permissions. A geofence needs 'always' location rather than 'while using', and battery optimisation defeats it silently.
- 5
One action failed and stopped the chain
What separates it The first part of a routine happens and the rest does not, consistently at the same point. Actions run in order and a failure partway leaves a half-executed result.
How to confirm Run each action individually. The one that fails alone is the one that is stopping the chain, and it usually has its own separate fault.
- 6
The automation belongs to an account that lost access
What separates it It stopped on a date that matches someone leaving the home, a password change or a device being re-added. Automations are owned, and ownership is not always transferred when a device changes hands within the household.
How to confirm Check which account created the routine and whether that account still has permission to the devices it touches.
- 7
Two automations are fighting
What separates it The result flickers, or the last state does not persist. A schedule and a sensor rule that disagree will each keep applying their own outcome.
How to confirm Look for another routine touching the same device at an overlapping time. This is invisible from either routine's own screen.
- 8
The device was renamed or moved to another room
What separates it The automation exists and references something that no longer resolves. Renaming a device or moving it between rooms breaks rules that referenced it by name or by room.
How to confirm Open the routine and confirm each referenced device still resolves rather than showing a placeholder.
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.
- Whether the automation appears in the activity history at all at the expected time — this single check splits trigger problems from action problems.
- The exact time it should have run and the exact time anything happened, because an offset of whole hours is a time-zone answer.
- The full list of conditions attached to it, before any are removed.
- Which account created the routine, and whether that account still has access to every device it touches.
- Whether it fails always, or only overnight, or only when nobody is home — each points somewhere different.
- For presence triggers, each household member's location permission and background activity allowance.
Read the activity history before changing anything
ReversibleAn entry at the expected time means the trigger fired and the problem is downstream. No entry means the trigger never fired and nothing about the actions is worth investigating. This one look decides which half of the work is real.
Run every action manually, one at a time
ReversibleActions execute in order and a failure partway leaves a half-run routine. Running each alone identifies which one stops the chain, and that action almost always has its own separate fault worth fixing on its own terms.
Check the home's time zone and location, not the phone's
ReversibleThe home has its own location setting and it defaults to wherever it was created. Everything running at a consistently wrong hour, or sunrise and sunset landing wrong, is this and very little else.
Remove conditions one at a time and re-run
ReversibleConditions fail silently by design — presence, time window, sunset offset, another device's state. A routine that works with none and fails with one has told you exactly which condition is false at the moment it matters.
Verify presence permissions on every phone involved
ReversibleA geofence needs 'always' location rather than 'while using', and background activity has to be allowed. Battery optimisation defeats both silently, and the symptom differs per household member because the settings do.
Look for a second routine touching the same device
ReversibleTwo rules that disagree each keep applying their own result, which shows as flicker or as a state that will not persist. This is invisible from either routine's own screen and has to be looked for deliberately.
Confirm every referenced device still resolves
ReversibleRenaming a device or moving it between rooms breaks rules that referenced it by name or room. The routine still exists and still appears valid; it simply points at nothing.
Run it twice at the intended time and state
ReversibleOnce proves it can work. Twice, at the real trigger time and in the real household state, proves it does. Automations that pass a manual test and fail in life are failing on a condition that manual testing never reproduces.
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
- GA01318. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
- Camera
- A ⅓-inch 1.3-megapixel colour sensor with 6x digital zoom, shooting a 3:4 aspect ratio — portrait, not landscape. The tall frame is deliberate so a parcel on the step is in shot, and it is why footage from this doorbell does not match footage from a 16:9 Nest Cam of the same scene.
- Field of view
- 145° diagonal. Note this is a diagonal figure rather than separate horizontal and vertical numbers, so it is not directly comparable with cameras that publish 110° horizontal and 57° vertical.
- Video
- HD at 960 x 1280 pixels, up to 30 FPS, with HDR and H.264 encoding. That is a portrait resolution — 960 wide by 1280 tall.
- Night vision
- Up to 10 feet, from four 850 nm infrared LEDs with an IR cut filter. Ten feet is a short range, and it is the reason a subject clearly visible in daylight can be effectively invisible at night on this model. Google publishes it as a specification, not as a typical figure.
- Motion sensing
- A PIR motion and proximity sensor plus a magnetometer. PIR detects heat crossing its field, which is why this doorbell will not detect through glass and behaves differently in hot weather when the background approaches body temperature.
- Video history
- Up to 3 hours of event video history included. Up to 30 days with a Google Home Premium subscription, or up to 60 days on an Advanced plan. Google states explicitly that whether it is installed on battery or wired, the Nest Doorbell (battery) cannot record 24/7 continuous video.
- Power
- A built-in rechargeable Li-Ion battery, 6 Ah at 3.65V. It can alternatively use existing doorbell wiring for chime and recharging, which requires an 8–24VAC, 10VA, 50-60Hz transformer.
- Existing chime
- Google states that your existing wired doorbell chime will NOT ring when this doorbell is pressed. Notifications go to the phone and to compatible Google-enabled speakers and displays instead. This surprises people who hardwired it expecting the old chime to keep working.
- Wi-Fi
- 802.11a/b/g/n/ac on both 2.4 GHz and 5 GHz, with WEP, WPA, WPA2 and WPA3 supported, plus Bluetooth Low Energy. This is dual-band hardware — the usual 2.4-GHz-only smart-home constraint does not apply.
- 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, so instructions written for older Nest hardware do not apply.
- 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 Doorbell (battery) when it routine, schedule or automation is not running. 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 automation is relied on for anything safety-critical — heating for a vulnerable person, medication reminders, access for someone who cannot let themselves in. Consumer routines are best-effort and are not specified for that.
- !The controlling account is inaccessible and the routines cannot be edited or reassigned.
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 GA01318 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
Why does my existing doorbell chime not ring?+
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.
How far does the night vision reach?+
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.
Can the Nest Doorbell (battery) record 24/7?+
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.
Does it detect motion through a window?+
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.
Does the Nest Doorbell (battery) work on 5 GHz?+
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.
What transformer does it need if I wire it?+
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.
Why is the video a tall shape?+
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.
Can I use the Nest app with it?+
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.
How much video history do I get without paying?+
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.
The action works when I run it by hand but the routine never fires.+
That is the clearest possible evidence the action is fine and the trigger is not. Check the activity history — no entry at the expected time means nothing downstream is worth investigating, and running the action manually only confirms the part that already worked.
Everything runs an hour off.+
Check the home's own time zone and address rather than the phone's. The home has a separate location setting that defaults to wherever it was created, and an offset of a whole number of hours — or sunrise and sunset landing wrong — is almost always this.
My arrival routine fires late, or twice, or not at all.+
Geofencing depends on the phone, not the home. It needs 'always' location permission rather than 'while using', and background activity has to be allowed — battery optimisation defeats it silently. That is also why it behaves differently for different household members: their phone settings differ.
Half the routine runs and the rest does not.+
Actions execute in order, and one failing stops the chain. Run each action on its own to find which one fails alone — it will usually have a fault of its own worth fixing independently, and the routine will then complete.
It stopped working and nothing changed.+
Something usually did. Check for a device renamed or moved to a different room, a household member who left, a password change, or a device removed and re-added. Routines reference devices by name and room, and reference the account that owns them.
The light flickers between two states.+
Two automations are fighting over the same device — commonly a schedule and a sensor rule that disagree. Neither routine's own screen shows the other, so it has to be looked for deliberately by checking everything that touches that device in the same window.
Should I delete and rebuild the automation?+
Not before reading the history. A rebuild that happens to work teaches you nothing about which of the four parts failed, and the same cause will take out the next routine you build. Diagnose first, rebuild only if the routine is genuinely corrupt.
Can I rely on this for something important?+
No consumer automation platform is specified for safety-critical use. Trigger, condition, controller and action each fail independently and silently, and none of them alerts you when they do. Anything that matters needs a layer that is designed to fail loudly.
Why did it work when I tested it and not in real life?+
Because a manual test skips the conditions. Presence, time window, sunset offset and another device's state are all true when you are standing there testing and frequently false at the real trigger moment. Test at the intended time, in the intended household state, twice.
Does this answer apply to every Google Nest model?+
No. It is scoped to GA01318. Google Nest/Home device; Matter/Thread role, wired/battery power, subscription and Google Home migration vary.
What should I record before troubleshooting routine or automation?+
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 routine, automation. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not use consumer routines as the sole safety-critical control.
Answer for the exact device and software version shown above.