Google Home Nest Speakers Failing, Drop Outs and Intermittent Perfomance

[martinix]

As of today, performance on my Google Nest speakers has become unusable. I'm experiencing random dropouts, failures to reconnect, loss of audio on one side of a speaker pair, and forced reconnections to Google Home.

In the recent past, I've had a stable setup of Google Home/Nest with 7 speakers and fairly standard setup. It appears that something has changed to break this. There have been no changes with my internet connection, router or WiFi configuration. In addition I've had no problem with other services on my LAN. The problem appears to be specific to Google Home/Nest. I've checked speaker firmware - all are at the latest. I've done resets but the problems continue to occur.

Has anyone else been experiencing similar problems over the past few days? Is this a known problem? Is it something to do with the recent changes being rolled out to Google Home that have been published? Would welcome hearing from other folk and anything from Google about how to fix this. As of today Google Home is unusable with BBC Sounds and You Tube Music.

[martinix]

Problems continue. Completed complete reset. Speaker setups fail at last step 'wait a moment to complete'. Speakers show in Google Home and then partially work. Speaker pairing no longer possible. Groups not working. I've checked all Firmware versions. Google App at latest version. I've tried setup using both Samsung and Google Pixel phones. Basically Google Home / Nest no longer work. Are these problems due to the recent/on-going updates to Google Home. Google online support non-existent.

[martinix]

Further information. Setup of Nest always fails at last step 'Setting Up Nest Audio' with report 'There was a problem setting up Nest Audio' leaving two options 'leave setup' or 'help centre'. If you 'leave setup' speaker shows and there is limited functionality but some options (eg. create speaker pair/group do not fuction). Previously setup worked without problems. These issues have only started in the last 72 hours. Perhaps this reflects problems with the transition to 'new' Google Home. Is anyone else experiencing problems with Google Home in the recent past for a system configuration that has previously been working without problem? Would welcome any thoughts folk might have.

[virnab]

Hi martinix,

Thanks for reaching out to our community.

I understand that your previously stable setup of seven Google Nest and Home speakers has become unusable within the last 72 hours, despite no changes to your internet or Wi-Fi. You're experiencing a major breakdown, including random dropouts, loss of stereo pairing/grouping functionality, and setup failures that block full functionality. I appreciate the extensive troubleshooting efforts you've already tried to restore your speakers' functionality. Please do not worry, I'm here to help you find a solution.

Before I start further troubleshooting, let me ask you a few questions:

• What type of Google Nest or Home speakers do you have? Here is a Google Help Center article that can help you to identify your device: Google Nest and Home device specifications
• How far are the speakers from the Wi-Fi router?
• Are you trying to connect your speakers to the 2.4 GHz or 5 GHz Wi-Fi network?
• Are your speakers connected to the same network as your mobile devices?
• Where are the speakers placed? (By itself, up against the wall, next to a TV or audio speaker, or next to a microwave.)
• Are there any other networking devices on the network aside from the wireless router, such as an extender, repeater, or another access point?
• What is the current operating system version on your Samsung and Google Pixel phones?
• Are Location Services turned on for the Google Home app on your Samsung and Google Pixel phones? (To enable this, follow these instructions: On your smartphone, open Settings Tap Location → turn on Use location → Scroll down and tap App location permissions → Home → select Allow all the time).

Please reply with the requested information so we can continue troubleshooting and find a solution.

Best regards,

Virna