First-Gen Google Nest Doorbells Hit by Widespread Live View Outage in Google Home App

A frustrating technical issue is impacting owners of Google’s original smart video doorbell, leaving live video feeds completely broken for numerous users within the Google Home application. Weeks after initial reports began trickling onto community forums, the problem appears to have escalated significantly, leaving affected customers unable to monitor real-time video from their front porches, and so far, Google has not provided an official timeline for a resolution.

The glitch specifically targets the first-generation wired video doorbell, widely recognized and beloved by consumers as the "Nest Hello." While Google has formally referred to the hardware model in recent documentation as the "Nest Doorbell (wired, 1st gen)," the branding matters little to the growing cohort of users who are suddenly finding themselves staring at endless loading screens or black boxes instead of their live camera feeds.

Frustration has boiled over across multiple online communities, including Reddit and the official Google Nest Support forums. While early complaints began surfacing in isolated threads weeks ago, the volume of user reports has surged dramatically over the past few days. Nearly a dozen distinct support threads have popped up recently on Google’s community boards, filled with complaints from long-time owners who are suddenly losing core functionality on devices that have otherwise served them reliably for years.

While the vast majority of complaints center squarely on the first-generation wired doorbell, some users have also reported erratic behavior or streaming failures on other legacy first-generation Nest camera hardware. However, those collateral issues appear far less widespread compared to the persistent stream failures plaguing the Nest Hello doorbells.

The timing of the outage has naturally drawn scrutiny from the smart home community. Just weeks prior, at the end of October, Google rolled out a software update aimed at older Nest hardware. While updates are generally intended to patch vulnerabilities, improve performance, or prepare devices for modern ecosystem integrations, users and tech analysts are left wondering if this recent firmware deployment inadvertently introduced the current streaming bug.

Adding to the confusion is the selective nature of the malfunction. Interestingly, users who are impacted by the missing live view in the Google Home app note that other secondary integrations continue to function normally. For instance, physical doorbell presses and motion notifications routed to Nest Hub smart displays are still functioning properly, allowing homeowners to receive alerts and even view temporary snapshots or video streams locally in certain contexts. This discrepancy has led some tech-savvy users to dissect the backend behavior of the app.

Based on community troubleshooting and technical observations, some users have deduced that Google’s ongoing backend migration and switch to WebRTC—a protocol designed to enable peer-to-peer real-time communications for web browsers and mobile applications—might be the underlying root cause of the problem. Unfortunately, theory has not easily translated into practical solutions. Workarounds proposed by community members attempting to force compatibility or bypass the WebRTC routing do not reliably work for everyone, leaving the vast majority of affected customers entirely dependent on an official software patch from Google.

As of now, Google has yet to issue a formal public statement acknowledging the bug or detailing a targeted fix. Users reaching out through standard channels have primarily encountered generic troubleshooting advice, such as restarting the device, clearing app cache, or reinstalling the Google Home application—steps that ultimately fail to resolve what is clearly a server-side or ecosystem-level software incompatibility. Given the mounting volume of support tickets and forum complaints, the evidence strongly points to a problem originating on Google’s end rather than individual hardware failures.

As the situation develops, affected smart home owners continue to look toward the tech giant for answers. For now, the smart home community waits in limbo, hoping for a swift backend adjustment or app update to restore live visibility to their front doors.