Direct answer
For the Nest Doorbell (battery), event capture, cloud processing, phone permission, Focus/background rules and alert zones are separate layers. First, trigger one repeatable event and compare event timestamp with alert time.
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: notifications are late, missing or excessive
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 phone's operating system is holding or silencing the notification
What separates it The event exists in the app's history with the right timestamp, but nothing appeared on the lock screen — or it appeared much later, in a summary. Focus modes, scheduled summaries, per-app notification settings and battery optimisation all do this silently.
How to confirm Compare the event's timestamp in the history with when the phone showed it. A correct event and a late or absent alert puts the fault entirely on the phone, and nothing done to the device will change it.
- 2
The device is asleep between events to save power
What separates it The first alert after a quiet period is late and subsequent ones are prompt. Battery hardware sleeps its radio and takes time to wake, transmit and be processed.
How to confirm Trigger two events a minute apart. A slow first and prompt second is a wake-from-sleep delay and is a designed trade, not a fault.
- 3
Alert-type settings do not match what is being triggered
What separates it Some events notify and others do not, consistently by type — motion alerts arrive but person alerts do not, or vice versa. The app's own alert settings are layered per device, per zone and per event type.
How to confirm Compare the event types present in the history against the alert types enabled. This is the most common cause of 'missing' notifications and involves no fault anywhere.
- 4
Motion zones or sensitivity exclude the event
What separates it Nothing appears in the history at all, which means the device never recorded the event — a notification cannot be missing if the event does not exist.
How to confirm An empty history for a known event moves this to a detection problem rather than a notification one, and the motion-detection record covers it.
- 5
A subscription feature lapsed
What separates it A specific class of alert — person, package, vehicle — stopped on a date, while basic motion alerts continue. Feature tiers gate alert types, not just recording.
How to confirm Check the plan's status and renewal date against the date the alerts changed. A feature that stops on a billing date is not a fault.
- 6
Network delay between the device and the provider
What separates it Alerts arrive in bursts after a delay, several at once, rather than individually late. The device is queuing events it cannot deliver.
How to confirm Compare the reported signal strength and the event timestamps. Bunched delivery is a transport problem; evenly late delivery is a processing or phone problem.
- 7
Excessive alerts from an environmental trigger rather than a person
What separates it Events cluster at particular times of day or in particular weather. Headlights, shadows moving with the sun, rain, insects drawn to an infrared illuminator and moving foliage all produce genuine detections of things nobody wants alerts about.
How to confirm Open the first frame of several unwanted events. What is in that frame identifies the trigger far faster than adjusting sensitivity blindly.
- 8
Several people share the device and each has their own alert settings
What separates it One household member gets alerts and another does not, from the same device. Alert preferences are per user, not per device.
How to confirm Compare the settings on each phone rather than assuming the device is configured once for everyone.
- 9
The app has been force-stopped or restricted in the background
What separates it Alerts stop after the phone was cleaned up, updated, or put into a battery-saving mode. An app that cannot run in the background cannot present a push notification reliably.
How to confirm Check the phone's background activity and battery optimisation settings for the app specifically. Aggressive power management on some Android builds does this by default.
- 10
Duplicate alerts from more than one integration
What separates it Every event notifies twice, from the manufacturer's app and from a linked platform. Both are working correctly; nothing is broken.
How to confirm Disable notifications in one of the two rather than changing device settings.
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.
- One repeatable, deliberate event — walk the same path at the same time — because a comparison needs a known trigger, not a remembered one.
- The timestamp of that event in the app's history, and the timestamp the phone displayed the alert. The gap between them is the single most diagnostic number on this page.
- Whether the event exists in the history at all. A missing event is a detection problem; a present event with no alert is a notification problem.
- The alert types enabled in the app, per device, compared against the event types actually being recorded.
- Whether other household members received the same alert, since preferences are per user.
- The phone's Focus, scheduled summary, per-app notification and battery-optimisation state at the time.
- The battery level and whether the device had been idle before the event.
- The subscription's status and renewal date if a specific alert class stopped on a specific day.
Trigger one deliberate, repeatable event
ReversibleWalk a known path at a known time rather than waiting for something to happen. Every comparison below needs a trigger whose real time you know, and a remembered event will not do.
Check whether the event exists in the history at all
ReversibleThis splits the problem in half and costs one look. No event in the history means nothing was detected, and the detection record applies instead — no notification setting can deliver an alert for an event that was never recorded.
Compare the event timestamp with the alert timestamp
ReversibleA correct event time and a late or absent alert puts the fault on the phone or the push path. Both times late puts it on the device or the provider. This one comparison decides which half of the remaining steps is worth doing.
Audit the phone's own notification settings before the app's
ReversibleFocus modes, scheduled summaries, per-app permissions and battery optimisation each suppress alerts silently and are the most common single cause. Check them explicitly rather than assuming they are as you left them.
Compare enabled alert types against recorded event types
ReversibleAlert settings are layered per device, per zone and per event type. Motion recorded but person alerts enabled — or the reverse — produces exactly the reported symptom with nothing actually broken.
Test two events a minute apart
ReversibleA slow first alert and a prompt second is a battery device waking its radio, which is a designed power trade rather than a fault. Consistent lateness on both is a different problem.
Compare settings across every account that uses the device
ReversiblePreferences are per user. One person receiving alerts and another not is a settings difference on the phone, not a device fault, and changing the device will not fix it.
Open the first frame of several unwanted alerts
ReversibleFor excessive alerts, what is in the first frame identifies the trigger — headlights, shadow movement, rain, insects at the illuminator, moving foliage — far faster than reducing sensitivity blindly and losing the events you wanted.
Change one setting at a time and retest with the same event
ReversibleSensitivity, zones and alert types interact. Changing several at once produces a result that cannot be attributed, which is how a working configuration gets tuned into a broken one.
Verify with the phone locked and away from home
ReversibleNotification behaviour differs between an unlocked phone on the home network and a locked phone on cellular data. Only the second test reflects how the alert will actually reach you.
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 notifications are late, missing or excessive. 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.
- !Critical security or safety alerting is unreliable after the checks above. Consumer push notification is a best-effort service and should not be the only layer for anything that matters.
- !Alerts stopped on a subscription renewal date and the plan shows a billing failure — that is an account matter, not a device one.
- !The device records events correctly and the provider consistently fails to deliver them, which is a service fault only the provider can see.
- !Events are missing from the history entirely and the camera's view or power is compromised — that is a detection or hardware problem, not a notification one.
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 "Troubleshoot Nest camera alerts and notifications". Google's own camera/doorbell alert-and-notification troubleshooting article. Verified reachable and title-matched via the Browser tool 2026-08-28. 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.
Alerts arrive minutes late. Where is the delay?+
Compare the event's timestamp in the history with when the phone showed it. If the event time is correct, the delay is entirely on the phone or the push service, and nothing you change on Nest Doorbell (battery) will help. If the event time itself is late, the delay is at the device or the provider.
I get no alerts but the recordings are all there.+
That is the cleanest possible split: detection and recording work, delivery does not. Check the phone's Focus modes, scheduled summaries and per-app notification permission first — they suppress alerts without any indication that they are doing so.
Why is the first alert of the day always slow?+
A battery device sleeps its radio between events and needs time to wake, associate and transmit. The first event after a quiet period pays that cost; the second one a minute later does not. Testing two events a minute apart confirms it in under two minutes.
My partner gets the alert and I do not.+
Alert preferences are per user account, not per device. Two phones on the same device routinely have different settings, and the device is configured correctly for one of you. Compare the two phones rather than changing the device.
I get far too many alerts. Should I reduce sensitivity?+
Not first. Open the first frame of several unwanted events — what is in that frame names the trigger. Headlights, shadows tracking the sun, rain, insects at the infrared illuminator and moving foliage each have a specific fix, and blanket sensitivity reduction loses the events you actually wanted.
Person alerts stopped but motion alerts still work.+
That pattern is a feature tier, not a fault. Person, package and vehicle detection are subscription-gated separately from basic motion. Check the plan's renewal date against the date the alerts changed.
Alerts arrive several at once after a gap.+
Bunched delivery means the device queued events it could not deliver and then flushed them. That is a transport problem — signal or provider — rather than a notification setting. Evenly late delivery would point somewhere else entirely.
Does Do Not Disturb block these?+
Yes, along with Focus modes, scheduled notification summaries, per-app permission changes and battery optimisation. All of them suppress alerts silently, which is why the phone should be audited before the device.
I get every alert twice.+
You almost certainly have the manufacturer's app and a linked platform both notifying. Nothing is broken. Turn notifications off in one of them rather than changing anything on the device.
Alerts stopped after I updated my phone.+
Operating system updates reset per-app notification permissions and background activity limits more often than people expect. Check the app's notification permission and its background activity allowance specifically — a restricted app cannot deliver a push reliably.
How do I test this properly?+
Walk one deliberate, repeatable path at a known time, with the phone locked and on cellular data rather than Wi-Fi. Anything less realistic than that produces a result that does not match how the alert will actually reach you.
Should I reinstall the app?+
Rarely necessary and it loses your per-device settings. Work the timestamp comparison first — it identifies the layer in one step, and a reinstall that happens to fix things teaches you nothing about which layer was at fault.
Nothing appears in the event history either.+
Then this is not a notification problem at all. An alert cannot be missing for an event that was never recorded, and the investigation belongs with detection — zones, sensitivity, lighting and power — rather than with alert settings.
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 notifications or alerts?+
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 notifications, alerts. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Preserve critical security/safety alerts and privacy.
Answer for the exact device and software version shown above.