Google Nest Doorbells Experience a Quirky Identity Shift with New Accents

C. Scott Brown / Android Authority
Connect with Android Authority on Google:
Summary
- Users from various countries outside the United States are reporting that their Nest Doorbell is unexpectedly using an American accent during announcements.
- This anomaly appears to be limited to the Nest Doorbell, with other Google devices functioning normally.
- A user found a potential workaround by temporarily setting English (US) as a secondary language before removing it.
Recently, Google Home has experienced a series of technical glitches. The latest issue involves Voice Match, which has been failing to accurately recognize users. While the company is working on a solution for that, another unexpected problem has arisen, specifically affecting the Nest Doorbell.
Gemini for Home supports multiple languages, including English, French, German, Spanish, and Japanese, with options for various accents like US or UK English. It’s commonplace for users to choose the accent they are most familiar with. A sudden shift to a different accent in their language can be quite startling.
Reports from users on social media indicate that those with Nest Doorbell devices in countries such as France are encountering this issue. A user noted that they have set French as the language on their Google devices, which respond appropriately in French with a local accent. However, the announcements from their Nest Doorbell come in French but in a US accent.
Similar experiences have been reported by users in the UK, where Nest Doorbell announcements have unexpectedly shifted to a US English accent, while other interactions with Google devices remain consistent with the British accent.
One user claimed that the problem could be resolved with assistance from Google support. The reported fix involves temporarily adding English (US) as a secondary language, then removing it after a brief period, which allegedly restores normal functionality. It remains unclear whether this solution has been effective for others facing the same issue.
We have contacted Google regarding this peculiar issue and will update this article with any new information as it arises. In the meantime, we invite readers to share their experiences if they have encountered this bug.
Thank you for being a part of our community. Please review our Comment Policy before engaging.



