Hello @Alessandro_Zizi,
Thank you for the update. I have now had a chance to go through the full set of diagnostic logs across all sessions — from May 26 through June 1 — and the picture is clear. The root cause of your playback stopping after one or two tracks is not a cloud connectivity problem. It is a WiFi instability issue specific to your Sonos ARC, which is being aggravated by how your Eero mesh network handles band steering and device roaming.
1. Your Sonos ARC is on 2.4 GHz while every other device in your home is on 5 GHz.
The diagnostic data embedded in the logs reports the WiFi channel each Sonos device is connected to:
Sonos ARC (Soggiorno) ChannelFreq="2437" → 2.4 GHz, channel 6
Bagno ChannelFreq="5640" → 5 GHz
Terrazzo ChannelFreq="5640" → 5 GHz
Camera da letto ChannelFreq="5640" → 5 GHz
Camera di Ottavia ChannelFreq="5640" → 5 GHz
The 2.4 GHz band has a longer range but far worse signal quality in a multi-room environment, and it is the band that Eero’s roaming algorithm most aggressively hands between nodes. Every time the ARC is handed from one Eero node to another, its WiFi connection momentarily drops — long enough to invalidate all active control subscriptions with Roon.
2. The ARC has reconnected to the network ~84,000 more times than any other device.
Each Sonos device records a BootSeq counter that increments every time its network connection is re-established. From the same log data:
Sonos ARC (Soggiorno) BootSeq="84489"
Bagno BootSeq="8"
Camera da letto BootSeq="9"
Camera di Ottavia BootSeq="9"
Terrazzo BootSeq="66"
Era 300 rear satellites BootSeq="31" / "38"
The ARC has re-established its network connection 84,489 times. Every other device is in single or double digits. This is the clearest possible evidence that the ARC is experiencing chronic WiFi instability — not a one-off event, but a permanent ongoing problem.
3. One of the Era 300 satellites changed its IP address between sessions.
On May 28, the rear-left Era 300 satellite (RINCON_F0F6C1C2A69601400) was at IP 192.168.4.26. By June 1, the same device was at IP 192.168.4.63. An IP address change on a device that should have a stable lease is further evidence that devices in the Soggiorno zone are dropping and re-acquiring network connections — consistent with Eero node handoffs.
4. Every playback failure follows the same chain of events.
The logs show this pattern occurring at least 21 times between May 26 and May 31:
Step 1 — ARC reconnects after a brief WiFi drop
→ broadcasts a topology update to the entire Sonos mesh
→ all other devices immediately echo the update (seen in logs as a
simultaneous zone update on all 5+ devices within the same second)
Step 2 — Roon's periodic UPnP subscription renewal fires
→ ARC rejects it: "PreconditionFailed"
(its internal subscription IDs were wiped when WiFi dropped)
→ Roon must tear down and rebuild the control channel
Step 3 — If a track boundary happens while the control channel is being rebuilt:
→ Sonos reports state: STOPPED
→ Roon's zone player enters state: Disconnected
→ Roon cannot issue the "play next track" command
→ After 5 seconds of silence, Roon automatically suspends the zone
→ Playback stops
The actual log entries for the May 27, 15:57 Rome session:
13:52:14 [client/sonos] try renew after renew: AVTransport, failed: True,
code: PreconditionFailed
13:52:15 [client/sonos] try renew after renew: RenderingControl, failed: True,
code: PreconditionFailed
13:52:15 [client/sonos] try renew after renew: ZoneGroupTopology, failed: True,
code: PreconditionFailed
13:57:47 [zoneplayer/sonos] state from device: STOPPED
13:57:47 [zoneplayer/sonos] zoneplayer state: Disconnected
13:57:47 [zoneplayer] BufferingTrack == NextTrack during ClearQueuedMedia,
setting _stop_on_next_track_transition
13:57:52 [zone Soggiorno] no playback for 5s, suspending to release audio device
13:57:52 [zone Soggiorno] Stop
What to do
The underlying cause is the ARC staying on 2.4 GHz and roaming between Eero nodes. There are two ways to fix this:
Option A — Connect the Sonos ARC to Ethernet (strongly recommended)
The Sonos ARC has a built-in Ethernet port. A single cable from the ARC to your nearest Eero node will immediately eliminate all WiFi roaming, stabilise the BootSeq counter, and prevent every UPnP subscription failure in the logs above. The Era 300 rear satellites will continue to use SonosNet (Sonos’s own mesh protocol, which they already use — the logs confirm WirelessMode="3" for both rear satellites) and do not need separate cables. This is the most reliable solution.
Option B — Force the ARC onto the 5 GHz band
If cabling is not possible, open the Eero app and try the following:
- Go to Devices, find your Sonos ARC by its MAC address, and check which Eero node it is currently associated with.
- Under Network Settings, if your Eero has Band Steering enabled, try disabling it. This prevents Eero from automatically moving the ARC between bands.
- Some Eero models also allow you to create a separate 5 GHz-only SSID — connecting the ARC to that SSID would keep it off 2.4 GHz permanently.
After making either change, please power-cycle the ARC (unplug from the wall for 30 seconds) so it re-establishes a fresh connection on the new band or cable. You should see playback become completely stable across playlist transitions.