Google Assistant & Sonos

I have changed between Alexa and Google Assistant on my Ones about 4 times. All of the “fixes” from all the forums aren't working. I have tried EVERYTHING. Alexa just stops when it’s time to play the news and Google Assistant says “I don't understand”. Is there and update coming from Sonos to fix this anytime soon? 

This thread is aimed at all of us whom has a Sonos Roam product (and probably a few other Sonos products as well).This thread aims to solve the following issues:Sonos refuses to add google assistant as a voice assitant (getting stuck during onboarding) Google Assitant commands can only Stop and Say what it is playing, but not Resume / change it (timers still work) Sonos Roam only plays if directly adressed, otherwise responds with “I can not do this on this device”.I have already solved these issues, the step by step guide is posted bellow as a answer.The solution i found to these problems are as follows:Issue #1:This requierd me to do a full unlinking of the product to my google account,Remove assistant from Sonos app, as it tends to get added but not work Press the Cogwheel (Settings) in the top right Press General Settings Select Voice Assistants then remove Google Assistant from your device Remove the connection from the Google Home app Open the Google Home app Click on your p

Hi,Just bringing up the ongoing lack of Google Assistant (and now Gemini) support on Sonos in Poland. It’s no longer just a minor issue—it’s a real dealbreaker. I don’t even need Polish language support; English would be completely fine.Because of this regional block, my smart home integration is basically useless. I love how Sonos sounds, but I’m seriously considering replacing my entire home audio architecture with a brand where voice assistants actually work.Are there any updates on this? What do you recommend? RegardsBart

I bought Sonos equipment because it was Google compatible.I have a daughter with muscular issues and giving voice commands is essential for various appliances around the home…Now what? You want me to purchase another set of Google products because guys can't sort our your differences? Struth!Get over it already! Give us the functionality that the products were sold with!  

Hello,I installed Google assistant on my Beam Gen 2. When Spotify is playing music, I can ask google assistant to move to another song. But if Spotify is not playing and I ask to start it or just ‘play music”, google assistant answers he is not able to do this. Can someone help?ThanksCoco

Google Assistant went through a rocky period over the last year while Google was attempting a rather confusing re-organization of how their automation routines work. They managed to break most existing automation routines, and at times it seemed like nothing was working properly. This not only affected Sonos speakers supporting Google Assistant, but Sonos saw more impact than native Google speakers. I pretty much gave up on them and moved most of my automations to Alexa.But Google finally seems to have gotten their act together, and automation routines are working again, including those which failed on Sonos previously. The earlier flaw that automation routines can’t speak any custom text on Sonos remains, but it’s worth trying Google automation routines again if it was the more recent failures that led to abandoning Google Assistant.

As it stands Sonos hasn't been programmed to accept Gemini. Here's why. The Sonos app is design to communicate with the Google assistant app. Gemini is a separate app. The sonos app attempts to open the Google assistant app only. If you've switched to Gemini, your Sonos devices won't accept your new AI assistant. 

With Android phones moving to Gemini, this change interferes with using Google Assistant on Sonos devices. If Google Assistant is not already set up on Sonos, the setup process now redirects to Gemini, making it impossible to connect GA to Sonos. For those who have GA already activated, enabling Gemini on the phone causes GA on Sonos to respond with a connection issue, rendering it unusable. This creates a difficult choice for users either stop using GA on Sonos or avoid switching to Gemini on their phones. Given that GA is likely to be fully replaced by Gemini in the near future, how does Sonos plan to address this transition and ensure continued voice assistant functionality on its devices?  

Honest not sure if this is a Sonos issue or Google issue or both.  After adding Sonos with Voice Match for my account, my partner goes into add Voice Match but it says there are no devices available. She can see the speakers in our Home but they are not appearing as eligible for voice match. She does however see a bunch of old versions of these speakers. does she need to add Sonos speakers herself as works with Google? Do I need to somehow share the speakers as available for voice match? 

There is a service notice about this posted now by Sonos now under Support, and it has been discussed in the “Update on the problems with Google automation routines” thread, but it deserves its own topic.A couple of days ago Sonos speakers using Google Assistant stopped responding to any media playback commands from Google, including Play, Stop, Set volume etc., although basic Google Assistant commands like “Time?” and “Weather?” were still working. Only Google was affected - Alexa, Home Assistant and other services could still perform those functions through the Sonos api. So either Google has their own api, or Google was being specifically blocked.Sonos suggests removing and re-adding Google Assistant from the speakers as the solution, but if you expect that to be less than straightforward, you’re not wrong. My Sonos app on Android successfully removed Google Assistant, but as others have been reporting for 5 months now, it could not re-add Google Assistant, getting stuck in a “No Co

I am using a stereo pair of Era 100 speakers and wanted to ask if Sonos would consider enabling native Chromecast and Gemini support on its speakers.Native Chromecast support would allow users to cast audio directly from any app that supports casting, without relying on individual app integrations or the Sonos app to initiate playback. This aligns closely with how many users already consume music, podcasts, radio, and streaming content across Android and Google TV ecosystems.Gemini integration would further position Sonos speakers as everyday smart speakers, extending their role beyond music to voice assistance and home interactions. This would increase long-term reliance on Sonos hardware rather than limiting usage primarily to music playback.From a practical and adoption point of view, this could: Lower the learning curve for new users Improve interoperability in mixed Android, Google TV, and Sonos households Remove a common purchase hesitation where casting is expected as a base

It has been mentioned a lot already but wanted to make a thread solely to say that all the remedies and work around offered by Sonos and Google do not work. My Sonos Move used to work flawlessly with Google Assistant. Recently it stopped allowing certain functionality like adding to shopping lists or find my phone stating that I had to set up voice match. The problem lies in that within my Google Home app, specifically the voice match setting, the Sonos speaker isn't found, even though it is part of my home and can be used for everything else. Then, 3 days ago, Spotify completely stopped working with Google Assistant and my Sonos. I can no longer control my music using voice controls, the speaker tells me "Sorry I can't do that on this device" I have unlinked and uninstalled all three apps (Sonos, Google Home and Spotify) re linked them and updated them multiple times. The Sonos speaker still isn't showing in the Google Assistant voice match setting so not allowing me to get personalis

It’s a bit difficult to pin down exact nature of the new problems with Google Assistant automation routines running on Sonos speakers that I reported earlier, but I’ve made some progress. It’s complicated by the fact that Google Home is in a state of flux at the moment as Google is making extensive changes that have introduced a lot of new bugs. No help from either Google or Sonos on this of course.The main item is this: now when a Google Assistant routine runs on Sonos and executes a custom command or query action that generates spoken output, it causes the routine to abort after completing the action.For example, you can have a routine with a series of actions to make device settings, or to tell you the time, the date. the weather, your schedule for the day, etc., and the routine will run just fine as long as they are standard actions or queries selected from the menu of the new automation editor. But if you insert in there a custom Google Assistant query or command not  on the menu

I have a Sonos One pair in my living room with GA installed and also a Nest speaker in my bedroom that has updated to Gemini. I use an iPhone 17PM. My entire house runs on google assistant.  Almost everything that can be plugged including all my lights, switches, LED’s curtains, climate, air filter, dishwasher and teapot.  GA was being really buggy so I thought I would reset the speakers and re-add the assistant. Bad Idea.  Obviously it was before I read anything on this forum about all the issues. I spent hours and hours working on it. I finally figured out that the only way I could re-enable GA was if the speaker pair had a new name, and they were in a new “room.” Once I got it installed, however, it refused to respond to “Hey Google.” Then I tried enabling the audio indicator which I always had tuned off and BAM, now everything is working mostly ok. It still often doesn’t work perfectly, but it’s working better than before. My nest speaker in my bedroom usually can hear me, but if i

It’s almost pointless to report new bugs with Google Assistant on Sonos these days, but for the benefit of those still using this combo:Google has new problems identifying which speaker to respond from if you have both Sonos and Google Home speakers in the house. The microphones are sensitive enough to pick up “Hey Google” from a couple of rooms away, but the multiple pickup is normally resolved by timing to identify the closest speaker. Lately there seems to be a new delay between Sonos and the Google servers, because now frequently a more distant Google Home speaker responds before Sonos, which belatedly chimes in with its own duplicate response. Sadly Google has never implemented alternative wake words to replace the tongue-twisting “Hey Google”, so there is no way to resolve this except to speak quietly.

Sonos really needs to figure out a way to get full Gemini or Siri integration.  I have a bunch of Sonos speakers that I’ve been mulling upgrading to new ones for a while now.  That said, no way I do it given the current limitations on using the speakers for voice assistants like Gemini.  I recognize this may or may not be Sonos’ fault, but that doesn’t mean they should not be going nuclear on figuring out how to do it.  If they aren’t able to fully integrate with systems like Gemini, I’d guess their footprint will shrink until they disappear or get bought.  Neither case is ideal as I’ve been a fan for many years, but this feels like an existential issue for them.I’m rooting for you Sonos, but need to see a solution no matter how you achieve it.

As far as I can tell, the sonos app can no longer connect to Google Assistant on a modern Android phone. I've un installed, re installed all apps and connections and all that has managed to do is remove my existing Assistant connections on other existing devices.Then I realised that due to changes in Google Assistant and Gemini it is no longer possible. I'm absolutely over this crap, luckily I can process a return for the new Sonos Move (not the 2..) Sonos is a waste of time and energy, what a joke!

So this morning all my Google Home automation routines that have a command to activate a Scene started interjecting “Ok, activating (name of scene)” when run on my Sonos speaker, but not on Google Home speakers. On the Google Home speakers the command continues to execute silently like before. This screws up the way some of the routines play out unfortunately.Compounding the problem, there seems to be a new bug with automation routines running on Sonos. When a routine with several steps is created or an existing such routine is edited, it will stop after the first 3 commands or so and exit - but only on Sonos, not when run on a Google Home speaker. Editing the routine further to drag the command order around and re-save it can cause it to start working again on Sonos.

Sinds kort reageerde mijn Sonos one niet meer op mijn vragen. Voorheen kon ik altijd vragen om radio NPO5 te spelen maar dan krijg te horen dat er een fout is opgetreden. Ook spreekt de sonos one als ik wat vraag dan weer in het Engels en dan weer in het Nederlands.  Ik heb alles gereset. Ik gebruik de Google assistent zowel in mijn telefoon ( S24 FE ) als op mijn sonos en toch blijft ze de opdrachten in het Engels uitvoeren. Ook heb ik de talen in het Nederlands gezet in Home. Voorheen ging het altijd goed maar de laatste tijd veel problemen. Ik hoop dat jullie misschien een oplossing hebben.Mvg Ad Trompert  

As I'm not able to reply anymore on the other topic here's a copy paste below. This issue still exists and is there for years now with a period in between it did work without issues. Any update on this? I'm experiencing the exact same issue as described below with my Sonos One Gen1. I can say volume 30 instead of volume 3 or volume 50 instead of 5 etc.to have it work correctly but it's still a bit weird this hasn't been solved so far.Info from another topic by ​@P.Janssen“For some months now I’m experiencing an issue when asking Google Assistant to set the volume of our speakers/rooms to a desired volume. This does not work properly when asking to set the volume to either level 3, 5 or 10. The other volume levels seem to work okay though, as per below list:“Hey Google volume 0” : room volume is correctly set to 0% “Hey Google volume 1” : room volume is correctly set to 10% “Hey Google volume 2” : room volume is correctly set to 20% “Hey Google volume 3” : room volume is incorrectly set

As anyone who uses Google Assistant routines on Sonos knows, it was quite a while ago that Google started saying “Sorry, I don’t understand” to any action in a routine that attempts to speak a verbal output on a Sonos speaker. The bug came and went a few times, and then settled in permanently with no acknowledgement from Sonos or Google.I experimented a bit to see if there was any workaround, such as playing a standard sound effect (unfortunately Google doesn’t have any built in sound effects) or playing a pre-recorded audio file with the response (that works, but media volume is muted as long as the routine is running, so the audio isn’t very audible).If all you want is a simple verbal acknowledgement to know that the routine ran, you can add actions in the routine to increase volume and then decrease volume by the same amount. That results in Google saying “Ok” or “Got it”, and it does work on Sonos speakers.

I’m not able to get Google nest to play anything on my pair of Sonos play 1 speakers.when I try and add Google assistant in the Sonos app it doesn’t work it just pops up help info instructions on how to set it up which I’ve already done. I’m using the Sonos app on my iPad. I have installed google home and Google assistant and the Sonos app. I try setting the default speakers to the Sonos speakers in Google home for the nest device. When I ask the nest to play music it says okay and that it’s playing on the selected speakers but the speakers never play anything. I can control the speakers fine using the Sonos app by itself.Any ideas on why this doesn’t work at all? I’ve seen other people posting that it works and I’ve watched YouTube videos on how to set it up and it working for them. 

I have Sonos system containing two Sonos One and one Sonos AmpGoogle Assistant have worked great together with my Sonos One for the last three years. Suddently out of the blue a “Sonos TV control” apears in my Google Home App. When I ex. call Google Assistant to switch off my Sonos One, it fails, and tell me there is a error with my “Sonos TV control”.First of all, I dont have any “Sonos TV control” installed nor any TV speaker and I don´t know where its coming from or how its suddently apears in my Google Home app. After two months of investigaing I now know its coming from my Sonos Amp.How can i remove/disconnect to this “Sonos TV control” in my Sonos Amp to get my Google Assistant workning again?

Ich möchte bei Aktivierung von Google Assist einen Anfangston einstellen. Wo kann ich das Problem beheben? 

So today I ran into an odd issue with both my Move and Roam, when I go Hey google play XXXX on Pandora. It will respond playing XXXX on Pandora, then silence. Same thing happens when I say play XXXX on YouTube music. It will response playing XXXX on YouTube music and then silence.If I go into the app on my phone and select what to play, it will start playing on the speaker.Losing the ability to have music play via voice command just started in the last day or so. When asking the google assistant about weather and such, it will respond as expected. It seems to be just with playing music currently.I’ve tried rebooting the devices, no change. I removed google assistant from the Move and no difference. I’m not sure if this is stemming from a larger issue I’m having with Sonos and google assistant where when Pandora is playing I can’t use voice commands to like a song, again I need to go into the app to do this.