Older Nest Doorbells Are Losing Live View, and Google Hasn't Named a Cause

What owners are seeing

Owners of older Nest doorbells are reporting a Live View failure that Google hasn't explained. Live View is the feature that lets you pull up a live feed from your phone whenever you want, instead of waiting for a motion clip to show up in your history. When it breaks, the camera still does part of its job, but you lose the thing many people bought it for. And at least one person says their attempted fix made things worse, which should make anyone with this hardware pause before touching settings.

The complaints are piling up in a thread on the Google Home subreddit. One user says Live View has been down "for over a week now for older Nest doorbell cams," while their newer wired outdoor camera works fine. That split matters. It points toward a problem tied to hardware generation rather than a broad outage. Faults like this are often easier to pin down than a general service failure, but they're also easier to ignore, because the affected group is a smaller slice of the user base.

The original post is the clearest summary of the problem, and it's short enough to read in under a minute. The poster isn't asking for a theory. They're asking whether anyone else is seeing the same thing, which is the question that tends to surface real patterns in a support forum.

When that user raised it with Google, the reply was a general acknowledgment: "we are aware of many issues." That's a carefully vague answer. It confirms the company knows something is wrong without saying what, which tells owners nothing about whether a fix is coming or what they should do in the meantime. Acknowledgments like this are common in support channels, and they're usually a holding pattern rather than a diagnosis.

Other owners then shared their own experiences. One Nest Doorbell stopped streaming a few days ago, but it still sends movement alerts and clips. The camera sees motion, just not in real time. (And this is the part most people overlook: the alerts still working can make the problem look smaller than it is, since you'd only notice the missing live feed the next time you tried to check on your front door.) Hard to say how many owners are in that situation, since the thread is anecdotal.

When the fix backfires

Google has asked affected users to work through its standard troubleshooting steps, but by most accounts that hasn't resolved anything. That's the normal first move for support teams, and it's reasonable as a starting point. The trouble is that when a fault is tied to a specific hardware generation, generic steps tend to miss the cause, and owners are left to decide how far to push on their own.

The worst report comes from an owner of an older Nest Cam whose Live View broke. They used the pinhole reset on the back of the unit, and the result was blunt: "...now the unit is dead." Hardware resets are usually the last rung on the troubleshooting ladder for a reason. They're designed to fix serious problems, and they carry more risk than a simple restart. I wouldn't read one anecdote as proof that the reset caused the failure. Still, it's exactly the kind of outcome that makes people hesitate before trying it.

Another report describes an Arlo camera hitting the same Live View bug. That's the detail I find most interesting in the thread. Arlo is a different brand, so a shared symptom across two companies suggests the trigger may sit in shared streaming infrastructure or firmware. Though the thread doesn't confirm a root cause, and I wouldn't treat a handful of anecdotes as proof. Two reports are a pattern worth watching, not a diagnosis.

Then came a twist. One commenter says Live View has started working again. It's unclear whether Google pushed an update. If it did, the company didn't list it in its changelog. That's a problem even if the fix is real, because owners who got it back have no way to know what changed. Without a changelog entry, you can't tell whether your camera is fixed for good or just working until the next unannounced change.

Why this feels familiar

This isn't the first rough patch for Nest hardware. Earlier, first-gen Nest doorbells and cameras reported an offline bug shortly after owners migrated from the Nest app to the Google Home app. The offline error stripped out many features. Live feeds went dark, and doorbell ringers connected to speakers stopped working. That history matters here because it suggests older devices sometimes get caught in transitions between software platforms, where the newer system and the older hardware don't fully agree on what they're doing.

Google Home and Nest speakers and displays have had their own stretches of unresponsiveness, sometimes failing to answer the most basic questions. Those episodes are different in kind, but they share a theme: the smart home stack has many moving parts, and a fault in one layer can look like a fault in another. A camera that won't stream might be a device problem, an account problem, or a server problem, and owners rarely get enough information to know which.

Google's late-October Google Home, Nest, and Gemini for Home update leaned heavily on Gemini and Matter fixes. Its Nest entries covered Nest Wi-Fi and speakers. Nothing addressed doorbell or camera streaming. That's a telling omission. Release notes reflect what a company chooses to highlight, and when a known complaint about a product line doesn't appear, owners reasonably assume it wasn't on the list. It doesn't prove the update ignored the bug, but it doesn't help the people waiting on it either.

What this means for you

If you're running an older Nest doorbell or camera, the practical takeaway is simple: be careful with anything that resets the hardware. Live View failing is annoying. A dead camera is worse, and right now the evidence for a fix is thin. Check whether your alerts and clips still arrive, since that tells you the device is at least recording events even if the live feed is broken.

Your newer devices may be fine, as that original poster's wired outdoor camera was. But don't assume the whole ecosystem is healthy just because one model is working. The split in the thread suggests the fault follows hardware generation, and that's the kind of problem that can show up on your next device purchase too, if you're mixing old and new gear in the same home.

Here's what I'll be watching. Does Google name a cause, or does it quietly ship a fix and hope nobody notices? Silent updates make it hard for owners to know what changed, and that's a bigger issue for older hardware that's already past its prime. If the company wants to rebuild trust with people who have older cameras, a short, specific explanation would go a lot further than another general acknowledgment. Until then, the most useful thing you can do is keep a record of what's broken, when it broke, and what you tried. If the fix comes, you'll want to know what it fixed.