I would perhaps check to see if you’re seeing the same issue with another service, like Amazon Music, and maybe try different Ethernet cable (and the ports) in use to see what difference (if any) that may make.

I’ve seen issues like this reported in the ‘distant’ past with Spotify, which was resolved by signing out the Spotify account from ‘everywhere’ via the online Spotify account settings and removing and reinstalling both the Spotify App and Sonos App in-built service from the mobile controller device, so that’s maybe worth a try too. 

Hi @Jack2m 

Thanks for your post, and for the diagnostics!

I recommend that you do the following:

1. Re-enable the WiFi card on the Connect - Settings » System » Living » Connect » Enable WiFi
2. Wait approximately 1 minute
3. Go to Settings » System » About My System and make sure Bedroom and Bathroom report WM:0. If they do not, try rebooting them by removing power for 10 seconds.
4. Make sure you have 3 rooms in your Sonos app - do not continue with step 5 if this is not the case.
5. Change SonosNet channel so it doesn’t overlap with your WiFi channel. Your WiFi is on channel 7, so we’ll put SonosNet on channel 1. Settings » System » Network » Change SonosNet Channel » 1. (channel 6 would be a better choice for your WiFi as then either 1 or 11 could be used for SonosNet, but if channel 1 works without issue, don’t worry about it)
6. I can’t see how close your Connect is to your WiFi router, but if it’s closer than 1m (3 feet), please separate them.
7. Ungroup your rooms, select Living as the current room, then regroup the rooms together. Selecting Living first will put the wired Sonos device “in charge” of the group, which is the most efficient in terms of network traffic.
8. Play some music and monitor for issues.

I hope this helps.

@Corry P @Ken_Griffiths thank you both for your precious replies.

It took me few days to give a feedback bcause I was testing the Ken's solution since Saturday night. So far it seems working pretty smooth and no disconnetion has occurred so far.

If any, in the next days, I will go on with Corry's procedure and see if any improvement.

@Corry P do you think it's better to follow the procedure anyway?

And also, is the Connect affected by the wifi signal even if connected via ethernet, as in my case? (My answer would be "yes, because SonosNet works through the Sonos devices and not through the wifi router")

Thanks again!

Keep you updated if any change

Hi @Jack2m 

I think it will reduce (or eliminate) the issues, and prevent more if you add to your Sonos system at a later date.

The Connect isn’t affected per se - it’s providing a WiFi signal for the other rooms to use, so the rest of the system will rely on it’s WiFi.

I see…

Strange enough that the issue never affected any of the other devices. The Connect was the only one disconnecting, even if the only wired.

Hi @Jack2m 

It’s all about the path that the music takes. The Bedroom was the Group Coordinator (it was selected first) so it was fetching the music from the source, via WiFi on the router. It then has to send the stream back over WiFi to the router so it can be distributed both to the other WiFi speaker and to the Connect. Why 3 WiFi jumps performed better than 2 WiFi jumps and a cable is not clear - there are no reports of a faulty ethernet connection in your diagnostics. It may help to reboot the Connect.

One more thing - if you’re happy the changes do work, and all the devices report WM:0 in About My System, you’ll want to remove the WiFi credentials from your Sonos system, so that the WiFi speakers only connect via the Connect.