Header Banner
Gadget Hacks Logo
Gadget Hacks
Android
gadgethacks.mark.png
Gadget Hacks Shop Apple Guides Android Guides iPhone Guides Mac Guides Pixel Guides Samsung Guides Tweaks & Hacks Privacy & Security Productivity Hacks Movies & TV Smartphone Gaming Music & Audio Travel Tips Videography Tips Chat Apps
Home
Android

Nest Doorbell American Accent Bug: Google Confirms a Fix Is Coming

"Nest Doorbell American Accent Bug: Google Confirms a Fix Is Coming" cover image

Some Nest Doorbell owners outside the US are hearing their doorbell announcements delivered in an American accent even though other Google Home interactions on the same account still match their configured language or dialect.

The symptom isn't identical across every report. Some users describe an accent change while the spoken language stays the same, while at least one separate report describes a full switch to US English. Google has acknowledged the problem and said it is working on a fix, but it has not provided a cause, timeline, or affected-model list.

Android Authority reported on Sept. 22 that an official Google account had responded to complaints and confirmed the issue was being worked on. 9to5Google reported the same day that no fix had rolled out.

Google's Sept. 30 Home release notes don't list a fix for the accent problem, so there is still no documented confirmation that the issue has been resolved.

What the Nest Doorbell American accent bug sounds like

A user in France reported that Gemini continued replying in French with a French accent during normal Google Home interactions, but doorbell announcements switched to French spoken with a strong American accent, according to Android Authority.

UK users reported similar behavior, with their usual British voice changing specifically for doorbell announcements.

9to5Google also highlighted a related report in which Gemini switched fully to US English rather than simply changing accents. The same report noted another user in the Netherlands whose Bosch washing-machine alerts were delivered in US English instead of Dutch.

That points to two related but distinct behaviors: an accent-only shift for some users and a full language-and-accent switch for others.

Neither Android Authority nor 9to5Google puts a number on how many homes, models, or regions are affected, so this is a documented pattern rather than evidence of a widespread problem across all Nest Doorbells.

Where the bug fits in Google's Gemini for Home rollout

Gemini for Home is still in early access, but the program is no longer limited to the US.

Google currently lists early access to the Gemini for Home voice assistant in 20 countries, including France, the Netherlands, the UK, Germany, Canada, Australia, Japan, and the US. Supported languages include French, Dutch, English, German, Italian, Japanese, Spanish, Swedish, Danish, and Norwegian.

Google says once a home is upgraded to Gemini for Home, compatible devices in that home use Gemini for Home instead of Google Assistant.

That makes the reported cases in France, the Netherlands, and the UK consistent with markets where Gemini for Home is officially available in early access.

Neither Android Authority nor 9to5Google has tied the accent bug directly to one particular Nest Doorbell generation, firmware version, or language rollout. The reports also don't establish whether the same problem occurs on homes still using Google Assistant rather than Gemini for Home.

What Google has confirmed, and what it hasn't

Google has confirmed that it knows about the problem and is working on a fix.

Android Authority quotes a Google response saying the team is aware of the issue and is actively working on a fix, with an update promised once that fix has rolled out.

That acknowledgment came through a response to user reports rather than a formal support bulletin, and it did not include a release date, technical explanation, or list of affected devices.

9to5Google suggested the problem may have appeared after a September Google Home update, but that remains speculation. Google's Sept. 16 release notes listed Gemini changes including improved follow-up behavior, TV playback fixes, fewer Live Mode interruptions, and reduced broadcast errors, but nothing involving doorbell accents.

Google published another set of Home release notes on Sept. 30. Those included improved multilingual recognition, faster voice responses, camera and doorbell tile changes, and several other fixes, but again did not mention this accent or language-switching bug.

That doesn't prove the bug is still affecting every user who saw it previously. It does mean Google has not publicly documented the promised fix as shipped.

The unverified workaround some users are trying

One user told Android Authority that temporarily adding English (US) as a secondary language, waiting a few seconds, and then removing it restored the expected accent.

That's a single-user workaround, not a fix Google has officially published or validated.

Another user described resolving a related Google Assistant problem after working directly with Google support. That doesn't establish that the same steps apply to Gemini for Home or to every Nest Doorbell setup.

There's also no evidence showing how consistently the secondary-language workaround works, how long the result lasts, or whether it behaves the same way across different doorbell generations or account configurations.

If you try it, trigger an actual doorbell announcement afterward rather than assuming the voice setting has changed permanently.

What Nest Doorbell owners should do now

If you're hearing the problem, compare a Nest Doorbell announcement with another Gemini for Home interaction on the same speaker or display.

If ordinary responses use your configured language and voice but doorbell announcements switch to a US accent or US English, that matches the pattern users reported in September.

The secondary-language workaround is optional and unverified. There's no need to reset the doorbell or make more disruptive changes based on the available reporting.

Google says a fix is in progress, but it has not given a timeline, and its Sept. 30 release notes don't identify the issue as resolved.

For now, keep an eye on Google's Home release notes and test the doorbell again after future Gemini for Home updates. Until Google names the fix in a changelog or confirms the rollout, there isn't enough evidence to say the bug has been fully patched.

Apple's iOS 26 and iPadOS 26 updates are packed with new features, and you can try them before almost everyone else. First, check our list of supported iPhone and iPad models, then follow our step-by-step guide to install the iOS/iPadOS 26 beta — no paid developer account required.

Sponsored

Related Articles

Comments

No Comments Exist

Be the first, drop a comment!