Skip to main content
premiump
Contributor I
May 4, 2021
Answered

Google Home can't find Roam

  • May 4, 2021
  • 13 replies
  • 2019 views

I have a Beam in the lounge with two One SL’s as surrounds. Google Assistant works fine on this setup.

 

I have just bought the Roam and when trying to add the Google Assistant, it simply does not find the device. I have now tried it several times, both through Google Home and also starting within the Sonos app.

 

I removed Google Assistant from my Beam and tried again in Google Home, it found the beam instantly … but not the Roam. Ugh.

 

The Roam is on my network, I can play Spotify through it, I can add it to other speakers to play the same music concurrently (speaker groups?) … but I can’t add Google Assistant … as Google Home just cant find it! Frustrating to say the least. 

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Best answer by Corry P

Hi @premiump 

Thanks for trying those steps.

At this point, it’s difficult to proceed without getting some information from the speakers themselves.

I recommend you make sure both Sonos and Google Home/Assistant apps are fully up-to-date and try rebooting your phone/tablet or try using another device, if you have one available. It may also be worth trying again with the RBW30 turned off, though this is a long-shot.

Failing that, I recommend you get in touch with our technical support team, who have tools at their disposal that will allow them to give you advice specific to your Sonos system and what it reports.

13 replies

Show previous replies
CWE
Lyricist II
May 17, 2021

Ok, with a little perseverance I was able to figure it out - at least in my case the issue was that my Sonos account had a mixture of S1 and S2 devices associated. I was afraid if I deleted my S1 equipment I would lose my upgrade offers, so instead I created a new Sonos account, factory reset my Roam, and attached it to the new account instead. Voila - everything working smoothly. Hope this helps! @premiump @Corry P  

    Corry P
    Corry P
    Sonos Staff
    May 17, 2021

    Hi @CWE 

    I’m glad you found a resolution! When using Voice Assistants with Sonos, the Voice Assistant should only “know” about one Sonos household (system) on a Sonos account (for reliable use). As S1 and S2 systems count as different Households, and having the same Voice Assistant on both will confuse the Voice Assistant, this is why you’d need another Sonos account. You should also use a separate Voice Assistant account.

    Unfortunately, this won’t help @premiump as their system is S2 only.

    So that you know, the Upgrade discounts are associated with the device itself, and the device is associated with your account. Therefore, if the Upgrade voucher has never been activated for a particular device, it’s available to the account which last registered said device. In short, as long as you have the unit in your possession, you can get the Upgrade discount - resetting your system or creating a new account won’t affect this. If, however, you were to activate the voucher, then reset the unit and setup a new system on a new account, the voucher will still be on the original account and can be used as normal.

    "Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
    premiumpAuthor
    Contributor I
    May 17, 2021

    Ok, with a little perseverance I was able to figure it out - at least in my case the issue was that my Sonos account had a mixture of S1 and S2 devices associated. I was afraid if I deleted my S1 equipment I would lose my upgrade offers, so instead I created a new Sonos account, factory reset my Roam, and attached it to the new account instead. Voila - everything working smoothly. Hope this helps! @premiump @Corry P  

    Thanks for the update. I saw your initial reply and went to try again over the weekend before responding … then got a Roam product update when I went into the S2 app. After the update, it still wouldn’t add the GA from Google Home (I had high hopes too).

     

    I’m glad you got it sorted, as Corry P mentions above, your resolution won’t help me … but I’ll keep trying :) 

    Terms & ConditionsAccessibility statement