Skip to main content
Question

Sky Max Hub, Orbi 7 mesh & Sonos discovery issues??

  • July 4, 2026
  • 10 replies
  • 110 views

homeconnected
Forum|alt.badge.img

Help from the pro’s needed...🙏

11 Speaker Sonos System - Becomes Unresponsive After a While (Sky Max + Orbi RBE871 AP Mode)

I’m hoping someone can point me in the right direction because I’m running out of ideas.

My client has an 11-speaker Sonos system consisting of:

  • Beam
  • Sonos Amps
  • Play:3s
  • Sonos Ones
  • Roam

For over 6 months they’ve experienced intermittent issues including:

  • Rooms disappearing
  • “Unable to connect”
  • “Cannot communicate”
  • App timing out
  • Speakers appearing in the app but with no playback controls
  • Alexa playing to the wrong room or saying it’s playing when nothing happens

Original Network

I discovered the network was configured like this:

  • Sky Max Hub (routing + Wi-Fi enabled)
  • Orbi RBE871 mesh (Router Mode + Wi-Fi enabled)

So there were effectively two routers and two Wi-Fi systems.

Changes Made

I spent the day simplifying everything:

  • Sky Max Hub now does all routing and DHCP.
  • Sky Wi-Fi disabled.
  • Orbi RBE871 changed to AP Mode.
  • Garden Orbi also changed to AP Mode.
  • Garden Sonos speaker moved into the same Sonos household as the rest of the house.
  • Reserved almost every Sonos IP on the Sky router except Beam that would not reserve IP?)

General Internet performance is excellent and all devices receive correct 192.168.0.x addresses.

Behaviour

Initially everything appeared much better.

However, after a short while (or after leaving the house and returning), some or most speakers become unresponsive.

The strange thing is:

  • All speakers still appear under Settings > About My System.
  • Music services are still visible.
  • Playback controls disappear.
  • Trying to start new music often fails with “Unable to connect” or similar.

Interestingly:

  • Previously playing speakers often continue playing.
  • Sometimes pressing the Play button on the physical speaker starts playback, even though the app cannot control it.
  • If I go into the Devices screen at the bottom of the app, the speakers that were already playing often still respond.
  • It seems to be starting new playback or controlling speakers that fails.

One particularly odd observation was that during one failure, the only speaker that responded was actually the one with the weakest Wi-Fi signal.

Sonos Support

I spent around two hours on the phone with Sonos Support.

They looked at diagnostics and suggested changing the Orbi 2.4GHz channel from 1 to 6 due to network congestion.

Immediately afterwards every speaker appeared to work.

I ended the call, walked outside to the van for a few minutes, returned to demonstrate everything was working… and almost the entire system had stopped responding again.

The behaviour was identical on both my phone and the client’s phone, so it doesn’t appear to be controller-specific.

Current Thoughts

At this point I’m wondering whether this could be related to:

  • SSDP/mDNS discovery
  • Multicast handling
  • Sky Max Hub behaviour
  • IPv6
  • Orbi AP Mode
  • Or something else entirely

General Internet access remains stable throughout.

I should also mention that before changing the network topology, the client’s main complaint was that when he walked between rooms, the Sonos app often took a long time to reconnect or would lose communication with the speakers.

One thing that keeps standing out is that every time I reboot the network, or make a network change, the Sonos system appears to work properly again for a while before gradually becoming unresponsive.

Has anyone experienced similar issues with Sky Max Hub + Orbi RBE871 in AP Mode + Sonos?

Before I return next week I’m compiling a checklist of things to try, including:

  • Wiring one Sonos player as a test.
  • Disabling IPv6.
  • Checking WPA2/WPA3 security settings.
  • Looking into multicast/IGMP settings.

Any advice or similar experiences would be greatly appreciated.

Thanks.

10 replies

AjTrek1
  • July 4, 2026

What type of amps are being used? Gen1, Gen 2 or the latest Sonos Amp?

If you haven’t done so… try naming all bands with the same SSID.  Follow the steps:

  1. Unplug all sonos
  2. Make the SSID change 
  3. Reboot Main Router
  4. Delete the App from your device (at this point just stop the app on your clients device; don’t delete it)
  5. Plug in all Sonos and let them come back
  6. Reinstall the app on your device 
  7. Select join an existing system 
  8. Accept all prompts 
  9. Sign-in with clients credentials 

 


Stanley_4
  • Grand Maestro
  • July 4, 2026

Plugging one Sonos to Ethernet will put all but the Roam in Sonosnet mode, that removes the ability of your other Sonos to connect with your Wi-Fi if they can see the Sonosnet signal. Not what you want. 

Being unable to reserve an IP address for the Beam is troubling, there is something wrong in your DHCP configuration that needs to be found and corrected. Might be as simple as it is already assigned but under a name you aren't expecting, sort by MAC address and it should show up.

I no longer have IPv6 access but last year when I did Sonos didn't seem to be doing much with it and on my now v4 only network I have no issues.

The leaving with the controller and returning to errors makes me suspect the phone may be connecting to a different AP, one not fully passing the required network traffic, or a VPN or the like diverting it.

 


Airgetlam

In addition to the excellent suggestions above, I’d want to review the wifi interference FAQ. If Sonos CS showed signs of WiFi interference on one channel, the base transmission channel by the router may be impacted as well, causing the speakers to have difficulty connecting. I’d want to ensure that your network (or theirs, technically) is locked down to a single channel, and not hopping. 

And a network refresh (power off all Sonos, reboot the router, wait two minutes, then bring Sonos back online) is always a good thing. You’d get refreshed router firmware and refreshed Sonos firmware, as well as refreshed IP assignments, although that part may be moot with your reservations, although not being able to reserve one for the Beam makes no sense. The router reboot may clear that issue . 

Make sure, when they’re all connected, that you check for, and apply any updates, too. 


homeconnected
Forum|alt.badge.img
  • Author
  • Contributor I
  • July 4, 2026

Thanks both. The system is on a single SSID and single subnet. The Orbi is in AP mode and Sky is the only DHCP server. The issue affects both my phone and the client’s phone simultaneously, which makes me think it isn’t simply a controller cache issue.

Interestingly, when the issue occurs, all speakers still appear under About My System with valid IP addresses, and sometimes pressing Play on the physical speaker starts playback even though the app cannot control it. A reboot of the network restores operation temporarily before the issue returns.

Im thinking Multicast forwarding issues across the Orbi satellites when in AP mode? But I’m no network engineer!

Im going to disable IPV6 on my next visit, I will update my findings  👍🏻


Stanley_4
  • Grand Maestro
  • July 4, 2026

I know there is good advice here on Ubiquiti gear since I have some, haven't followed Orbi though so it might be worth a check to see if there are reported problems and cures.

The search here is near worthless but the AI assistant can be interesting but often wrong, best is an external search using the site: option to just look at the forum posts.

site:en.community.sonos.com


Airgetlam

Agreed that it’s system based, most likely router, although that reboot still isn’t a bad idea. The controllers merely show you what’s happening on the speakers (when they’re connected),the controllers merely show is merely a ‘window’ and a command generator…the system runs fine without one connected, as designed. 

Your tests suggest an issue between the controllers and the speakers, if the speakers are working fine on their own. I’ll be interested to see what turning off IPV6 does. Although it is supposed to be backward compatible, to my knowledge Sonos doesn’t explicitly support anything other than IVP4. But I’d certainly be digging further into that connection between the two phones and the router. With no guarantee, unfortunately, but it’s the only thing that matches your current posts. 


Airgetlam

Oh, one more thing…Sky has a bad reputation for connections, at least with me (a Yankee, far removed from the issue). I’m certainly glad you’ve cleaned up and simplified that network. 


Forum|alt.badge.img+18
  • Local Superstar
  • July 5, 2026

Before you disable IPv6 on Sky Hub Max, I would try disabling 6GHz radio’s on Orbi for client connections, if that's possible, depends on specific model(s). Restart Orbi(s) , no need to restart Sonos devices.

The issue you are describing, when your controller (phone) roams between APs/bands, suggests this.

You mentioned that Sonos still functions, plays from hard buttons on devices etc, so I’m pretty sure its how the APs are handing the traffic between bands, especially with IPv6 also enabled.

There is no need to reserve IPs in DHCP, this is a legacy.

If you then disable IPv6, disable this on the Sky Max Hub, if possible, will have to restart Orb(s) and Sonos devices. Sonos will still use the IPv6 linklocal address, just wont get a Sky UK IPv6 global address.


Forum|alt.badge.img+18
  • Local Superstar
  • July 5, 2026

 I would try disabling 6GHz radio’s on Orbi for client connections, if that's possible

If you change the security protocol to WPA2 (is probably default “WPA2/WPA3” Transitional Mode) this will disable 6GHz client connections, as 6GHz band requires WP3.

Another thought, is when the phone controller is having issues with transport buttons etc, open a web browser on a laptop and go to play.sonos.com (IPv4 only), and check if the Web App can see all Sonos devices and control them.


Stanley_4
  • Grand Maestro
  • July 5, 2026

There is no need to reserve IPs in DHCP, this is a legacy.

This is probably correct, it depends on the type, features of the version and of your DHCP server as well as some configuration options. The preservation of MAC to IP address mapping is a "best effort hash function" not a certainty but it usually is good enough.

When nothing else is working keep reserved IP address assignment as something to try. It is a fairly quick and easy process, fully reversible with even less effort. Faster than most calls to support.