Docker running on UnRAID v6.11.5 on 2x Xeon E5-2670
Roon Core v2.0 Build 1223
Networking Gear & Setup Details
Core connected via Ethernet to Centurylink C4000XG
Connected Audio Devices
2x Rasperry Pi 4b w/RoPieeeXL v2023.02 (0745) connected via wifi showing Roon Bridge v1.8 build 1125
2x Google Nest Audio speakers model GA01586-US
Multiple Windows clients on v2 build 1223
Multiple Android clients on v2.0 build 1219
Number of Tracks in Library
34700 tracks
Description of Issue
Roon is unable to see my Nest Audio speakers. I can use them by starting playing on the Android client and then manually selecting “Cast my audio” from the Google Home app, but the speakers never show up under Settings/Audio as available devices. Other Chromecast aware apps and devices can see them fine.
Just to put my Docker out of the loop, I set up a test core on a Win 11 system. As with my Docker core, the RoPiee bridges were found on the network without an issue but the Nest Audio speakers do not show up. I have rebooted the core(s) and the Nest speakers with no change.
Thank you for your patience while the tech support team worked through the queue to reach your report.
We’re certainly sorry to hear that these Nest speakers aren’t connecting as intended - below are a few steps to sort out what might be wrong.
Are these Nest speakers stereo-paired, or are they operating independently?
Diagnostics from your Core show multicast failures. Have you changed any settings on your Centurylink router lately? It might be worth entering the web administration page for the router and verifying that router firmware is up-to-date and the Nest hubs aren’t blacklisted on any network security or firewalls.
When you’re able to successfully connect to these devices via Google Home, are you using Bluetooth or WiFi? In most cases where a Google cast device fails to appear, multiple subnets on the LAN are the root cause. Since these Nest speakers aren’t announcing themselves to Roon, it’s possible they are on a separate subnet.
We’ll keep an eye out for your response and work from there. Thank you!
Thanks for getting back to me! Answers in-line below:
Are these Nest speakers stereo-paired, or are they operating independently?
I have tried it both as a stereo pair and as individual speakers. My core does not see them in either case.
It might be worth entering the web administration page for the router and verifying that router firmware is up-to-date and the Nest hubs aren’t blacklisted on any network security or firewalls.
Everything is on the latest firmware. No nest hub, but speakers are visible on the network.
When you’re able to successfully connect to these devices via Google Home, are you using Bluetooth or WiFi? In most cases where a Google cast device fails to appear, multiple subnets on the LAN are the root cause.
The Google Home app can see them outside of BT range, and I can Chromecast to them with my phone and other devices via WiFi. I only have a single subnet on my network, and both speakers show up on its device table. As mentioned in my first message, I can use the Google Home app to cast Roon indirectly via my phone’s audio.
FWIW, I recently got a couple of Ikea Sonos speakers, and my Roon Core has no trouble accessing them.
Hope that helps, and let me know if I can provide any additional information.
Thank you for the precision and detail of your response. Let’s escalate by regenerating a new RAATServer after you’ve rebooted both speakers.
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:
Rename the “RAATServer” folder to “RAATServer_old”
Restart the Roon App to generate a new RAATServer folder
We’ll pull new diagnostics automatically after you’ve refreshed the server, and these should give us an indication as to whether Roon is ignoring the devices erroneously, or they are failing to announce themselves properly on the network.