Google assistant on Sonos one not responding

Hey @Richard F. - got any updates for us regarding this issue?

Nice to see that this thread is still going strong and that, even better, Sonos staff are now involved (thanks @Richard F. ) 

I originally posted, some months ago, that pausing Voice & Audio Activity controls solved the problems with GA. It did, but only for about 2/3 months then, around Xmas time, I encountered all the problems mentioned here and tried all the solutions (I even changed my router) but nothing solved the issue. At best, GA would respond to the first command of the day but after that, nothing.

I’ve had to change the voice assistant for Sonos to Alexa which works flawlessly. However for me, that’s not a solution. I have Andriod phones and tablets and a couple of other Google Assistant enabled portable speakers. I held off buying any new Sonos speakers until GA was included. So I now have some gear that responds to Google Assistant and Sonos that will only work with Alexa - hardly the fully integrated system I was hoping for. So I really hope Sonos do sort this out and I can go back to using GA throughout. I have to say that it does now seem there’s a chance of this happening which, when I originally posted here, didn’t seem that likely. Fingers crossed :)

Hey, guys just want to make this thread stronger.

Having the same issue with GA as you guys. My Sonos One is 2 days old and I am very disappointed. GA understands only the Hey Google and after that in the history I can see Unknown Voice Command.

This is the primary reason that I have bought Sonos. I hope Sonos are on to it.

Hello everyone. I know how frustrating this can be for you. We are still working on this issue with Google. We will update this thread when we have more information to share. Thank you for your patience. 

I’ve also had plenty of trouble with this problem recurring several times over the last several months. Everything will be working fine, then gradually GA on Sonos starts not getting commands (1 minute delay, then “there was a glitch/something went wrong”. Gets worse and worse.

It’s a popular theory that it might be due to a local IP address conflict, but it isn’t. Scratch that explanation from the list.

The first time this happened I tried rebooting the router and the Sonos speakers - no good. I tried disconnecting anything else on the network that has anything to do with Google (Google Home speakers, Android phones and tablets) - no good. I tried unpairing the stereo pair and turning off the 2nd speaker - no good. I tried connecting to ethernet instead of WiFi - no good. I tried connecting to a different router on a different LAN - that cured the problem, but it came right back when I reconnected the Sonos to my regular LAN. Finally one day there was a general power failure, and when power came back the entire LAN rebooted in random order, probably changing the Sonos LAN IP address and many others - and the problem was cured, for about a month before it started again.

It is totally understandable why one would think that this could be an IP address conflict. It was practically the first thing I thought, and I checked thoroughly. But there is no IP address conflict.

I did send logs to Sonos, and they responded that there was “something strange”, but they stopped looking into it when my problem was initially cured.

What I have found that cures it is to assign a different LAN IP address to the Sonos speakers. That cures the problem right away. So now when this problem happens, I flip them back and forth between two dedicated IP addresses (i.e., .71/.72 and .73/.74). That cures the issue for a while. I don’t reboot the router if possible, because that’s a disruption to all the devices on the network, and it doesn’t automatically change existing IP addresses. Instead I use dhcpsrv on my Windows machine to re-assign just the Sonos speakers when they are unplugged/re-plugged.

I have not tried the “clear Google activity” method, but I will give it a test next time. It doesn’t seem likely to me because as I noted above I can cure the problem temporarily by moving my Sonos speaker to a different LAN, and the problem comes right back when it returns to the original LAN.

I might believe that it’s a unique issue between my Netgear router and the Sonos speakers, but in that case I doubt it would be a widespread issue with other people, unless you all have Netgear routers?

One other thing: this problem affects only Google Assistant. Another one of the things I tried was to go back to Alexa voice assistant on my Sonos One. Alexa worked fine. Switched back to GA - problem returns. I noted that I also had a lot of trouble (can’t find your speaker etc.) and a long delay registering Google Assistant again.

I have the same problem

We are still waiting from Sonos. 

This is very annoying. I have bought Sonos one for the integration with GA and now I am stuck. 

If we had an estimation when the problem will be solved it would be very good.

Either they have found out the problem and it is very serious or still they do not have a  clue. 

I have had good luck so far with my current solution: when this problem develops (could be anything from a few days to a month), I change the local IP address of the Google Assistant speaker in my Sonos One stereo pair. I switch back and forth between two dedicated IP addresses, .71 and .73. To avoid the disruption of resetting my whole network, I use a little Windows utility program called dhcpsrv which acts as a substitute DHCP server on the network and can be set to ignore everything except one MAC address, to which it issues a specified IP address. I can just unplug the speaker, run dhcpsrv on my computer, re-plug the speaker, wait for it to get an IP address, then terminate dhcpsrv (dhcpsrv manages to override the DHCP server in my router, so I don’t even have to turn the normal DHCP server off). Once I do that, normal GA function is restored, and usually lasts for days or weeks until the problem occurs again.

@Doug Ames 

I am trying to understand how come and this internal IP might be related with the Google servers.

Do you have any idea why this related?