Mac mini late 2012
macOS Catalina
2.6GHz Quad core Intel i7
16GB ram
Networking Gear & Setup Details
BT Home Hub used as router
2x Ubiquity UAP AC Lite AP’s
Connected Audio Devices
Sonos Play 5
Sonos Play 3
Sonos Play 1 x 3
Sonos Connect:
Connect: Library
Serial Number: B8-E9-37-94-59-A0:A
Sonos OS: S2
Version: 14.2 (build 67126143)
Hardware Version: 1.17.5.5-2.0
Series ID: C100
IP Address: 192.168.1.233
WM: 1
OTP: 1.1.1(1-17-5-zp90-2.1)
Bose Wave (Airplay)
Sonos play 5 (airplay, not enabled)
iMac Default
iMac Core Audio
Number of Tracks in Library
7000
Tidal
Description of Issue
NB, I made a mistake on the Sonos zones, I also have a Sonos Connect - details added above
This is a reopen of the previous thread, which was closed by @support.
The system had remained stable for a few days, after moving the Mac mini and connecting directly to the router but with out (as far as I can see) any changes has reverted to the previous behaviour.
Add images
Roon loses all of the Sonos endpoints. A reboot of Roon core several times then refunds them, until they all disappear again.
All the Sonos devices remain present and reachable in Sonos. All non Sonos end points remain reachable in Roon. The Sonos zones rarely stay connected for more than an hour now.
It seems this is an ongoing problem, @support could you please take a look?
Martin sadly I have been experiencing exactly the same issues for the last couple of releases as well, along with a number of other user’s.
3 reboots a day for the last several weeks, after months of stable working. It started the day build 903 was released with the first restart required within 3 or 4 hour’s of the install. It has not gotten better with any subsequent release.
Like you my Sonos devices are always available through this downtime in the Sonos app and reappear within 2 minutes of restarting Roon.
To expand on that, my individual Chromecast ultra is very consistently available, but the group of my Chromecast and Nest Display is not present in Roon very often.
Martin I fully agree.
When it happened last year I think I had a Sonos update at the same time as the first beta came out, so could have well been something that they did at the time (similar to Apple breaking Airpod stereo playback in an update).
I just wish Roon would give more information on what has happened beyond that they cannot replicate it. Plenty of people have had this issue and complained here. I’m sure there are plenty of us that would run test code or have additional system debugging enabled (I already did this to no avail).
It’s causing marital strife at the moment, I’ve set my wife up with Roon and created a profile, but then 4 times out 5 she opens the remote to play music all the Sonos zones have gone, so she reverts back to Sonos, which then begs the question, why have Roon.
I’ve had very little feedback from @support - someone pulled some logs a while ago but no follow up.
@support is there a way to raise a ticket, or at least get a response on this? The issue is still very much there.
Actions I have taken:
You mentioned that Roon has had issues with the BT home hub, is I changed the router for a Vigor 2866.
Roon core on Mac mini now connected directly to the router, not via a switch, as you mentioned Roon has problems with switches
Re initiated my two Unify UAP AC lite AP’s
Ensured all Sonos software is up to date
Updated router FW
Updated AP FW
Changed out Ethernet cables for new Cat5e/Cat6
Literally everything else on my network, including 3 Mac’s, 1 windows PC, Sky, Pioneer TV, Amazon Fire box, Airplay, multiple IOS and Android devices, printers, NAS, works fine.
Sonos works fine from any device using the Sonos app.
Airplay works fine from any IOS device, and from Roon.
The problem I see seems to relate to Roon and Sonos, and I see from other threads it goes back a long time, but I also see other supports tickets with Roon losing other audio devices.
I have had pretty much no response from Roon support, which is poor for software that costs over £100 per year.
Hi @support like Martin I am getting very tired of this issue and looking to start rebuilding my Sonos system once again and do more testing.
I have turned several of my Sonos devices off which seems to confirm my suspicion that the Roon discovery is the area with the problem. In Sonos the devices disappeared within a minute or two. In Roon they are all still showing (see below)
How often is the discovery process run and how does it keep track of the devices.
It really would be good to get some information from you, because this is really annoying and the silence only makes it more so. I am a life timer so I cannot cancel, and I really love Roon, but silence like this is what makes people quit Roon.
EDIT : About an hour later and all the turned off devices have disappeared.
Hi @Yaohan you chipped in an earlier thread, can you add anything if this is being ignored
Your question deeply resonates as the Sonos issue it’s something we’ve been wrestling with for a bit . We are making progress though, so all hope is not lost.
As far as your case goes, our technical team has performed an investigation and it looks like the discovery messages from your Roon Core are never making it to the Sonos zones.
If your Sonos is connected over WiFi, would you be able to at least temporarily try an Ethernet connection?
@beka out of interest was anything changed n b923 ?
As for me it takes about twice as long to lose Sonos now.
It has gone from 3-4 hours to normally 7-10 hours, so really on two restarts in a day (when I wake up and when I get home from work). If any changes were made I wanted to say they might be working.
I did turn off my Sonos Move a day or so before b923 came out, but fairly sure that made no difference.
Martin that’s interesting as previously I had lots of issues while connected to Ethernet and WiFi was the way to make it more reliable until build 903.
Maybe digging out my Boost and turning Sonosnet back on is called for.
Though I think I will wait to hear what the developments Beka spoke of were.
The Roon lost control was my most regular problem when I first had Roon and it might happen 10 to 15 times a day. Now it never happens but they all disappear twice a day…… choices
Just reporting here that, after my last network rebuild, which uncovered some IP conflict issues, I have had all of my Sonos endpoints up and running for about 3 days now with no “lost control of endpoint” errors.
As always, all of the other endpoints remain stable and I’ve just added another endpoint via a Pi with a HiFI Berry DAC over WiFi and that also seems to be OK, save a weak WiFi connection.
I have an IKEA Symfonisk (equivalent to Sonos) speaker on my network, in the children’s room. This is connected via WiFi and I have never had any problems.
Since build 923, my Nucleus very often loses the connection to the speaker, or it stops playing between queued songs, and it often does not respond to actions no matter what Roon remote. The solution is to reboot the core and restart Symfonisk, but it only takes a few minutes for the problem to reappear.
The speaker hangs particularly often when my daughter listens to audio books and the tracks are particularly short, sometimes only 30 seconds or similar.
Unfortunately, I find the network speaker very unreliable and no longer really useful.
Beka has said Roon are working on a fix for this so hopefully those of us that are afflicted have light at the end of the tunnel.
I understand that it is very frustrating but at least there now appears to be hope
. We are making progress though, so all hope is not lost.