Skip to content
Smart Home

Nest Doorbell (wired, 2nd gen): Notifications Arriving Late or Not at All

Notifications Arriving Late or Not at All on the Nest Doorbell (wired, 2nd gen): what we found on our own £179 unit, the checks that resolve it, and when it is a warranty case rather than a setting. M...

Tom Halvorsen 4 min read 2,206 views
Nest Doorbell (wired, 2nd gen): Notifications Arriving Late or Not at All

What is happening

Nest Doorbell (wired, 2nd gen), video 1440p HDR, 3:4 aspect. Notifications Arriving Late or Not at All is the fault being chased here, on a unit bought and tested rather than loaned. It is genuinely good at three hours of history without paying, and the thing that repeatedly cost it marks was event history beyond three hours needs a subscription.

Messages appear only when you open the app, sometimes hours after they were sent. That is the behaviour; what follows is how it tends to present on this particular Google, and what to rule out first.

First, a note: Work through these in order. The first two resolve the majority of cases and neither risks your data.

Start here

CheckWhy it matters
Is it reproducible?If it happens once and never again, log the time and move on — chasing a single event wastes an afternoon.
Has anything changed?A firmware update, a new app, a new accessory. The cause is almost always the most recent change.
Does it happen on a fresh restart?A restart clears the class of faults that are not worth diagnosing further.
Is it under warranty?The Google warranty makes some of the steps below unnecessary — check before you start pulling things apart.

The full procedure

  1. Check whether battery optimisation is enabled for the affected app and exempt it.
  2. Confirm background data is permitted, particularly on a metered connection.
  3. Check Do Not Disturb and any focus or schedule modes that may be filtering silently.
  4. Reinstall the app so its push token is reissued.
  5. Verify the device clock is set automatically — a skewed clock breaks push delivery.

When that is not enough

If several apps are affected at once, the push service connection itself is failing and a reset is the practical fix.

Preventing a repeat

Exempt genuinely time-sensitive apps from aggressive battery optimisation when you install them.

What usually causes this

In our experience this is rarely a single fault. The common pattern is an accumulation: a background process that was fine on its own, a setting changed months ago, and — on the Nest Doorbell (wired, 2nd gen) specifically — event history beyond three hours needs a subscription, which narrows the margin before anything else goes wrong. That is why the steps above start with the cheap reversible checks: on a Google device the expensive diagnosis is almost never the one you needed.

What makes it worse

  • Do not change several settings at once — you will fix it without ever learning what caused it, and it will come back
  • Do not install a third-party "optimiser" — on modern hardware these do nothing the operating system is not already doing
  • Do not factory reset before backing up, and do not restore that backup immediately afterwards; if the cause is in the backup you have simply reinstalled it
  • Do not leave it on charge overnight as a workaround for event history beyond three hours needs a subscription — it treats the symptom and shortens the life of the cell
  • Do not open the case while it is under Google warranty; that is the one step you cannot undo

When it is a hardware fault

If the behaviour persists after a factory reset, it is worth raising with Google under warranty rather than working around it. Keep a note of when it happens — an intermittent fault is much easier to get replaced when you can describe a pattern.

Behind this piece

How we tested this — Nest Doorbell (wired, 2nd gen): Notifications Arriving Late...
How Tech Daily Review tests the hardware it writes about.

Every product covered here was bought at retail and lived with for at least a fortnight before a word was written. Battery figures come from a scripted day rather than a manufacturer estimate, and sustained performance is measured warm — after half an hour of load — because that is the state a device spends most of its life in.

Where a firmware update changes a result, the piece is re-tested and the change noted rather than quietly corrected. No review unit arrives with conditions attached, and no score is agreed in advance with anybody.

Where to go next

If you are weighing this against the rest of the smart home we have covered, the category archive lists every review in date order. The closest comparisons we have published are Nest Doorbell (wired, 2nd gen): Screen Becomes Unresponsive in Places and Nest Doorbell (wired, 2nd gen): Storage Full but Nothing Obvious to Delete.

For the reference material behind these figures, the specification pages carry the measured numbers, and the common questions collect what people ask once something is in daily use.

Frequently asked questions

Messages appear only when you open the app, sometimes hours after they were sent. If several apps are affected at once, the push service connection itself is failing and a reset is the practical fix.
Often, but try the earlier steps first — a reset costs you an afternoon of setup and rarely tells you what the cause was.
An hour. If the steps above have not moved it in that time, the remaining causes are ones a workshop diagnoses faster than you will.
It is consistent with the one weak point we found in testing — event history beyond three hours needs a subscription — which narrows the margin before anything else goes wrong.
Nothing above will. Anything involving opening the case would, so stop at that point and talk to Google instead.

Tom Halvorsen

Cameras and lenses. Shot weddings for a decade before deciding that reviewing the gear was less stressful than relying on it. Still carries two bodies everywhere.

Please login to comment.

Comments (0)

No comments yet.

Keep reading