Thanks @benjamin for this suggestion that I’m excited to try.
Quick update. I’m still travelling so will get to this most recent suggestion later this week.
Will update here in a four days time.
Thanks
Sorry I’m late to the party, but could you clarify a couple of points for us?
- DryTech? Do you mean DrayTek?
- DrayTek switches are managed switches, and, AFAIK, don’t have DHCP servers in them - is there also a separate DrayTek router in your network?
Thanks for letting us know @anon38974048!
@Geoff_Coupe makes an excellent point above as well. It may be best to bypass these managed switches as well, and let us know the results. Thank you! 
We are still working through a few things and will update this thread shortly
Hi @anon38974048,
Have there been any changes since you last posted?
Hi @daniel
We are trying to resolve an issue with the Devialet firmware at the moment. I will need a few week on this as the guy who installed it is out until Feb 12.
Thanks,
Hi @anon38974048 ,
No worries, let us know when you’re ready to pick this back up again, we’ll be here, thanks!
I have a Ubiquiti UniFi network with some SONOS speakers also. In one room, we have the original SONOS Playbar plus Sub and two SONOS One surround speakers. A few years ago, it seemed logical to me to connect the Playbar via a wired connection and then let it communicate to the sub and surrounds via SonosNET or Wi-Fi. It was easy to do since I had a small Ethernet switch in the cabinet below were it was mounted.
Not long after doing so (hours?), all heck broke out on our network. All of the activity lights on my 16-port PoE switch were blinking in unison, Internet access slowed to a crawl, Roon stopped working. I spent some time troubleshooting, including adjusting STP settings and weights, but long story short, removing the Ethernet connection from the Playbar and moving all SONOS products to Wi-Fi solved the issue.
It would have been interesting to mirror the switch ports for Roon Server and the SONOS Playbar and use Wireshark to see what was going on in realtime, but I didn’t think of it back then. My hypothesis is that the incident was not caused by Roon Server, but the discovery protocols it uses exacerbated loops created by the SONOS connections. Since then, I’ve been connecting SONOS products via Wi-Fi only and experienced no recurrences of these symptoms.
I’m not saying that it’s impossible to get SONOS products to work with wired Ethernet + Wi-Fi and Roon on the same network. But, if you can improve your Wi-Fi AP density such that Wi-Fi is sufficient for all SONOS products, you’ll spend more time listening and less time troubleshooting. At least that’s been my experience! 
Regarding your Devialet Pro, I’m not familiar with that product. I would try temporarily connecting it to the same Ethernet switch as Roon Server. Ideally, use a simple unmanaged switch, just for testing. You can buy one for less than $20. If Roon can’t see the Devialet Pro in this very simple configuration, your network is not the problem. But, if it shows up and works, you have more network troubleshooting (and simplification) to do.
Hi there,
Unfortunately my tech support is not able to attend today. I’m trying to get another follow-up date. As this is a commercial network, I’m not qualified to reconfigure it.
I will update you as soon as I have news.
Thanks,
1 Like
These days, Sonos seems to play nicely with ethernet. 8 of our devices are cabled with no problems, only one on wi-fi as I’ve run out of network outlets in the lounge. Need to install a couple more when SWMBO is travelling next 
Sonos’ use of its own Sonosnet Wi-Fi network infuriated me. I have 3 Unifi AC Pro APs, yet Sonos insisted on setting up its own mesh network. Not great when the house internal walls are made from render set cinder block, which does a fairly good impression of a Faraday cage…
1 Like
I suspect that was the source of my problems also. Individual SONOS speakers connected exclusively by either Ethernet or Wi-Fi are not the problem. It’s only when Ethernet is mixed with SonosNet that things go sideways for me, IIRC.
Result! I forgot about the now disused RJ11/F Type coax outlet that I put in when we had cable TV and a land line. Just need to switch out the modules for a couple of Cat6 and pull in a couple of bits of cable between here and the patch panel in the cupboard behind!
Hello @projects.kob ,
Thanks for letting us know, we’ll be on standby for your reply!
Hi @noris,
Just as an update, I have done a clean reinstallation of Roon and can now see all of my AirPlay speakers but the Arc app cannot see the Roon server despite logging and initially seeing it from a drop-down list.
This error message is showing:
{
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:504,“error”:“error: Error: ETIMEDOUT, response code: undefined, body: undefined connected? undefined”},
“external_ip”: {“actual_external_ip”:“89.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}
FYI: Sonos streaming is also back from the MiniMac though no Devialet (Roon Ready); we will get this sorted on Tuesday.
Thanks
Hi @noris
Thanks for your insights. After some troubleshooting, we found that the issue with the Devialet Roon Ready device was related to a firmware issue—an update was required to make it properly discoverable and allow it to work with the Roon Server.
Additionally, setting up NAT correctly and ensuring port forwarding was properly configured resolved the ARC connectivity issues. Assigning a static (or fixed) IP to the Mac Mini running Roon Server was also a key step in maintaining a stable connection.
In our case, we didn’t need to use Tailscale, as proper port forwarding on TCP 55000 was sufficient to enable external access to ARC.
I now have an issue using my preferref credit card with the account. How do I contact Roon to escalate it?
Thanks,
@anon38974048
Give this page a try:
Thanks v much
1 Like
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.