· Running Roon Version 2.57 (build 1598) on a Mac mini (2023 Apple M2 Pro Mac)S Sequoia). Attached is a Promise Pegasus2 external hard drive, with my Music files. The Wifi is an Asus ZenWifi AX network with 3 nodes. The Mac mini is directly connected to my hifi playing music via Tidal - that works. Issues: 1) There are Sonos speakers throughout my house. They are not showing up. At one point, they showed up, but I was not able to "enable" them. Need help with that. 2) I am not able to connect Roon to the Music folder on the Promise Pegasus. Need help with that. If I am not able to fix these issues, I will terminate my subscription before the free trial expires. I would really like for this to work. Please help. Thanks.
Tell us about your home network
· Asus AX6600 XT8. I have one attached to my router, and 3 additional nodes hardwired via cat 5 for backhaul.
Both of the issues you’re seeing point to a network segmentation / multicast discovery problem, not a problem with Roon itself.
Roon discovers Sonos speakers using multicast (mDNS / SSDP). If your Asus ZenWiFi mesh nodes are not in the same Layer-2 network segment, or if multicast forwarding is disabled, Sonos devices may either:
not appear at all, or
appear briefly but fail to enable.
Please check:
All ZenWiFi nodes and the Mac mini are on the same subnet (no guest network, no VLAN separation)
Multicast / IGMP / mDNS features are enabled on the router
Sonos speakers are not connected to a guest or isolated Wi-Fi network
Roon requires full local filesystem access to the music folder. On macOS Sequoia, this often fails if permissions are missing.
Please verify:
The Pegasus volume is formatted and mounted locally (not via network sharing)
Roon has Full Disk Access and Files & Folders permission in macOS Privacy & Security
The music folder is added via Settings → Storage → Add Folder, not via a network path
If the mesh nodes are segmented or multicast is blocked, both Sonos discovery and local device integration can fail exactly as you’re describing.
Once network segmentation and multicast are confirmed to be correct, these components should appear normally.
Are you using these Sonos endpoints in a group Zone within Roon?
If you’re still having trouble, please try the following test:
Disconnect any Sonos Zones connected via ethernet, relying entirely on WiFI. This will force the Sonos Zones off of SonosNet. Reload the Settings → Audio tab in Roon using the refresh button in the bottom right (this will force a network discovery cycle from RoonServer).
Do all the Sonos Zones appear?
Now, connect a Play5 or another SonosNet-capable unit via ethernet, leaving the rest of the Sonos units connected via WiFi. This will automatically activate SonosNet, opening up a separate “channel” through which the Sonos devices can communicate device announcements (a dedicated 2.4GHz band through which the endpoints communicate directly).
This should prevent network discovery traffic from taking unnecessary hops between mesh nodes.
Do you see any difference in which Sonos devices appear in Roon?
This thread is now closing due to inactivity. You can reactivate the topic thread by simply submitting a new support request here if you require additional troubleshooting or assistance.