Post-upgrade audio routing issue with KEF speakers and ARC connection failure (ref#FJJ8G2)

What’s happening?

· Other

How can we help?

· How do I ...?

Other options

· Other

Describe the issue

stopped working after upgrade. music plays through my server (mac mini) internal speaker, though it says its connected to my KEF speakers. ARC won't connect either.

Describe your network setup

Google Fiber, eero mesh, all working fine before upgrade

Hi @Jeff_McCord,
Thanks for writing in to ask about this issue. I think the best way forward is to take a look at your logs so we can get a clearer picture of what’s happening.

To send us the logs, you can either turn on your server for a few hours so we can collect them remotely, or you can follow the instructions here to locate them manually and upload them using our File Uploader.

Once you’ve uploaded the logs or had the server online for a bit, let us know and we’ll continue from there.

When you go to Settings → ARC in Roon, do you see any error messages listed there? That info will help us narrow things down further.

I restarted both my network and mac mini server. Feel free to collect the logs in a few hours when you can. I’m a newbie, and don’t fully understand how to set up zones, so maybe that’s the issue. But everything was working fine before.

As for ARC, I re-signed in on my phone, and it seems to be working now. I could not get it to connect soon my iPad, no error, just a wheel spinning saying it was connecting but it never did.

In my Roon app, it says ‘Roon ARC was unable to access the Roon server’ and gives the following diagnostics: {
“ipv4_connectivity”: {“status”:“NetworkError”,“status_code”:502,“error”:“error: Error: connect EHOSTUNREACH 136.aaa.bbb.ccc:55000, response code: undefined, body: undefined”},
“external_ip”: {“actual_external_ip”:“136.aaa.bbb.ccc”,“actual_external_ipv6”:“null”,“router_external_ip”:“null”},
“natpmp_autoconfig”: {“status”:“NotFound”},
“upnp_autoconfig”: {“status”:“NotFound”}
}

Hello @Jeff_McCord,

Can you please navigate to System Settings > Privacy & Security > Local Network on your Mac, and make sure Roon is allowed? If it’s already enabled, try toggling it off and then back on. Then reboot your Mac and check if the issue still persists.

If the issue continues, try manually restarting the Roon services on your Mac. Here’s how:

  1. Open Activity Monitor (you can find it using Spotlight by pressing Cmd + Space and typing Activity Monitor).
  2. In the search bar at the top right, type Roon to filter the processes.
  3. Select all Roon-related processes (e.g., Roon, RoonAppliance, RAATServer), then click the X button in the top-left corner to force quit them.
  4. Once all Roon processes are closed, relaunch Roon from your Applications folder.

Would you additionally let us know if something changed in the network setup or firewall settings?

Let us know if that helps!

Roon is allowed. I tried the Activity Monitor force quit but nothing changed. This seems to be a zone issue. I tried adding a second set of KEF speakers from the app, got them to play briefly, but the nect time I went back to Roon, there was only the one LR zone (which seems to be renamed). Roon is not seeing my speakers when I go to audio under settings.

Not seeing any speakers under ‘zone settings’ either. Before my KEFs and airplay speakers all showed up.

Hey @Jeff_McCord,

Thanks for the update! From a fresh diagnostic report, we can see the Kefs are recognized in Roon, but fail to properly connect:

Warn: [raat_ll/client] [KEF LS50 Wireless II @ 192.168.7.27:40795] failed to connect(0) No route to host

If you haven’t yet, I’d reboot your audio devices as well as your router, and see if you’re able to complete the connection. If you still have issues, let’s refresh your RAATServer database on your Mac.

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 this helps! We’ll dig further into your Arc issues once we get your audio devices properly recognized first. :pray:

I tried this. No change. Still doesn’t recognize any of my KEF or Airplay speakers.

Hi @Jeff_McCord ,

Can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed. If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.

It was allowed. Toggled on and off and restarted. No change.

Thanks for giving that a try @Jeff_McCord!

We’ve seen many reports of users updating to the latest version of Mac Sequoia (15.4) resolving device discovery issues, is this something you’d be able to do as well?

If you do update, let me know if you still run into issues! :+1:

I upated my OS and my KEF speakers are now showing up. But my Airplay speakers (Apple AirPods) that were showing up before are not showing up now. I would like to set up three zones, one for each of my KEF speakers and one for both. Since trying this before is what seemed to cause these programs, please provide me with a step to step guide for doing this.

And I have not had time to tackle my ARC issues. I will get back to you on this.

Hi @Jeff_McCord,

Great! We’re getting close to success here.

After you’ve put your AirPods in your ears - on your Mac, go to System Settings > Sound and confirm your AirPods are the active audio output.

Then : Open Roon > Settings > Audio. Look for a section called “This Mac” or “AirPlay Devices”. If you see your AirPods listed as an AirPlay device, click Enable and give them a name (e.g., “AirPods”).

Selecting playback from a single endpoint will allow you to use it as a single zone, so no additional work is needed there.

To set up a zone with all three Kefs - select one of them, then select the Kef zone icon > ‘Group’. This will allow you to select your other Kefs and create a zone with all three endpoints grouped together:

Be sure to rename the zones so you can clearly distinguish them. Let me know if this helps! :+1:

Another upgrade, and the same issue again. Roon not recognizing my KEF speakers. What is going on???

Hey @Jeff_McCord,

Thanks for following up! After successfully updating Roon, we see the following error when Roon attempts to connect to your Kef devices:

Warn: [raat_ll/client] [KEF LS60 Wireless @ 192.168.7.XXX] failed to connect(0) No route to host

It looks like something is blocking the connection — Roon is able to discover the device and is attempting to connect, but not succeeding.

If you’re using Eero, try the following steps:

  • Go to Eero app > Settings > Troubleshooting > My device won’t connect, then temporarily pause the 5GHz band.
  • Alternatively, try turning off Band Steering under Advanced Settings.

If that doesn’t resolve the issue, you could also try:

  • Disabling one of your active Ethernet connections as a test.
  • Fully rebooting your network — sometimes a fresh restart can clear up persistent connection issues.

Let me know how it goes!

Benjamin - I disabled 5g in eero, restarted roon - no difference. i cannot find band steering in eero, only client steering and it is turned off. ill restart the network, but sice this working fine before the first roon update, and i got it working fine again before the second, eight days later, this seems to be a roon software issue. both sets of KEF speakers are showing up and working fine through airplay.

I rebooted the network. No change.

Hi @Jeff_McCord,

You mention Roon is allowed in your Mac firewall - what happens if you temporarily disable your firewall, reboot your machine and Roon, and test for a Roon Ready connection to your Kefs?

We’re still seeing the same error message I’ve shared above, which is pointing to a blockage in the connection somewhere within the local connection.

How are the Kefs connected to your router / mac specifically? Can you test out a direct Ethernet connection from your router temporarily?