Google assistant on Sonos one not responding

Sadly having the exact same issues. Removing the entire history doesn’t seem to make any difference. Google Home speaker flawlessly picks up every response, while my two €200 Sonos One’s are having difficulties understanding anything that’s said after ‘Hey Google’ (and having no problems catching ‘Hey Google’…)

Hello @mjanssen. Welcome to the community. Please Submit a diagnostic from your system, and reply back with that confirmation number. 

I’m jumping on this thread, as I also have huge problems with Google Assistant on Sonos One.

My experience is as follows:

When saying “OK Google” the Sonos One always responds with the ready beep. Never any problem here.

When speaking one of three things happen:

1. The light blinks (processing) for a few seconds, and then goes dim without any response.
2. The light stays on even though I stop speaking. After 3-5 seconds it goes dim without any response.
3. About 10 % of the time, the light blinks (processing) and I get a proper response.

I have tried speaking the same commands to Google Assistant on my phone, without any problems.

I bought the Sonos One late October 2019, and at that point it worked perfectly. It seems like the service deteriorated about a month later to the current unuseable condition. 

I have submitted a diagnostic with ID 1461227675

Hello everyone. @DonSahl, welcome to the community, and thank you for submitting that diagnostic. 

Thanks for the update. Our team is investigating and working with Google on implementing a fix. It seems like this is only prominent on Sonos One Generation Two’s. If you have a Generation One, or a Beam, then Assistant should work from those devices. Alternatively, you can add Alexa to your speakers to use voice control, as it is unaffected. We will update this thread when we have more information to share. Let me know if you have any questions. 

Thanks for the reply @Richard F. 

I just submitted the diagnostics with the following ID: 848074575. Hope Sonos is able to figure out what's up :)

Also, during daytime I seem to have a lot more problems getting the assistant working than during nighttime. I'm not sure if it's just a coincidence, but just letting you know :)

I have the same problem @Richard F. And have just submitted diagnostics for it #530986622

Hi All

Just a thought but if any of you have booted your router whilst trying to resolve this issue, you may now have duplicate IP addresses.  

As a general comment, when trying to resolve Sonos issues with either Alexa or Google and you feel the need to reboot the Router, it is ALWAYS advisable to reboot ALL connected devices within the home.

For those of you reading this that aren't totally clear on how this works, I’ll try and explain below:

• Each time a new device connects to your Wi-Fi or is plugged into an Ethernet cable, a device (normally your Router) allocates it a unique network (IP) address;
• Normally this address is in the format of 192.168.0.1 (This specific address is normally reserved for the Router) and then the next device to connect is allocated the next number - 192.168.0.2 and so on;
• The issue occurs when the Router is rebooted, as the Router then loses any knowledge of the addresses previously allocated and so will start from 192.168.0.2 again;
• Any devices within your network that have not been rebooted at the same time will continue to use the IP address that they were allocated before the Router was Rebooted;
• So, an example scenario of a household with 20 connected devices, including 5 Sonos devices would mean that the next device to connect would be allocated 192.168.0.22 and all is stable. However, as soon as the Router is rebooted and the previously allocated addresses are lost, the Router will then allocate 192.168.0.2 to the next device – meaning that there are now two devices with the same IP address within the Network.  If the Sonos devices are then rebooted, these will also be allocated addresses that had previously been allocated before the Router was rebooted and so the problem gets worse;
• For standalone devices, this can often go unnoticed by the user but for devices that need to communicate with each other (Sonos, Alexa and GA devices) this will cause a lot of seemingly unrelated performance and functional issues;

The ONLY way to resolve this issue is to reboot your network in this order:

• Router
• Any wired Network devices or switches;
• Any other wired devices;
• All other Wi-Fi devices (Turning Wi-Fi off and on again on each device would also work)

The way that you can reduce the effect of this problem is to reserve an IP address within your Router Set-Up for all permanent devices. This ensures that a device is never just allocated the next IP address that the Router ‘thinks’ is free.  I personally use the range 192.168.0.175 – 192.168.0.244 for my devices that are connected to my network on a regular basis.  This removes the requirement to reboot these devices whenever the Router is rebooted, as they will always be allocated the exact same address and the Router will NEVER allocate this address to another device.

@UKMedia I’m not entirely convinced that the router connection could be causing this issue. I have had no issues playing music trough the Sonos app, only having issues with the Google Assistant. @DonSahl stated the exact same issue as I have, where the assistant worked fine and all the sudden did not pick up 2/3 commands, but always catching ‘Hey Google’ or ‘Ok Google’.

The only reason I mentioned it was, it fixed a similar situation that I had with Alexa and so thought it may be worth trying.