Google Assistant - Vanished and cannot be added back on Beam (Gen 1)
As of November 20, after a long power outage of 12 hours, I noticed the following:
Google Assistant (GA) vanished - first noted with inability to turn on microphone, verified on Sonos App, on the Sonos Beam Gen 1.
Any attempt to re-add GA via either android or ios fails with different symptoms depending on the OS. Android will not be able to locate any google assistant capable device in the ‘google assistant’ phase post linkage (SSO/OUTH) between google sonos; IOS will get there error message ‘There may be a problem’.
Verified no former linkage exists in Google Home.
I added / removed the SONOS voice control successfully so the Beam is not mechanically challenged.
I’ve reviewed threads, cleared the beam to factory defaults and rebuilt, rebooted the router / sonos devices, all to no effect. All Sonos devices and controller are up to date. Still, no ability to add Google Assistant to the beam.
I’ve seen an email thread from three months ago that the GA feature / addition is currently not functioning, but I see no formal announcement of this. With the value of time, it’s just cheaper to buy a google nest mini and get used to saying ‘hey google’ for home control and ‘hey sonos’ for music … which is honestly rubbish.
Before I waste hours on the phone, can I get an official word if Google Assistant is formally supported.
Frank
Page 3 / 7
Another user, same problem. Absolutely pitiful!
Hi all, i just received my new Beam Gen 2 a few days ago and never was able to connect it to my GA. This was one of the key features and without this working I would never have chosen Sonos. Feels bad to be a new customer.
That errors can happen, I totally accept, but the communication and support pages are totally skipping this issue at all. Please consider to update the support page regarding GA implementation issues and please stop pretending on the status page, that the service is working fine if it doesn't.
Good luck and let us keep each other posted.
Thanks all
Same issue here.
Bought an arc yesterday, wouldn't aadd to GA.
I already had a beam that has been working fine.
Removed sonos from google home, amd now it won't add back. The error message in google home when trying to add is 'could not reach sonos. Please try again'.
I use uoutube music, so sonos voice control is no good for me.
Right now i have a brand new arc, and a beam not functioning with services they were sold as supporting.
If its not resolved soon, the arc will be going back.
In my opinion Sonos needs to be sued, for false advertisement.
Do people on this thread have multiple systems or model types in-common?
I have an ARC, sub and 2x SLs for home cinema. I also have a pair of SLs as speakers separately.
it would be great if Sonos could give us an update here to acknowledge what might be going on and provide any kind of work around.
It's unclear how long this issue has been happening.
For me, the issue is that you can't add sonos into Google home. I did see another thread, where someone mentioned that you also couldn't add other apps like phillips hue etc, so have Google done something that has broke a lot of apps?
I must say, so far the arc setup has been painful, where as the beam just went straight in like a dream. The arc wamted to update, then kept failing until I connected an ethernet cable.
Yeah the Arc and surround setup was a nightmare for me too.
Essentially in theatre mode, which is generally how the ARC works, the speakers stop talking to your WiFI directly and to each other, this can cause problems.
Do you have a single router/AP or multiple?
Bought a Beam (2 gen) yesterday and can't add Google Assistant to Sonos either. Connects fine with TV and Spotify etc. Same errors are everyone else above in this thread.
I unlinked GA today because my Nest Hub wouldn’t work with my Sonos speakers. Now when i try to add GA again it won’t work. Very annyoing because I control all my lights with GA and my Sonos speakers. Please just fix it. Been using Sonos for so long but this is just insane..
Same issue here. I bought the Beam Gen2 for Google and will now box it up and return it as Sonos are not living up to that which was promised.
I'm still trying to find out how long it's been an issue. I've had a beam for about 14 months, and other than the sonos > GA connection going down for a few days, it's been fantastic, hence me buying the arc.
Submit error report, however, the error "Cannot contact Sonos" appears in the Google Home app.
Same issue here. Sonos Move 1.
Over a week now... When can we expect a solution?
Same issue here. Nor my amazon dot nor my google assistant can’t find my sonos AMP. Weird thing is though that home assistant does find it ...
In this case, the automated testing (in Jenkins, gitlab, etc in the devops methodology is not doing the right testing). Production customers should not be your regression testing or new feature test. As much as I appreciate the escalation to engineering, there are problems here in the overall development and operational org. And yes, I managed the research, build and operation of global cloud service, platforms, workload and network infra of an enterprise hyperscaler. The final judgement is if Sonos learns from this or just places a new coat of paint over the old shed.
It's certainly took the shine off owning the arc, and it trying to resolve, I've also removed functionality from my existing beam, which are now just speakers rather than smart speakers.
Do people on this thread have multiple systems or model types in-common?
A single Sonos One - can’t get much simpler. And can’t connect to GA.
It's unclear how long this issue has been happening.
For me, the issue is that you can't add sonos into Google home. I did see another thread, where someone mentioned that you also couldn't add other apps like phillips hue etc, so have Google done something that has broke a lot of apps?
I must say, so far the arc setup has been painful, where as the beam just went straight in like a dream. The arc wamted to update, then kept failing until I connected an ethernet cable.
Exact same thing with me to the T. if I try it on my other Android phone is just says can’t connect/can’t reach
We’ve been having issues with our Sonos Ones and Alexa so I thought we’d give Google a try, but running into the same issue here as everybody else.
Really annoying.
Reminds me of that one time when the great new app came out rendering it impossible to modify our alarms because, why would that be something they’d test?! Strong work, as usual, Sonos.
Same issue hère
Beam gen1
2 play1 as surround
1 sub
And no more ringdoor bell notification as I've a nest hello.
So cool to let people wait at the door.
Diagnostic posted.
Thanks @FrankOwen for the thread.
Same issue here. Issue after issue. Is CEO going to issue apologies next year and not do anything anyway.
Same issue here. Just bought 2 x Era 300 in BF sales to add to Sonos Port. Hadn’t bothered with Voice control with the Port but experimented with VC for the Era 300. Native Sonos Voice OK and Alexa Voice via Era 300 mics. Thought I’d try Google voice using mic on Google Home Screen but no joy, same error as in OP. By not showing this as degraded on the Sonos service status page devalues all confidence in such a status page.
I am also having this issue.
Was having trouble with my Sonos One constantly having trouble responding to Google Assistant queries.
Removed Google Assistant, now I cant add it back, the whole process fails with generic “Try Again” errors that dont resolve upon retrying.
I have deleted and reinstalled both the Sonos and Google Assistant apps, tried installing the integration straight from the Google Assistant and Google Home app, nothing works.
I hope a developer is actually monitoring this thread. This is ridiculous.
Its almost like Sonos laid off the engineers who knew how to make this stuff work, and kept the ones who didnt. I hope whomever is in charge of this gets PIP’ed
I got the impression Sonos Staff mentioned here they were investigating and some had reproduced the issue, as seen here…
I see the GA issue too, but likely ‘thanksgiving’ and ‘the weekend’ has perhaps got in the way of things. I’m just waiting to see if there is a fix from Google, or Sonos, but suspect it might not happen immediately, particularly if investigations are possibly still ongoing.
I have removed Sonos from my Google home app and now I cannot re-add it. I keep getting ‘could not reach Sonos. Please try again.” I’ve been trying to get this to work for hours, nothing works.