Skip to main content

My set up is 1 x Play:3 hardwired creating a SonosNet with a number of Play:1/Sonos One dotted around the house.

I have 2 x access points in the house for the S2 controller to connect to (same SSID etc.)

I often get the following situation.  As an example, I’m playing music in the kitchen (this is the only room playing).  I open up the app to stop the music.  The app shows every other room and what was playing - that is you can see the album/radio station image - but the kitchen will be completely blank, so I can’t use the controls to stop the music.

It can take up to 1 minute for the room to “kick in” so I can see the album/station and use the controls to stop the music.

This isn’t restricted to the kitchen, it’s whichever room is playing.

Anyone else seen this issue?  Any idea how to resolve?

With a mesh network, it’s recommended that the Sonos device that is connected via an ethernet cable is connected to the base network device rather than one of the satellites.  Can you confirm that this is the case? 

Yes, I said the Play:3 is hardwired.  It’s directly connected to the router.  The 2 APs are also connected via ethernet to the router.

Yes, I said the Play:3 is hardwired.  It’s directly connected to the router.

Thanks.  Your didn’t say what network device the Play:3 was connected to in your original post and so I wanted to check.

Have you reserved any IP addresses in your router?

If not please checkout my post:

 

Thanks for the reply.  No addresses are reserved in the router.  A few devices have static IPs at the upper end of the subnet range to avoid conflicts.

I can’t see any IP conflicts.  Would the issue I’ve posted be symptomatic of IP conflicts?  I thought the speaker would not show or be accessible at all.

Thanks for the reply.  No addresses are reserved in the router.  A few devices have static IPs at the upper end of the subnet range to avoid conflicts.

I can’t see any IP conflicts.  Would the issue I’ve posted be symptomatic of IP conflicts?  I thought the speaker would not show or be accessible at all.

Yes, this is an example of duplicate IP addresses.

Thanks.  I’ll make some changes at the weekend and see if it helps

I made the updates and not sure if they have had much effect.  Unfortunately, the new app was released and it seems worse than ever.  Over the years this app/system has gone from “it just works” to being pretty flaky.

I’m still experiencing the app losing connectivity to the speaker currently playing.  I’ve started connecting via Spotify and have no issues with this at all.  Spotify finds the speaker, connects and remains connected.  Volume controls work fine (very small delay).  I don’t think this is an issue with the speakers and the network connectivity.  This seems an issue with the app.  

Without any change to my network, what used to work flawlessly has gotten worse and it pretty unusable now.

Which mesh network are you using? Avoid any temptation to Factory Reset a SONOS unit without further consultation.

The speakers are using SonosNet.  One is wired to the router.

WiFi is via 2 x Ubiquiti Unifi APs - both wired to the router

I was going to try and disable SonosNet and use WiFi, but the new app seems to have removed network configuration too  ☹️

Terms & ConditionsCookie settings