Stack Audio Link no longer appears as a zone in Roon (ref#PV8MI3)

Support
1

What best describes your playback issue?

· A connected audio device is not appearing in Roon

What type of Zone is affected by this problem?

· *Network Zones* are affected.

How is the affected Zone connected to your RoonServer machine?

· Network - Ethernet

Which network audio protocol is the Zone using with Roon?

· RoonReady

Does the device show up at all in Roon Settings -> Audio?

· No, it does not show up there

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?

· Multiple output types are affected

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?

· Last 2 days

What are the make and model of the affected audio device(s) and the connection type?

· Stack Audio Link

Describe the issue

My Stack Audio Link has disappeared from Roon - it no longer shows up as a zone...

Describe your network setup

Direct ethernet connection to Vodafone router

2

Hello @simon3 !

We can see in the analytics report sent by your device that it had trouble when it initialized in the network last time.

Can you please try to turn off your Roon Server machine, Stack Audio, and Router? Then turn on the router first and let it boot. And then you can turn on your Roon Machine and StackAudio device.

Looking forward to your reply!

Regards.

3

I tried this twice - unfortunately it did not work…

4

Hi @simon3 .

Thanks for confirming.

At this point, since the device does not appear in Roon at all, the next step is to verify whether the Stack Audio Link is advertising itself on the network correctly via multicast (mDNS), which is required for Roon Ready discovery.

Could you please help us by capturing a short network trace on your Windows machine running Roon Server?

Steps:

  1. Install Wireshark from https://www.wireshark.org/download.html

    (please make sure Npcap is installed during setup)

  2. Launch Wireshark as Administrator
  3. Select your active network interface (Ethernet or Wi-Fi)
  4. While the capture is running:
    • reboot the Stack Audio Link
    • then restart Roon Server
  5. Let the capture run for about 30–60 seconds
  6. Stop the capture and save the file (.pcapng)
Once done, please upload the capture file [here]( https://workdrive.zohoexternal.com/collection/8i5239cc05950ac07456889838d9319545a82/external ). This will allow us to confirm whether the Roon Ready announcements from the device are reaching the Roon Server.

Thank you for your patience - this will help us determine whether the issue is network-related or specific to the device’s Roon Ready service.

5

Done and uploaded…

6

Hey @simon3 !

Thanks for uploading!

From the logs from your server, we could have seen that your Stack audio link 2 is a name of the zone with IP 192.168.1.196.

However, from this dump we can see that now a Ropiee device is sitting on this IP address . Can you please clarify the ip address of your Stack Audio device and whether you use it directly connected to the router ?

Thanks!

7

Hi, I think the Link is the only Ropiee device I have in the house and yes it is directly connected to the router - there is one switch between the two…

8

Hey @simon3 !

Thanks for clarifying. We can see that Link 2 is a Roon Ready device, which means it should be visible in Roon even without Ropiee.

Can you please clarify what made you put it on the bridge using Ropiee and how do you expect it to work ? with Ropiee or directly ?

Does your Roon Device not see the Ropiee as well ?

Thanks!

Regards.

9

Hi, I don’t know what you mean sorry - I just bought the Link, connected it and it worked with Roon. I believe it to be a Raspberry Pi based system, but I am not totally sure. I don’t know for sure what Ropiee is. Now for some reason Roon cannot find the link (Windows can no problem) - I have not changed anything or done anything differently…

12

Hello @simon3,

Thank you for the update.

From the latest diagnostic report, we’re seeing the following errors:

connect: Connection refused  
/dev/tcp/192.168.1.198/9200: Connection refused

This indicates that while the port required for the RAAT connection is reachable, there is no service actively listening on that port on the target device. In most cases, this means that the RAAT server on the Stack Audio Link is either not running, disabled, or the RAAT-related service/package is not functioning correctly.

Could you please clarify what you mean by the following statement?

(Windows can no problem)

Do you mean that you are able to access the web interface of the Stack Audio Link from a Windows machine without any issues?

13

Yes I can access the web interface from my Windows 11 PC, also it shows up in the “Network” part of File Explorer.

Do you have any suggestions to help with this?

Thanks

Simon

14

Good day @simon3 !

In such a case, it likely means that the device is visible inside the network, but it’s Roon Bridge capabilities might be broken/disabled.

Can you please visit the configuration settings of Link 2 in its web interface and check if there is any setting that allows managing Roon Ready on/off ?

Thanks!

Regards.

15

Hi @simon3,

The latest diagnostics to reach our servers from your account show a Zone connected via network with RAATServer matching the hardware in your description.

Are we correct in assuming this issue was resolved behind the scenes? Let us know if you require additional assistance; this thread will auto-close within a few days without any further activity from the OP. Thanks!

16

We’re going to allow this thread to auto-close now due to inactivity under the assumption that the issue is resolved. If you require additional assistance with this or any other problem, please simply reach out in a new support request and we’ll promptly pick up the case.