SONOS SL1 en Beam "Roon lost control of audio device"

Hi There,

I tried the form:“Technical Support Request”, but this is a dog to go thru and does not address my issue. Better put an AI chatbot here with access to the solutions library.

Since a few days I cannot use my SONOS endpoints anymore. When selecting them I get the message: “Roon lost control of audio device”
This happened out of the blue as I have not changed any settings or hardware. Both my SL1 and Beam experience this issue. Using the SONOS app still works. My Devialet still works with ROON, which is my go-to device.
I have powered down all

SONOS SL1: Version 16.7 (build 84.1-63110) Hardware version: 1.28.1.6-2.1
SONOS Beam: Version: 16.7 (build 84.-63251 Hardware version: 1.23.1.10-2.1

ROCK v 2.48 (build 1517)
OS: Version 1.0 (build 259)
Running on Intel BOXNUC8I5BEH2
Connected wired to Router

SONOS running on my own wireless network with router set in slave mode and wired to main router.

As said, this setup has been like this for at least a year.

Researching this issue i also found this: (Sonos causing high CPU usage after playback stopped (ref#HMNFG1) [Roon Investigating] (Tracking thread) - #46 by Brian_Wood), which was closed unsolved??
I had stuttering music on my Devialet a few times, which is odd as it is wired to the same router as the ROCK.
Rebooting the network and routers did not do anything. I checked the NUC and found it hot and fans blazing, while I was running just a single stream. Rebooting the NUC was the only solve. Since its been ok.
I did have the issue in prior years that out of nowhere the fans started blazing. I “solved” this by removing the NUC from my office and placing it in my tech room.
Reading up though, it seems to be linked to SONOS streams. As these do not work anymore for me, the NUC is cold and quiet. Not the solve I was looking for though :wink:

Hi @DutchDuke ,

Thanks for reaching out with your query. I activated diagnostics mode for your account and what this does is upload a set of logs to our servers. Looking over your logs, it looks like your ROCK wasn’t able to get an IPv4 address at the start of the log until later on in the day. Looking over the Sonos error, I can see a No route to host error. Can you please try to perform a restart of RoonServer on your ROCK via the Web UI and let us know if this corrects the issue?

Hi Noris,

Thank you for the quick response and apologies for the delay in response. Wasn’t home this week.

This morning an update was awaiting after which both SONOS devices accepted ROON’s control again.

Good to go!

Cheers
DD

Hi @DutchDuke
That’s great news! We’re glad you’re back to being able to enjoy Roon.