Adding Sonos speakers back


I had Sonos integration which worked okay and had all my Sonos speakers in ST but something stopped it from working a year ago so I just skipped it and haven’t had time to sort it…
Anyway, actually got a few weeks off so I thought I’d spend a few minutes sorting it.
All speakers have been deleted from the app a long time ago since it didn’t work.
So. I just thought I can add it again…
Was I wrong or what. :grin:
If I ask ST to search for devices and Sonos it starts standard inclusion process then tells me to start the speaker? :joy:
Both on the same VLAN btw but not sure why that would matter it’s a Web connection right?
They are of course on, they are connected to Sonos (actually sort of working now despite the app update)
so I’m sort of lost for words here.
What do I have to do to force ST to sync them again?

Talked to Sonos support earlier about it and asked them to remove the link to ST but according to them ST support has to remove it.
Ita really interesting that I can’t cut the ties completely and start over?

Any one that can help, please?

The connection type depends on whether you have a ST hub or not. If you have a hub, there is an Edge driver that is loaded on the hub and all you have to do to add a Sonos device is do is Add Device->Scan Nearby.

If you don’t have a hub, it would have to be cloud->cloud, but I don’t recall if that is still supported. @bthrock might know better than I :grinning:

To check if there is still an association between Sonos and ST, go to Menu->Gear menu->Linked Services. If Sonos is there, go to the 3 dot menu and select Unlink to remove Sonos.

Clarify… what is both? ST hub and Sonos or mobile device with ST app?

Using Android or iOS? With the latest release of the Android app… who knows! :slight_smile:

Okay all three then… :grin:

Using android and all things and apps are up to date.

I do have the hub but Sonos is not among linked services anymore.
When I scan nearby I only get Direct connection to the phone devices.

Just a note around this, Sonos has undergone a major firmware (and app) update recently mainly to support thier new headphones and shift to a cloud based pattern.

This has seriously compromised the functionality and speaker discovery and onboarding within thier own infrastructure. According to users it has become virtually impossible to onboard new speakers, existing speakers are lost/dropping out/de-pairing and not grouping reliably.

In short, is has become a complete disaster for Sonos and thier users/professional installers who are in uproar over the crippled devices they are now left with…

I mention it here as, if Sonos themselves are facing issues with their new firmware it may be being reflected within ST interactions. I run several speakers from ST and have noticed an increased lag in/absence of status updating but otherwise they seem to be OK currently🤞

I have not added any recently though…

1 Like

I want to say i have sonos linked from partner devices and it automatically sync it to my hub. I dont believe they offer cloud to cloud since the app is just essentially a controller. Saying that my sonos Has been working and i can still see it despite the new app. Maybe try removing and readding sonos product and then try to set up the smartthings integration?

1 Like

To add your Sonos speakers—assuming they are on the same Wi-Fi network as your hub and already connected to and visible in Sonos’ own app—you only need to Scan Nearby. Just ignore the various media renderers and other devices that appear. The actual speakers will show up in your unassigned room under the names you originally gave them in the Sonos app.

It’s worth noting that the hub-based Sonos Edge driver communicates locally with your speakers, via the LAN and not the cloud, and that local architecture remains unaffected by Sonos’ decision to shift their own app from local to cloud-based. Similarly, the Sonos Control API, which is cloud-based, still functions as before. I almost never use the Sonos app and instead rely on integrations that utilize the websocket, UPnP, and API interfaces. As such, I have had no issues with my system—but, to be fair, neither have I tried to onboard new speakers to my new system in the past couple of months.

Thanks Bob!

They are indeed on the same network, speakers show up in the Sonos App.
I’ve even set fixed IP’s for every speaker and the ST hub so I’m 110% sure they are on the same network.
But it’s not under linked services either so I’m thinking I’ve gotten some catch 22 here… :smiley:
Guess I’ll have a chat with the support to see if they can do anything.

Sonos should appear under Partner Devices (I don’t think it’s been called 'linked services" for a while, but I don’t remember), but it’s not necessary or even useful for it to be there.

Check if your Hub has the Sonos driver installed. It should be installed automatically, But check anyway and see what version you have. You can check through the ST App or the SmartThings Advanced Web App.

And reboot your hub and router :slight_smile:

1 Like

:joy: :joy:
Sonos resolution 101…

Naah problem is not network. I can see the traffic and it’s not a problem.

Nobody said the problem is your network. The suggestion to reboot your SmartThings Hub and your router has nothing to do with the quality of your network. It’s a simple and very routine means of ensuring that your SmartThings hub, your router, and your speakers are all on the same page. It might not help with your issue, but it typically only takes a minute or two, and when troubleshooting LAN devices it is SmartThings 101.

1 Like

It was a joke… It’s the standard for any issues with Sonos on all Sonos forums… :grin:

All restarted but issue remains…
They only show up as directly connected to my phone not connecting to the hub.
So I raised a ticket with the support.