Thanks for taking the time to share your report! As a first step, let’s see about refreshing your RAAT Server database.
You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
To confirm, have you already rebooted both the Sonos device, as well as your Roon Server machine and router? If you haven’t yet, I’d safely stop Roon Server from running, and power cycle each device.
Can you also confirm there are no conflicting IP addresses in your Unifi network? Specifially the Wiim and Sonos in question.
Can you also try clearing your endpoint cache? You can do so using the following steps:
I have rebooted everything multiple times. I have not rebooted my router (Unifi DM Pro) since I know that does not have anything to do with this (been building software, networks, and PCs for 30 years). I definitely do not have any conflicting IPs anywhere.
Regarding the “Specifically the WiiM and Sonos in question.” I mentioned this early in the thread, but I do NOT own a WiiM Amp, so this is all about a current Sonos Amp being confused with a WiiM Amp. The only WiiM hardware I own is a WiiM Pro that is properly identified as Roon Ready. I have confirmed the IP.
I followed the instructions above, and it is still showing my Family Room Sonos as a WiiM Amp. If it matters, I am not able to play to that endpoint if I were to enable it. I press play, and nothing happens.
Edit: Another piece of info if it matters. My Sonos Amp is wired into my 24 port Unifi switch. It is not WiFi or Sonos Net. All but a couple of my media endpoints are wired.
I went through the process above again today (including reboots), and my Sonos Amp is still being identified as a WiiM Amp un Roon Tested. In “Other network devices”, it does show up as a AMP via Sonos Streaming.
Normally, I would go to Sonos Streaming, but as several other tickets have identified, the use of Sonos Streaming will peg at least one core to 100% until the server is restarted.
Thanks for letting us know. I am looking over your account diagnostics info and I see that the Sonos AMP was autodetected with this info. I am escalating your case over to our hardware team, thank you in advance for your patience until we hear back from them regarding this matter.
I see it after a little bit of Sonos Streaming. Once I stop, at least one CPU core will peg and never come down. Since I’m still experimenting, I moved my original Roon Server from an NUC i3 (4 core, Ubuntu), to a Synology 1520+, and now I’m on a ROCK installation back on the i3 NUC. The Sonos issue happened on all three installations. However, on my ROCK, I can only tell by listening for the fan and/or seeing the power utilization go up.