Nest Doorbell live video not working: causes and fixes

Owners of the original wired Nest Doorbell, sold since 2018 as Nest Hello, are reporting that Nest Doorbell live video is not working in the Google Home app. Live view opens to a black screen or spins indefinitely, while some affected owners say recordings and alerts continue arriving as usual (MondoAndroid).

9to5Google found nearly a dozen Google support threads describing the same symptom this week, following scattered Reddit complaints that date back several weeks. Google has not confirmed a cause, scope, or fix timeline, and has so far only pointed affected users to generic troubleshooting replies (9to5Google; MondoAndroid).

What follows breaks down what the reports actually establish, what keeps working despite the glitch, why a late-October software update is a lead rather than a confirmed cause, and how to check whether your situation matches the pattern before you reset or replace anything.

Is this a Nest Doorbell wired 1st gen live view issue?

The reports consistently center on the first-generation wired model, which Google's own app now labels "Nest Doorbell (wired, 1st gen)" (MondoAndroid; 9to5Google).

German retailer blog tink separately reports the same failure on Nest Cam IQ indoor and outdoor cameras, which would push the pattern beyond doorbells. 9to5Google, though, says it turned up only limited reports involving other Nest cameras, so that broader scope isn't established yet (tink; 9to5Google).

No outlet has published a count of affected units or a share of the installed base. "Nearly a dozen" support threads and scattered individual reports add up to a real pattern worth tracking, not a confirmed device-wide outage.

What still works when live view won't load

Motion notifications keep arriving for many affected owners even when the live stream refuses to open (MondoAndroid). Recorded event clips remain viewable for a portion of affected users too. MondoAndroid's explanation is that clips travel through a different delivery path than the live stream, though that's the outlet's own account rather than a technical confirmation from Google.

Nest Hub display notifications are also reported to keep functioning normally, according to 9to5Google. That's a useful clue, not proof: it suggests the failure sits with the real-time stream rather than the doorbell's full detection pipeline, but no source has confirmed that mechanism directly (9to5Google).

A separate thread on the Google Home Community, posted roughly two months ago, describes a different second-generation wired doorbell losing live view across multiple devices and the web portal while recordings kept working. The owner reported that disconnecting and reconnecting power restored the feed (Google Home & Nest Community). It's a useful illustration that individual live view failures can happen in isolation, but it predates the current reports and involves different hardware. Treat it as a troubleshooting data point, not evidence about what's causing November's pattern.

Does a late-October software update explain this?

Google pushed new software to older Nest hardware around October 29, shortly before support-forum reports picked up (tink; 9to5Google). The timing looks suggestive, but scattered Reddit complaints reportedly stretch back weeks before that release, which keeps the update from being a clean standalone explanation (MondoAndroid).

The release notes themselves don't help the theory much either. They reportedly addressed cameras hanging after brief Wi-Fi interruptions and, specifically for Nest Hello, audio and video sync problems. They make no mention of a live view outage (tink).

A theory connecting the failure to Google's shift toward WebRTC streaming is circulating among affected users, but it remains exactly that: a theory. MondoAndroid reports that workarounds built around it are unreliable, with video returning briefly before failing again, which is not what you'd expect from a verified fix (MondoAndroid).

How to check before you reset anything

Confirm your device first. The reports so far center specifically on the wired first-gen Nest Doorbell, also known as Nest Hello. If you own a battery-powered model, a 2nd- or 3rd-gen wired doorbell, or a device that's offline entirely, the current reporting doesn't point to your hardware. It's worth ruling out standard causes, like weak Wi-Fi signal or a stuck app cache, before assuming you're part of this cluster (MondoAndroid).

Check recordings and notifications. If recent event clips still load and chime or motion alerts are still arriving, your symptom matches what affected owners describe: a detection pipeline that works paired with a live stream that doesn't (MondoAndroid).

Test from a second device or account. A single-device or single-app glitch is a different problem than what's being reported. The idea of checking across multiple phones, accounts, or the browser portal comes from the September community case involving a different wired model, but it's still a reasonable way to rule out a one-off issue on your own setup (Google Home & Nest Community).

Rule out a local or offline problem. If the camera shows as offline in Google Home, if live view returns a specific error or timeout message, or if the failure only happens on one phone, that points toward a local network, app, or device issue rather than the broader reported pattern. A Wi-Fi check, app update, or standard restart is the more relevant next step in that case.

Try a basic restart before anything drastic. In the September case, the owner's fix was a brief power disconnect and reconnect, not a factory reset. That worked for a different doorbell under different circumstances, so treat it as a low-risk thing to try rather than a confirmed fix for the current reports. If you're unsure how to safely power-cycle your specific model, check Google's own Nest support documentation before pulling power.

Hold off on a factory reset or hardware swap unless Google Support specifically directs you to one. MondoAndroid reports that resets don't appear to touch what's suspected, though not confirmed, to be a server-side delivery problem. Resetting a device that's already recording and alerting normally risks losing settings for no clear benefit (MondoAndroid).

What to do now

As of this week, Google has not publicly confirmed the live view issue, named a cause, or given a fix timeline. Its public responses remain standard troubleshooting replies (9to5Google; MondoAndroid). tink's report that Google is privately aware of the problem and working on a fix hasn't been echoed by any on-record statement elsewhere, so treat that claim as unconfirmed for now (tink).

If you own the first-gen wired Nest Doorbell and your recordings and alerts still work while live view doesn't, run through the checks above, try a basic restart, and log your report through Google's support forum so it's counted as part of the pattern Google is seeing. Skip the factory reset and skip buying a replacement until Google says otherwise, and watch the Google Home app's release notes for any mention of a fix, since that's where tink expects one to appear.