RoonBridge is not showing up on Roon Server (ref#CAP3JI)

Michael_Weiner · March 10, 2025, 9:04pm

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

PROBLEM:
I have installed latest RoonBridge from the roon download page, apparently successfully, on to a fresh installation of official Raspberry Pi OS, but RoonBridge is not showing up on the roonserver -> Settings -> Audio and I cannot select it as an audio zone.

WHAT I HAVE TRIED:
Turning off the fire wall on the Mac computer running roon server.
Shutting down the pi, then quitting and restarting the Roon Server (several times).

MORE INFO:

Roon server is running on a MacBook Pro with Sequoia 15.3.1.
I can send audio to a squeezebox audio zone on the same LAN as the Pi.
In the RoonServer, Roon Bridge does appear in Settings->About
->info there reports shows it on my raspberry pi os 6.6.51+rpt-rpi-v8
at an ip address on the same network as my computer with roon server.
With ssh connection from the Mac (with Roon Server) to the pi, I can see the
status:
michaelweiner@raspberrypi:~ $ sudo systemctl status roonbridge.service
● roonbridge.service - RoonBridge
Loaded: loaded (/etc/systemd/system/roonbridge.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-03-09 12:49:39 CDT; 2min 36s ago
Main PID: 932 (start.sh)
Tasks: 31 (limit: 755)
CPU: 21.453s
CGroup: /system.slice/roonbridge.service
├─ 932 /bin/sh /opt/RoonBridge/start.sh
├─ 938 RoonBridge --debug --gc=sgen --server RoonBridge.exe
├─1028 RoonBridgeHelper --debug --gc=sgen --server RoonBridgeHelper.exe
├─1034 /opt/RoonBridge/Bridge/processreaper 1028
└─1039 RAATServer --debug --gc=sgen --server RAATServer.exe

Mar 09 12:49:42 raspberrypi start.sh[938]: 00:00:01.168 Debug: PathForResource, filename: RAATServer
Mar 09 12:49:42 raspberrypi start.sh[938]: 00:00:01.168 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/RAATServer
Mar 09 12:49:42 raspberrypi start.sh[938]: 00:00:01.169 Debug: PathForResource, filename: RoonBridgeHelper
Mar 09 12:49:42 raspberrypi start.sh[938]: 00:00:01.169 Debug: PathForResource, candidate: /opt/RoonBridge/Bridge/RoonBridgeHelper
Mar 09 12:49:42 raspberrypi start.sh[938]: Initializing
Mar 09 12:49:42 raspberrypi start.sh[938]: 00:00:01.223 Info: Starting /opt/RoonBridge/Bridge/RoonBridgeHelper
Mar 09 12:49:42 raspberrypi start.sh[938]: 00:00:01.277 Info: ConnectOrStartAndWaitForExit RAATServer, path: /opt/RoonBridge/Bridge/RAATServer
Mar 09 12:49:42 raspberrypi start.sh[938]: Not Running (.o)
Mar 09 12:49:43 raspberrypi start.sh[1028]: 00:00:00.040 Warn: get lock file path: /tmp/.rnbhgem0-
Mar 09 12:49:44 raspberrypi start.sh[938]: Running

I don’t know enough to tell whether that status report means the roonbridge is running ok, or instead points to where the problem is. If it is running ok, then why can't I see it in roonserver->settings->audio?

I would appreciate any help.
Further details are below and I could submit logs if requested.

MORE DETAILS:
I have a Raspberry Pi 3 B. and
MacBookPro running Sequoia 15.3.1
With the MAC, did a clean install to the card of the recommended OS image from the Raspberry Pi site.
2024-11-19-raspios-bookworm-arm64-full.img.xz

When booted up the Pi 3 b, the command uname -a outputs:
Linux raspberrypi 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux

From the official Roon download site I downloaded and ran the script:
roonbridge-installer-linuxarmv8.sh

The script completed and announced it was successful and that RoonBridge should now be running.

Describe your network setup

Since I can access my squeezbox on the same router and ssh into the raspberry pi, and at times in the past have been able to access an old roonbridge on the pi, I don't think there are networking issues. I do have the os x firewall turned off and there is no vpn enabled.

benjamin · March 10, 2025, 11:23pm

Hey @Michael_Weiner,

Thanks for writing in and sharing your issue - and welcome to the community! We’re excited to have you here.

Lets see if refreshing your RAATSever database on the Mac running Roon Server may help.

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:

Create a Backup of your current Roon database
Exit out of Roon
Navigate to your Roon’s Database Location
Find the folder that says “RAATServer”
Rename the “RAATServer” folder to “RAATServer_old”
Restart the Roon App to generate a new RAATServer folder

Let me know if you still run into issues afterwards!

Michael_Weiner · March 11, 2025, 1:29am

Benjamin, thank you for your prompt response. I had some difficulty finding the RAATServer directory. It is in neither my Library/Roon nor Library RoonServer. (I have both.). The RAATServer directory is a direct subdirectory of the Library directory and there is no other instance in my Library. In that RoonServer directory I found Database and renamed it to Database_old_old as you instructed.

I restarted Roon. However, there is no new file Database created in RoonServer (according to the Finder app which I relaunched).

RoonBridge is still running on the Raspberry Pi as per the status command above.
But still:
Roon>settings>audio shows no RoonBridge.

However, I think you are on the right track about the RAATServer Database since Roon is not re-creating it.

What next?

BTW: My Roon version is 2.47 (build 1510) - production

Michael_Weiner · March 11, 2025, 8:00pm

Benjamin, I have reinterpreted your advice and now realize that even though it did not reside in the Roon or RoonServer databases, it was the RoonServer directory itself (which in my situation was found as directly under Library) that I should have changed to RoonServer_old, not it’s Database. I did that and restarted Roon, but no new instance of ~/Library/RoonServer appeared.

connor · March 11, 2025, 9:10pm

Hi @Michael_Weiner,

Thank you for your post. This new Raspberry Pi RoonBridge instance is visible to our servers at an IP address on the same subnet as the Mac; there’s most likely just a multicast forwarding failure at some point in the network pathway between server and the Raspberry Pi.

I recommend verifying that multicast forwarding is enabled in any router settings page involved. Please share a basic overview of the network topology between the Macbook and the Raspberry Pi, including any routers, managed switches, and mesh nodes.

Let’s refresh this RoonServer database entirely to make sure the previous Database folder reset hasn’t disocciated anything.

On the Mac, first make sure you have a reliable Roon Backup. Next, close both Roon and RoonServer and verify they aren’t running in the Activity Monitor. Navigate back to the ~/Library folder and find the RoonServer folder itself. Also delete the RAATServer folder and the Roon folder.

Now, reinstall Roon from the downloads page: Roon - Downloads

You’ll be prompted to set up a server on the Mac when you open Roon. Do this first and restore your Backup. Please let us know if the RoonBridge is then visible in Settings → Audio.

We’ll watch for your response. Thanks!

Michael_Weiner · March 12, 2025, 1:50am

Connor,

I followed your instructions and had partial success.

The Raspberry Pi came up in Settings>Audio as a device.

Attached is an image of that page.

However, its zones are mysterious. I don’t recognize them,

and can’t use them. I can select the ‘headphone’ as an output that

roon shows as playing, but don’t know where it goes.

So we still have some work to do.

I did not find anything in the router pages about multicasting.
Here is the view of the ‘Audio Page’

Network Details are below:

Also, I have a problem with restoring the backup.

The path where they are stored and I have selected the last three in turn :

~/Dropbox > bacs > Roon > RoonBackkups > ec96fbc1-591e…etc > xx

xx contains lots of files with recent dates which are probably the backups.

However I get the message: Error…(invalid root) with selecting RoonBackups

and also it’s subdirectories. Can you help me with this.

I have successfully activated my squeezebox

(connected via ethernet on a different LAN from the Pi).

NETWORK CONFIGURATION:

BIG PICTURE:
The Mac computer hosting Roon connects:
via ethernet cable to a 192.168.1.1 LAN
(to which a squeeze box connects via wire) and
via wifi to a 10.0.1.1 LAN
(to which the Raspberry Pi with HifiBerry connects via wifi).
The Mac can connect to the internet via either wire (192.168.1.1)
or wifi (10.0.1.1) — seamlessly.
The wire is usually unplugged unless I want to use the Squeezebox.
Both connections can be simultaneously active on the Mac
no special switching necessary except Roon selecting the output zone.
In fact both zones can play simultaneously different content.
Most importantly, the set up has worked for years with
Roon talking to the Squeezebox consistently and
to the Pi intermittently, on for a few weeks, off for a few weeks.
For our purposes of trouble shooting the pi, I think we only need
to be concerned with the 10.0.1.1 LAN WIFI connection.d

DETAILS:
Spectrum internet cable comes into the house to a modem.
Spectrum D3.1 eMTA
DOCSIS 3.1 Advanced Voice Modem
The modem connects with a short cable to a router:
802.11ac Wave 2 Router
Model Number RAC2V1K
This router has an address of 192.168.1.1
This Wave router has wifi and also connects via ethernet to
1.) an old Apple Airport extreme which talks to a Netgear extender
which I think we can ignore
2.) via a long ethernet cable to a Netgear powered switch.
3.) From the switch go several cables, The important ones are:
A. Ethernet to the Mac hosting Roon
B. Ethernet to a Squeezebox
Both cables are part of the 192.168.1.1 LAN:
C. The third cable from the switch goes to a router:
Nighthawk AX12 2-Stream AX6000 WiFi Router
with the address: 10.0.1.1
This 10.0.1.1 LAN is mostly wifi and host both the Mac with Roon and the Pi.

MORE DETAILS about the 10.0.1.1 Nighthawk router:
Router Firmware Version V1.2.9.5
It has a guest network. 5G is allowed.
The Mac has addressed: 10.0.1.52 2.4G allowed
Raspberry Pi: 10.0.1.88 2.4G allowed.
There are also a great many home control devices.
Upstream QoS is not enabled
There is no USB attached.
Security Status: Not Active

Wireless Settings

Region Selection
Region:
CanadaJapanNorth AmericaChinaRussia

Enable AX - This WiFi mode will enable AX features such as OFDMA

Enable OFDMA in 2.4GHz

Enable OFDMA in 5GHz

Enable Smart Connect - Let the router intelligently select the best 2.4 GHz or 5 GHz WiFi band for your WiFi connections. Smart Connect requires that the 2.4 GHz and 5 GHz WiFi networks use the same WiFi network name (SSID), security options, and password.

Wireless Network (2.4GHz b/g/n/ax)

Enable SSID Broadcast

Enable 20/40 MHz Coexistence
Name (SSID):
Michael’s Network
Channel:
Auto0102030405060708091011
Mode:
Up to 54 Mbps (11g) Up to 573.5 Mbps (11ax, HT20, 1024-QAM) Up to 1147 Mbps (11ax, HT40, 1024-QAM)

Security Options

None

WPA2-Personal [AES]

WPA-Personal [TKIP] + WPA2-Personal [AES]

WPA/WPA2 Enterprise

WPA3-Personal

WPA2-Personal[AES] + WPA3-Personal

Security Options (WPA2-Personal)
Password (Network Key) :
(8-63 characters or 64 hex digits)

Wireless Network (5GHz 802.11a/n/ac/ax)

Enable SSID Broadcast
Name (SSID):
Michael’s Network-5G
Channel:
3640444852(DFS)56(DFS)60(DFS)64(DFS)100(DFS)104(DFS)108(DFS)112(DFS)116(DFS)120(DFS)124(DFS)128(DFS)132(DFS)136(DFS)140(DFS)144(DFS)149153157161
Mode:
Up to 1147 Mbps (11ax, HT20, 1024-QAM) Up to 2294 Mbps (11ax, HT40, 1024-QAM) Up to 4803 Mbps (80MHz) (11ax, HT80, 1024-QAM) Up to 4803 Mbps (160MHz) (11ax, HT160, 1024-QAM)

Security Options

None

WPA2-Personal [AES]

WPA-Personal [TKIP] + WPA2-Personal [AES]

WPA/WPA2 Enterprise

WPA3-Personal

WPA2-Personal[AES] + WPA3-Personal

Security Options (WPA2-Personal)
Password (Network Key) :

David_Snyder · March 12, 2025, 4:30am

Hmmm… perhaps login to the Raspberry Pi and run this command:

sudo aplay -l

If the command is not found, you may have to install it. For example:

sudo install alsa-utils

You should see something like this:

sudo aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus

The specific DAC will be different, but you should see something that you recognize. If not try a different USB cable and/or make sure that your external DAC is powered on. If Linux can’t see your DAC, Roon can’t either.

Michael_Weiner · March 13, 2025, 7:56pm

David, that was very useful advice. the command showed nothing related to hifiberry. It did show the 2 mystery audio zones that had showed up in the reinstall of Roon. One was the raspbery pi hdmi port and the other it’s audio 3.5 jack. That inspired me to attach the Pi to my other DAC and bingo, it came right up in the aplay -l list. My Roon can play through that and the path Roon displays shows that it is going through RAAT on the Pi – so the RoonBridge on the Pi is working well. The problem must be either the HiFiBerry hardware or some software it’s missing on the Linux. There is a HiFiBerry support page about this: https://www.hifiberry.com/hifiberry-dac-software/ – which recommends adding these lines to /etc/modules:
snd_soc_bcm2708_i2s
bcm2708_dmaengine
snd_soc_pcm5102a
snd_soc_hifiberry_dac

However, after reboot, that didn’t fix the HiFiBerry not being seen problem. Unless some can contribute some insight about that, this topic can be closed. Thanks to all.

connor · March 13, 2025, 8:22pm

Hi @Michael_Weiner,

We’re glad to hear that the device announcement between the Raspberry Pi and RoonServer is established and some Zones are visible.

It sounds like the HiFi Berry sound card/drivers aren’t fully configured here - the device announcement for the USB port is reading out the chip manufacturer in Roon logs (Burr Brown).

HiFiBerry support will have the most precise instructions here, but the next step would be to verify the configuration in the Pi:

pi@raspberrypi ~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0

You can also run their diagnostic script:

wget www.hifiberry.com/files/dac/check-system
mv check-system check-system.dac
chmod u+rx ./check-system.dac
./check-system.dac

We’ll keep this thread open until we can confirm that RoonBridge isn’t misbehaving during device announcements, but the evidence points to a driver loading issue at the Pi → Berry USB stage, rather than the network path between RoonServer and RoonBridge.

We’ll watch for a response! Please upload a fresh set of RoonBridge logs at your convenience, as well: Log Uploader