Roon not detecting Ropieee

Audio Gear Talk RoPieee
1

I’ve been using a RPi4 w/ RoPieee for years without issue. The RoPieee installation wasn’t updating to the latest version so I reformatted the SD card and imaged the SD card w/ the latest version (2026.03 (3367) [STABLE]. The RPi4 is up and running RoPieee. I’m able to open the Ropieee UI and see that my USB DAC (Mytek Brooklyn DAC+) is connected and recognized by the RoPieee. Everything appears normal in the RoPieee UI.

However Roon (2.64) is not detecting the RoPieee on the network (wired LAN, all Layer2), despite both being on the same subnet. Roon is running on a M1 Mac Mini and is working normally for local playback. I have the RoPieee UI open in a browser running on the same Mac Mini. I pulled an Ethernet cable and connect the RPi4 to the same Ethernet switch that the Mac Mini is connected to and Roon is still not detecting the RoPieee.

Does anyone have any ideas on why Roon is not able to detect the Ropiee or what to try next?

2
  1. have you enabled the audio endpoint in Roon settings? (under audio)
  2. can you send me feedback?
3

I don’t see the RoPieee endpoint in Settings –> Audio.

4

I also tried switching the Mac MIni from the wired network to Wifi and Roon is still not able to detect the RoPieee.

5

see above.

6

My apologies, what do you mean by ‘feedback’?

7

On the ‘advanced’ tab there’s an option ‘send feedback’. Hit it, and send me the identifier.

8

Ah got it… ‘3ab770d26dace9af’

9

It’s definitely a network issue. It seems DNS related, which results in a resolving issue.
Does this makes any sense? Any changes on your infra / router etc?

10

It’s possible… I am running a Pi-hole, checking now.

11

I disabled the Pi-Hole and restarted both RoPieee and Roon, but Roon is still not seeing the RoPieee. I also did not see that anything was being blocked in the Pi-hole logs related to RoPiee or Roon.

12

I also set the DNS server to the standard Cloudflare DNS (1.1.1.1) and that did not have any impact.

13

I saw that. But I think there’s an issue with local resolving.
Can you send me logs with the Pi-Hole disabled?

14

uhmmmmm… another thing: your unit only shows up in Roon (on the audio tab) when your DAC is powered on and connected.

And I see that at some point it is connected, but I also see disconnects.

Yeah. I think that I sent you on a ghost chase with that network stuff… I’m really wondering if this isn’t related to the USB DAC not being connected to RoonBridge: I see 2 ‘LOST’ events. That means no audio device, hence a no show in Roon.

15

The DAC is powered back up now and it’s showing up in the RoPiee ‘audio’ tab. I’ve tried powercycling the DAC as well as disconnecting / reconnecting it to see if that tripped something.

16

And when it shows up in RoPieee’s audio tab it should also be visible in the ‘audio’ section within Roon.

1 Like
17

Yep… thanks for taking a look… this does not appear to be a RoPieee issue. I had to go find it, but I have a Sonos Play:1 speaker that isn’t showing up in Roon. I also tried Volumio w/ the Roon plug-in installed and it wasn’t showing up in Roon either.

18

Wow, apparently rebooting the Mac that’s running Roon has ‘fixed’ the issue :flushed_face: I’m now seeing RoPiee and the Sonos speaker in Settings –> Audio and can enable them.

1 Like
19

Will stick to this post since it seems similar to me.
I’ve just send feedback with the unique ID 4f8431d1edc9979c.
My Ropieee is detected in Roon but enebling it in settings-audio take forever. AirPlay works just good, problem is only with the bridge.
Thanks up front for any hint.
Thanks for great job.