Google assistant on Sonos one not responding

Disconnect Spotify from Sonos and connect it again! It worked for me

I can’t get Sonos to recognize hey google at all. Have through the link process multiple times. Sonos shows in the google assistant and home apps. Voice control of Sonos is basically worthless. I tried Alexa but it never played on the correct speakers but at least it recognized my voice. 

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.

After multiple diagnostics over FB Messenger, which got escalated to phone and email correspondence, there’s still no resolution to this  . 

Have been in contact with them over FB Messenger, phone and email, and have performed all of the following:

• Unlinking and re-linking Google Assistant
• Pausing Voice and Audio Activity
• Connecting the speaker via Ethernet instead of wireless
• Connecting the speaker through a different wireless network with different ISP.
• Creating a brand new Google Account and linking it.

All of which Google Assistant still did not respond.

And then what was especially infuriating was when Support started asking me to repeat the same steps above right from the beginning. It was a new person by the name of Alanis who took over the case, who clearly did not look through the case history and past diagnostics logs. I requested for Alanis to look through the case history, but the reply back after that totally ignored my request and asked me to repeat step 1. I nearly combusted.

Anyhow, what worked however is when I tried connecting to Alexa, and it worked perfectly! This totally eliminated the possibility that it’s a hardware defect and it should be purely a software issue. I don’t know whether Sonos is working on a fix, but looking at how unhelpful Support is, I am starting to have my doubts.

I have the same problem