Skip to main content
Trending Lyricist I
April 21, 2026

Arc Ultra Surrounds Disconnect Daily After Extended TV Off Period

Using Sonos Arc Ultra with Sonos Ones as surrounds. The system works normally at first, but after the TV has been off for an extended period (overnight or a few hours), the surrounds disconnect and start blinking white.

Behavior:

  • TV off for a while > surrounds begin blinking white (attempting to reconnect)
  • Turning TV back on > surrounds continue disconnecting/reconnecting (sometimes rapid white LED blinking)
  • Rebooting the Arc Ultra > immediately fixes the issue
  • Happens consistently after extended idle

What has been tried:

  • Factory reset Arc Ultra
  • Disabled roaming assistant
  • Disabled airtime fairness
  • Reserved IPs for Arc Ultra and surrounds
  • Bound Arc Ultra and surrounds to main node (mesh: ASUS RT-AX88U + RT-AX58U)
  • 2.4 GHz channel manually set to 11

Additional observation:

  • When this happens, the surrounds appear and disappear on the network

Question:

What is the expected idle behavior?

  • Should surrounds remain connected to the Arc Ultra during standby?
  • Or is it expected that they disconnect and reconnect after inactivity?

This appears to be the Arc Ultra dropping the surround connection after extended idle and not re-establishing it properly until a reboot. However, even if the surround link is temporarily dropped, it seems unexpected that the surrounds would begin blinking white rather than remaining idle.

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.

34 replies

AjTrek1
April 24, 2026

​@ScottDDev 

There are questions I have yet to get answered. If you did and I missed your reply … my apologies.

Questions:

Do you have different SSID’s for your 2.4Ghz and 5Ghz bands?

Do you have a Guest Network active?

Together Everyone Achieves More = T.E.A.M.
ScottDDevAuthor
Trending Lyricist I
May 1, 2026

My system has been stable for a few days now, so I wanted to share an update in case it helps others.

After restoring default settings on my ASUS RT-AX88U, I made the following changes:

2.4 GHz Band

  • Disabled 802.11ax / WiFi 6 mode
  • Set Channel bandwidth to 20 MHz
  • Set Control Channel to 11
  • Disabled Roaming assistant
  • Disabled Explicit Beamforming
  • Disabled Universal Beamforming

5 GHz Band

  • Set Control Channel to 48 (non-DFS)
  • Disabled Roaming assistant
  • Disabled Universal Beamforming

After these changes, the Sonos Arc Ultra and surrounds have remained stable with no more auth/assoc/deauth loops.

The last changes I made before things stabilized were disabling beamforming and setting the 5 GHz control channel to 48, so one (or both) of those appears to have made the difference. I haven’t isolated which one yet.

ASUS is still looking into it, but so far this configuration has been stable.

ScottDDevAuthor
Trending Lyricist I
May 2, 2026

ASUS got back to me:

…Your changes:

Disabling Roaming Assistant
Disabling Universal Beamforming
Fixing the 5 GHz channel to a non-DFS channel (e.g., channel 48)

are all aligned with best practices for improving stability in environments where devices rely on consistent, low-latency peer connections rather than dynamic roaming behavior.

At this time:

This does not indicate a hardware fault with your ASUS router.
It is also not unexpected behavior, given how advanced wireless optimization features can interact with proprietary device communication protocols.
The configuration you applied is appropriate for ensuring stable operation of your Sonos system.

For ongoing reliability, we recommend:

Continuing to use a fixed non-DFS 5 GHz channel (36–48 range)
Keeping Roaming Assistant disabled for environments with stationary IoT or audio systems
Avoiding features that dynamically steer or modify client associations when using mesh or multi-node setups with latency-sensitive devices…

Stanley_4
Grand Maestro
May 2, 2026

If you avoid the DFS channels that leaves you 9 channels at 5 gHz but 165 can be iffy depending on your location.  

Channels 36, 40, 44, 48, 149, 153, 157, and 161 are all good first choices. 165 is a second but not DFS choice.

 

Good advice on DFS, avoiding it and the channels involved 52, 56, 60, 64, 100, 104, 108, 112, 116, 120, 124, 128, 132, 136, 140, and 144 is the safe bet. 

Some possibly bad advice, if the 9 non-DFS channels are crowded and you don't have a DFS priority user (usually radar) in your area you might be tempted. I was and picked channel 100, for no particular reason, and have been using it for a long time. I haven't had any DFS events where my Wi-Fi was shutdown or forced to change channels so I'm going to keep using it. If I'd have had any events I'd have tried other DFS channels or gone back to the safe ones.

Bottom line, go with the safe option but if you are willing to experiment with little or no support...