Roon Lost Control of Sonos System and Fails to Detect Sonos Port Device (ref#OUW1KU)

What’s happening?

· I'm having trouble connecting to Roon

What type of connection issue?

· Something else

Describe the issue

I am using a new Roon Nucleus One to stream to various Sonos speakers. When I first set it up a couple of weeks ago, everything worked fine; however, over the past week I receive a message that Roon lost control of the system. Further, Roon no longer finds the Sonos port device. Roon does find the four other Sonos devices on my system. They are all on the same WiFi and the WiFi is working fine. When I operate the Sonos system using the Sonos app, all works well. What must I do because it is very annoying since I am paying for Roon and recently purchased the Roon Nucleus One.

Describe your network setup

Arris modem and netgear router. About 400 mbs speed. All of devices on same network.

Hi @brad_fleetwood,
Thanks for reaching out to us about this issue. Besides the port device how many other devices are not showing up? If you temporarily switch your server back to your Windows machine does that server see the missing Sonos devices?
In the meantime please try restarting your Nucleus and Sonos devices to see if that helps.

I did everything that you said. The windows app shows each of the three Sonos devices as issue:
the Sonos Port, the Sonos One and the Sonos Roam as enabled and indicates their IP addresses. I am able to play the Sonos Port and One individually or as a group using Roon; however, if I add the Roam it loses control the devices. I am unable to use Roon to play the Roam alone. If I use the Sonos App, all play fine together or separately. On the Sonos PC App, each of the Sonor Port and the Sonos One show the Roon moniker. The Roam does not. I rebooted and reset it this morning. The problem appears to be the Sonos Roam and Roon. I have already spoken with Sonos and they do not see any indication of a problem with their applicaiton or hardware. Roon needs to fix this because I invested in the Sonos Nucleus One, so I am committed to Roon, but frustratingly cannot fully use it.

Hey @brad_fleetwood,

Thanks for sharing the additional information! We appreciate your continued patience while we continue to troubleshoot your issue.

Could you please set up a simplified network configuration for testing purposes? Would you be able to set up a direct ethernet connection from your Nucleus directly to your router, bypassing any network gear?

Next, see if you can hardwire your Sonos devices, even temporarily, and see if you continue to run into the same issues.

No. This is simply too hard. Sonos says that there is no formal agreement with Roon and clearly Roon does not work with the Sonos Roam. You need to fix this! I have gone through too many gymnastics trying to get devices to work with Roon. We are leaving this house for some time in two days. If Roon continues to be a problem with my other house system in Virginia I am returning the Nucleus One and will discontinue Roon. Roon is great WHEN it works. If you want to grow your user base, you need to make it easier and enter into formal agreements with devices. You are too darn expensive to be so damned finicky

Hi @brad_fleetwood ,

Just to confirm, if you switch back the Roon Server to your PC, the issue goes away, or does it remain? You can switch back to the PC by going to Roon Settings → General → Disconnect and then selecting the PC as the Roon Server (ensure you have opened the RoonServer app on the PC as well).

Can you let us know the exact local time + date + track you try to play to the Roam by itself and you notice the issue? This will help us narrow down the issue in the diagnostics.

I can’t. Roon took so long to get back to me on this issue, we leaving the house and have taken the Nucleus One down. I won’t be back to this house until next June. needs to up its game on customer service in line with the price you charge. Re the Roam, work with one and see how it works.

Hey @brad_fleetwood,

Thanks for taking the time to share you’re feedback (I’d also share it over in our Feedback as we have a dedicated area on community for this!)

We’ll go ahead and close this thread for now, but please let us know if you experience similar behavior in your other location moving forward. :pray:

This topic was automatically closed after 20 hours. New replies are no longer allowed.