Google assistant on Sonos one not responding

No, I don’t understand it either. My best guess is that Google has gotten a bit too fancy with their networking code and is taking some kind of efficiency shortcut that doesn’t work properly with Sonos. I see this kind of problem elsewhere as well - Google Home speakers don’t work properly with Home Assistant unless you give them a fixed IP address and tell Home Assistant explicitly what it is. It seems that the GH speakers are not responding to arp commands on the network a lot of the time, leading to loss of contact unless the software trying to communicate knows the fixed IP address for them.

I have discovered that every morning at around 7:30-8 am GMT+2 GA works just perfect. Is this a coincidence?

Can someone confirm that?

@Doug Ames 

I have tried your solution multiple times getting different IP addresses.

The result is the same. No response.

@Sonos Support ,

Do we have, any permanent solution do this or at least a temporary one? 

Did you manage to pinpoint the problem?

It’s a long time since this issue appeared.

Same issue here on a new Sonos Move (diagnostic ID: 1477074619)

Google Assistant responds to a handful of basic commands (what time is it, what’s the weather) but never responds for anything more complicated (skip this song, what’s this week’s forecast, what’s my first meeting). 90% of the time, these queries have no response at all or I get “Sorry, something went wrong”.

My Google Home Mini with the same account on the same WiFi has none of these issues.

Here’s what I’ve tried (none of which have worked)

• Factory reset of Move
• Unlink then relink Assistant in iOS Sonos, Home and Assistant apps
• Delete and re-install Assistant and Sonos apps
• Connecting to a different Google account
• Changing language from UK English to US English

This issue has been happening for months. I bought the Move specifically for its Assistant integration so this is extremely disappointing and Ive wasted hours trying to resolve the issue.

I’ve had my Sonos One stereo pair get into this non-responsive state 4 times, but most recently it has been reliable for the past 6 weeks.

Each time I tried every measure I could think of to fix it, and the only thing that worked for me was to force a local IP address change. I still don’t know why that works, but it does work for me. I flip it back and forth between 2 fixed IP addresses now. After the IP address change it returns to normal operation, where it has lasted as short a time as just one day, and as long a time as 8 weeks.

...and May 2020 is approaching fast, which means EOL for receiving updates if you own older Sonos products.

As I own several such products, I am now facing the choice of receiving a software update, which repairs Google Assistant but requires me to throw out three devices which works perfectly OR I can choose to stay behind leaving the Google Assistant not working. 

I hope the Google Assistant fix will be in a compatible update, but I have a feeling that things will turn out exactly as I fear.

Or perhaps choose the best of both worlds and opt for the 'split system’, as mentioned in this Sonos publication.

Sonos S1/S2 Overview & Compatibility

Hi,

Dutch speaker from Belgium, but use GA in English: exactly the same issues as other Dutch speakers: Google assistant not working.
Had this issue before, disabled the voice match and changed country in my Sonos profile to the US.
This fixed it, till my flatmates unplugged the speakers a couple of times, till one time I had to re-initialize the whole setup.

Now the GA recognizes my commands, but does’t execute them (while it does without issues on my phone). Interesting to note: when I say “Okay Google” while both my phone and Sonos are within hearing distance, it prioritizes my Sonos (as it always did), this is still the case, so I’m guessing it’s still connecting to the Google server one way or another to make this distinction.

Anyway, I cannot disable voice-match anymore, it has been replaced by an “associate product” screen, I have no products associated, but cannot associate any either (for the sake of debugging).

So now I cannot use my GA anymore, which is the whole reason I bought this speaker for.

If anyone has a new solution: feel free to let me know!

Cheers,
Ben

I wasn’t aware of that. Thank you for that information. That is a better approach from Sonos.

Bought a few 2 and assistant getting the unknown voice command issues... After 2wks of messing around I returned and got an exchange... Sonos advised I didn't have the issue you're referring to on this thread, it must be another. New speaker has arrived and guess what, it doesn't work. Given this has been going on with sonos for about a year I'm assuming they can't fix it and therefore seem to be miss selling this product. So very dissapointed in Sonos!