· My DAC, streamer, or speaker doesn't appear as a Zone in Roon
What type of Zone is affected by this problem?
· *All of my Zones* are affected.
Is your device connected directly to the Roon Server via cable or over the network, or is it chained through another device (such as a streamer, Roon Bridge, or Roon Remote)?
· It is connected through a different device (e.g Rasberry Pi)
Does the device play audio from another source when using the same connection?
· The device has no problems with another audio source
Have you checked that Roon is whitelisted in any firewalls?
· I've checked the firewall and the issue remains
Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device
· My devices are on a single subnet but is not visible to Roon
Do you have a complex network setup?
· Both the device and RoonServer are connecting to a *single router*
Try to disable any additional networking interfaces on your RoonServer machine.
· Disabling network interfaces had no change in behavior
Check to make sure RoonReady mode is selected on the device.
· I've checked this and the issue remains
If the device has multiple output options, do the other options work as expected?
· Only one output type is affected while the other output type works as expected
Is the device using the latest firmware as per the manufacturer?
· Firmware is up-to-date but the issue remains
Do you have an approximate timestamp of when the issue last occurred?
· Sun 02 Feb 2025
What are the make and model of the affected audio device(s) and the connection type?
Hi @Darren_Evans,
Thanks for reaching out to us for help with this issue. We need some more details to proceed with troubleshooting. Is this issue happening with Roon ARC or the regular Roon app?
Just to be clear, I don’t want to control any remote devices.
But I do want to be able to detect my DAC connected via USB and also to play audio via the speaker on the phone itself, neither of which are detected via settings / audio / refresh.
To be able to disable private zone on the speaker or DAC, don’t these need to be detected first ?
Please try to open Roon Settings → Audio on the affected device and disable Private Zone functionality from inside the Roon app on the device itself. Let us know if this works!
Just to confirm, you’re attempting two things here:
Enable Roon to recognize a USB DAC connected to an Android device: you have connected a DAC to his Android phone via USB but finds that Roon does not detect this DAC as an audio output option.
Play audio directly through the phone’s internal speaker using Roon: you also wish to use the phone’s built-in speaker for audio playback within Roon.
Both should be possible! If you plug the DAC into your Mac, does it work normally?
If you haven’t yet, remove the mobile app and reinstall a fresh version, and let me know if you run into the same issues.
Let’s also refresh your RAATServer 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:
Have you set the correct Exit Node in Tailscale when this issue is occurring? There should also be an “allow network access” setting in Tailscale, I would check to make sure this is enabled.
I’ve enabled Exit Node on my phone, not possible to enable exit node on the roon server though as it’s running on the NAS, at least there’s not the option to enable it in Tailscale.
When I enable Exit Node on my phone and connect via mobile only, the speaker is not detected.
When I enable Exit Node on my phone and connect via Wifi, the speaker is detected.
When you’re in this state, are you able to load up youtube or another audio/video app and connect to the headphones?
If you adjust your Arc settings to the lowest possible playback settings - disable ‘automatically pick best quality’ and download quality to ‘bandwidth optimized’, do you see any change in behavior?
Lastly, it may be worth performing a fresh reinstall of Arc - let us know if that changes anything as well.
Unfortunately, while Tailscale allows you to connect the Roon app to your server from outside your network, multicast discovery doesn’t work with Tailscale. This means you won’t be able to use any audio devices connected to your phone.
Some users have found workarounds in the Tinkering section of the forum, so I’d recommend searching there if you’re set on using the Roon app instead of ARC. Let us know if you have any questions—we’re happy to help however we can!
As mentioned above, using Tailscale for remote connectivity with Roon itself isn’t officially supported. It’s only been tested for NAT traversal with ARC. We don’t have any additional feedback or suggestions for remote connectivity with Roon that we can share officially in the Support section here.
That said, in the past, some users have relied on ZeroTier, which has more granular multicast forwarding settings that allow for basic Zone control. As mentioned above, it’s not a solution that has been QA’d in any official capacity by our team.
If you’d like, we can move this thread to Tinkering so the post history is retained. Alternatively, we can close this thread and you’re welcome to start a new discussion in Tinkering.
There are existing Feature Suggestions for remote connectivity with Roon itself. You can additionally lend your voice there.
