Roon + Sonos not working

@ben, I will test as soon as I get home.

Regards,

For what it’s worth, I’m running 248 and I just had the “Roon has lost control” message with my Sonos. I don’t seem to be able to regain control, either. When I try to play a track, I get the same message.

Oh, interesting. Guys, I seem to have a reproducible bug. I have a track that, when played, causes Roon to lose communication with the Sonos. Please let me know what I can do to help you reproduce this.

All working stable here with Sonos.

I have continued to have Roon “lose control” of Sonos end points. When that happens, even Sonos cannot fully get it back. I have had to reboot the speaker to get it back.

Here’s what would help me the most with this:
A brief but accurate description of your system as show here. In particular, exactly what Sonos hardware are you using?

What track is causing the problem? Can you upload it somewhere I can get it? If you don’t have a convenient place to upload files I can PM you instructions for something.

Can you try using some DSP in Roon to change the stream sent to the Sonos slightly and see if it still crashes? The goal here is just to make any change at all to the audio stream and see if the Sonos can handle it, so just enabling DSP and the Headroom Management feature might be enough, or turning volume leveling to the opposite of whatever your current setting is. Changing a sample rate conversion setting would be even better, set Sample Rate Conversion to Custom and set the sample rate of the track that crashes to convert to something different from what was being sent before.

Do you observe any sort of pattern in when they crash?

What Sonos hardware do you have exactly?

Just to tack one more thing on here…what version of Sonos firmware are you running? I had a similar issue a while back and realized that I hadn’t done the 7.3 update (never use the Sonos app anymore). Applied the update and a similar glitch disappeared.

Worth checking if you haven’t done so already.

I have had it on two endpoint. One is Soundbar + Connect + Sub (those are bundled within Sonos as one thing) and a room with two Stereo Play 1.

Well, it figures. This morning, I was playing the playlist with the reproducible-crash track, and it played without issue. Sigh. I suppose it’s not 100% reproducible after all. I hate bugs like this as a developer so much…

I will try a few more times to see if I can get a reliable reproduction case again.

Like RobOK, I noticed that once Roon lost control of the endpoint, the Sonos app was also not able to properly control it. It could play tracks, but couldn’t show correct Now Playing information. Interestingly, after a little while of not trying to use it, Roon was again able to control the endpoint. I didn’t do anything specific, like rebooting the Sonos, so I’m not sure what caused the issue to resolve.

The track is Apple Lossless, and I am using volume leveling, so I believe that Roon is already applying some DSP to the track. If I’m able to get it to reproduce again, I will trying turning volume leveling off to see whether that has any effect.

FWIW, here’s the info you requested:

Roon 248
macOS X Sierra Server 10.12.4
Roon Core is on a Mac Mini Server Late 2012. 2.6GHz i7, 8GB RAM, SSD.
Music is stored on a Synology 1515+ NAS, shared via SMB
Music is Apple Lossless, imported by iTunes.
I have roughly 8700 tracks
Endpoint is a Sonos ZP-80 running Sonos 7.3

Intermittent bugs are the best, the extra time spent hunting makes finally squashing them much more satisfying.

We’re trying to track down what I think is a related bug internally. So far I haven’t observed any relationship between files and where it crashes. I suspect but cannot prove that it is more of a networking problem than a file problem.

I could use one set of logs showing the crash to check if the symptoms match what we’re seeing.

Let me know if you find any sort of pattern, just wanted to say that we’re still looking at this.

Yes, this is what I had too. I couldn’t figure out how to explain it but you got it right – Sonos App could still play songs but did not show Now Playing song name. I opened a new thread to keep our issues seperate but we can look for commonalities too.

So far, no. I did have it lose control last night in the same fashion, while playing something totally different. I happened to be in proximity to the Sonos player at the time, so I just yanked its power and rebooted it.

@ben, if it happens again, how do I get the log you asked for?

Here are the instructions for finding the log files: https://kb.roonlabs.com/Logs

Take everything in the logs folder, zip it up into one file, and upload somewhere I can get it. If you don’t have a convenient place to upload files I can PM you instructions for one managed by Roon.

Roon keeps a reasonably long log history around, logs from ~24-48 hours ago should still be in there, so you probably don’t need to wait for the problem to occur again.

Michael,

How has your playback been?

Rob

I haven’t had the problem again, but I have not been doing the same rapid track changes that seemed to be associated with the issue before.

I have seen the playback fail to start when I tried to change tracks, but I was able to make it start by hitting play a couple of more times.

Michael,

Just wanted to respond to say that I know exactly the issue you describe. I have encountered it with my sonos speakers and I have found a way to ‘gently’ avoid it. Basically, if I quickly skip 4-5 tracks one after the other then Roon loses control of the audio device (in this case the Sonos speaker). Once this occurs then Roon cannot play anything for a while. I need to leave it be for 5 mins or so before it can ‘regain’ control of the sonos device. I avoid this issue by being ‘gentle’ when skipping tracks. I have not yet reported it but I know the fantastic Roon team can tackle this quite well :-).

Best
Yiannis

Yes, this causes some of my Sonos problems too, but not all. I will try you more “gentle” approach to track skipping!

1 Like

I’ve been running Roon and Sonos very successfully for 3-4 months at least. I went away on vacation for 2 weeks, came home and my Sonos devices are no longer working with Roon. Note that I also have PS Audio DSjr (connected to network via its Bridge) and a MyTek Brooklyn (connected to Mac Mini running the Core) and both these devices still work flawlessly since returning from vacation.

I checked the two Sonos devices (Play:1 and Play:3) using the Sonos Application and can stream music to both via Amazon Prime music without any issues.

I’ve tried to disable and reenable the devices within Roon to no avail - still will not play through them.

When I returned home from vacation, booted up Roon and first thing I did was upgrade to 1.3 (build 259), upgrading the Core and all remote roon devices. Since experiencing this problem I refreshed to latest version of Sonos on both devices, still not working with Roon.

One thing I did notice is that Roon has a very bizarre IP address associated with both Sonos devices. I’ve checked the device IP addresses on my router and and they don’t match what Roon lists.

All my network devices are on 192.168.2.. Roon says the Sonos devices are sitting at 169.254..*. Roon does have all other devices (Core, MyTek, PSA DSjr, etc) with the correct IP addresses.

If I attempt to play anything to either Sonos device, I get no errors, the play button shows depressed but the song timer does not move. No music, no error messages, it just sits there.

Help

1 Like

I just rebooted the Mac Mini where the Roon Core resides and the Sonos IP addressed all refreshed to their proper addresses (192.168.2.*) and everything is working.

Problem closed.

Is this problem still occurring for you @Yiannis_Kouropalatis