diagnostic confirmation # 519393952. Thank you for looking into this!

You can add me to the list as well. The issue popped up about a week ago. I can manually initiate playing Tune-In content or my local radio stations through the Sonos App but when doing so through the Google Assistant, I get the ‘Sorry, I can’t find what you asked for’ response.

I’ve got over $1,000.00 worth of SONOS devices in my house and it would be an understatement to say this is an extremely disappointing development.

Diagnostic Confirmation #1471919679.

I started having this problem about a week ago as well. I have Sonos One Gen 2’s, Sonos Beam, Sonos Arc, all have the issue.

Diagnostic submitted, #1778073560

Sonos team, you’d save a lot of us and your team time if you could tell us how to resolve this on our own. 

Started for me on TuneIn stations about two weeks ago. Glad it's not just me! Diagnostic 2032091374

Same issue here trying to connect to tunein, diagnostic # 1326254199

This started about two weeks ago for me as well.

When I say, hey Google, play KHUT.  

Got it, playing KHUT on Tunein. Sorry, I can’t find what you asked for. 

I have 9 Sonos One Gen 2, a Beam, and Arc, etc. The problem occurs across all devices.

Same problem with my local NPR station. Can play through the app but can't bet Google Assistant to play for me. Diagnostic confirmation number: 1492053890

A status update would be appreciated.

Same issue, beginning about 10 days ago. Status update, please.

Any updates on this issue?

Please add me to the group too, @Simon B.

Diagnostic #: 911422862

Google on Sonos can’t find TuneIn or other music apps connected through Sonos. But weather, directions, any random google questions work just fine. And Google understands what I’m looking for, as it always first says, “Got it, playing tradio station] on TuneIn” before giving the sorry message. This has been going on about a month now. Possibly longer. I’ve tried the uninstall and re-install Google and that did nothing to change the problem. And nothing on my end changed to precipitate this.

Could you also please provide an update as to what is causing this issue and a potential timeline for addressing it? I’m sure all of us on this chain would appreciate that. Thank you!

Yeah, I’d like to be added to the list too.  @Simon B.

Tunein radio and apple music basically useless.

I’m glad I didn't update all my home theater sound system yet, or the whole house like planed. I feel bad for the ones that have.

If it’s because of Sonos own streaming platform that would be a shame.

Diagnostic: 116500507

An update please?

Hi to all, Sorry for the delayed response on this issue, I coordinated with our specialists about this issue and they’ve told me that there is no known issue for this error on Google Assistant and was asked to continue with the basic troubleshooting steps. 

If you're getting no audible response or this error message “Sorry I can’t find what you asked for” from Google Assistant when issuing a command, let me suggest the following steps for you to check.

• Check if your Sonos system is up to date.
• Sign out from your Google accounts on your device controller and browsers.
• Giving specific commands, like example "OK Google, play The Beatles in the kitchen" will direct your Google Assistant to play through the kitchen speaker.
• If the microphone is enabled, but Google Assistant still does not hear your room name or command correctly, check to see what Google Assistant heard: myactivity.google.com and check the corresponding activity if you will see an “unknown voice command” in the activity.
• Try removing Google Assistant from Sonos and setting it up again. This will re-establish the connection with Google Assistant servers.
• Hardwire through an ethernet cable one of your speakers to your router temporarily and check if Google Assistant will work.

Let us know how it works for you. You may also check out this article to get help with Google Assistant's daily routines.

We're here to answer any further questions you have.

Is it possible this has to do with running the S1 OS? Is anyone experiencing this having already updated their system to S2?

It doesn't.  I've performed all of the recommended steps and it still behaves the exact same way, as others have already reported.

IMHO, this appears to be an issue with the hand-off from the Google Assistant back-end to the Sonos system's TuneIn support.  It's not an issue with the Google Assistant itself, nor with network connectivity, microphone settings, not the specific command spoken.  Those are all red herrings.

Please escalate this issue and have your engineers continue their investigation.

Thank you.

Hi @perrymasterflex & @mj1856, thanks for the update and for trying the troubleshooting steps provided. We’ll have this checked by our team, but kindly contact our phone support team as well for further assistance and more in-depth troubleshooting steps and so that they can file a troubleshooting ticket if there is a known outage for this issue. 

Please, feel free to let me know if you require any further information.

Hi.

I called the phone support and spent quite some time with the support engineer.  He was very helpful and working together ultimately we were able to reproduce the issue on his side.  He said he would escalate it to the appropriate engineers for further analysis.

Also, we were able to determine that this happens only with certain radio stations.  For example, saying “Hey Google, play KUOW” would always fail, where saying “Hey Google, play NPR” or “Hey Google, play KEXP” would work.  We both got the same results on our respective Sonos devices.

In my opinion, this feels like an issue with TuneIn’s API that Sonos is using.  Since I can ask the Google Assistant to play KUOW on TuneIn from other non-Sonos devices (such as my Android phone), I speculate that TuneIn may have more than one version of their search API.  Perhaps Sonos is using an older one that fails certain lookups whereas the newer one doesn’t.  I can’t verify this, but it’s reasonable.

Hopefully the Sonos engineers can look at this and either take the issue up with TuneIn, or switch to a newer or different TuneIn API.

Also, to answer @perrymasterflex’s question, I am only on S2 devices.

Hi @mj1856, thanks for the update and for the information that you provided.m Hoping for the best that it would be fixed soon since it was already coordinated with the right team. 

If you have any questions or run into any other issues, please do not hesitate to contact us. We are always happy to assist you.

This problem is most definitely NOT just related to specific channels, and it’s not limited to TuneIn.

For me at least, pretty much nothing is working through “Hey Google...” 

I get a version of “Sonos is not available right now” or “Sorry, I couldn’t reach Sonos” when saying, “Hey Google, play <Artist> on Tidal”.

It tells me Apple Music isn’t support on the speaker.

It tells me my Spotify account isn’t properly linked when I say, “Play <Artist> on Qobuz” or when I say, “Play <Artist> on Spotify.”

 I’ve tried the suggested debug steps listed in the earlier post. 

I suppose I’ll reach out to phone support when I have time, which I do not have at the moment, but for now it’s pretty much a dumpster fire that used to work perfectly fine.

Yes this is how it works for me as well. It will play some stations I do not want to listen to through voice. But not the ones that previously worked. It used to work to say ‘hey google play classical music’ and now doesn’t. But if you specify the artist it will play.

Seems to be working as of tonight. The only change I’ve made of late is the voice of the Google assistant. 

I also noticed two days or so ago that TuneIn appears to be working again.

“Hey Google, play <artist> on <service>” is still not working, either telling me <service> isn't supported or isn't connected or Sonos is unavailable, even though any given <service> works perfectly well from within the Sonos app.

Same here

Still no update on this? I bought arc specifically over beam to use as a voice control for my entire system and so far it hasn't served its purpose. I'm continually getting this message