Roon on MacOS 15.0+ Sequoia: Audio Zones Disappear, Requiring Local Network Access Reset or RAAT/Roon/macOS Restart [Roon Investigating]

Hi

I have a similar issue with my 2018 Mac Mini which is our home’s Roon server.

Yesterday, I updated it to Sequoia 15.01 and Roon continued to work OK. This morning, however, the Roon server was unavailable. When I logged into the Mac Mini to look into the problem, Roon was running, but no audio zones were visible. After looking around the forums, I decided to restore Roon from a recent backup. That didn’t fix the problem. Then I came across a post that mentioned the Local Network toggle. When I checked to see if Local Network was set, it was, but I unset and reset the toggle anyway. Instantly, the audio zones came back. However, I still couldn’t see the server on any of remotes - hardwired Macs or iPhones or iPads etc. I restarted the Mac Mini to refresh network connections and once again, Roon on the Mac Mini wasn’t displaying any audio zones. I unset and reset the Local Network toggle and the audio zones returned.

It seems the problem occurs after startup - my Mac Mini is scheduled to shut down at night and restart in the morning (to save power - it’s an Intel machine), which is why it worked OK yesterday, but not this morning.

I’ve restarted the Mac Mini a couple of times since and the same thing happens. I have to to toggle Local Network on again to get the audio zones back. I don’t believe it’s a network issue - all my Macs are on CAT 6 Ethernet. The Mac Mini is only used for serving music and only runs two other apps apart from Roon. Both of these apps maintain their Local Network permissions after a restart. It seems to me that the issue is between MacOS Sequoia and Roon Server and until it’s fixed, it looks like I’m going to have to log into the Mac Mini every day to reset the Local Network toggle.

BTW - The Roon remote issue - “Waiting for your Roon Server” - was fixed by choosing “Select a different Roon Server” which allowed me to reconnect them to the Mac Mini.

1 Like

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

Recently, Roon doesn’t see my Eversolo DMP-A6 upon startup unless I reboot my router. It then works fine until I shut down the Eversolo overnight. I have to reboot the router every morning to get Roon to see the Eversolo.

Roon is on my Mac mini connected to router via Ethernet. Eversolo is also connected to same router via Ethernet. All are on the same subnet.

This is a recent development as it has worked perfectly before recent updates to the Mac, Roon, Eversolo and Asus router so it is impossible for me to tell weather any of these updates caused the problem.

Describe your network setup

Router is Asus ZenWiFi. Model: XT8. Mac and Eversolo are connected via ethernet

Do you’ve a chance to use another router?
There are some reports, that the Asus router needs every day a reboot to work properly.
And: Do you’ve tried to set fixed IP addresses for your devices?

1 Like

Yes. Please try another router. I own a dmp-6 because my buddy had so many issues with it on his network. He used an Asus router. I have a Eero setup and have not experienced an issue. I am leaning toward it being an Eversolo over Roon as well.

Thanks for your kind suggestions. I don’t have another router to try but this has all been working quite well for several years. This just started happening about a week ago. I’m sorry to say, but I’m the old fart in the room and don’t have a clue about fixing ip addresses. If you would be willing to elaborate a little on the ip suggestion I could try to search for instructions.

Hey @Rumpole,

Thanks for taking the time to write in and share your report! Below are some steps you can try in regards to setting up fixed IPs with your devices:

Log in to the Asus Router Admin Interface:

  1. Open a web browser and type in the address of your Asus router. The default address is usually http://router.asus.com or 192.168.1.1.

  2. Enter your username and password to log in. If you haven’t changed it, the default username and password are both typically admin. (You should change these for security.)

  3. Click on the LAN tab.

  4. Inside the LAN section, find and click on the DHCP Server tab.

  5. Toggle the Enable Manual Assignment option to Yes.

  6. Assign a manual IP:

  • You will see a list of connected devices, with their MAC addresses and current IP addresses.
  • In the MAC Address field, select the device to which you want to assign a fixed IP address. If the device is already connected, it should appear in the dropdown list.
  • In the IP Address field next to the selected device, enter the IP address you want to assign (e.g., 192.168.1.100). Make sure the IP address is outside of the range of IP addresses automatically assigned by DHCP, but within your network’s subnet (e.g., 192.168.1.x).
  1. Save your changes - Once you have filled in the MAC address and the desired fixed IP address, click on Add (or the equivalent button to add the configuration).
  • After adding the device, click Apply to save the changes.
  1. Reboot your router and devices.

Let me know if this helps and if you have any additional questions! :+1:

I changed the IP address for the Eversolo as per instructions and it has a new (fixed) IP address but it didn’t fix my problem. This only happens in the morning and I only have to reboot my router once. Once I reboot the router, all is good for the rest of the day. I can turn the Eversolo on and off throughout the day and all is fine. But overnight something happens that prevents Roon from seeing the Eversolo the next morning.

Hey @Gordon_B,

Thanks for the report! As a next step, can you confirm Roon has been listed within your Mac firewall with proper permissions?

An easy way to initially test this is to temporarily disable your mac firewall, and see if you run into the same issue (you may need to reboot after doing so for a proper test.)

Here’s more info on setting proper firewall permissions:

Hope this helps!

Hi,

Firewall is already inactive on the Roon Mac Mini.

As I mentioned in my previous post, there are two other apps on the Mac Mini with Local Network allowed - iStat Menus and iNet Network Scanner - and they retain Local Network access on restart. After startup, when you open Local Network, all three apps show they have permission, but Roon won’t display any network devices until I toggle the setting on and off.

This behaviour started after upgrading to Sequoia, so that seems to me to be the culprit. The Sequoia upgrade had made a mess of access settings in other apps on other Macs in the house, but once they’ve been re-set, they seem to stay fixed.

Gordon

I am having a similar issue. I regret updating to Sequoia. My M1 Mini is running headless in my rack, hardwired to my switch. Roon is working great if I remote into the Mini and log into it. But after it shuts down/reboots I need to share screen/log in from my MacBook into the M1 in order for Roon to work.

I have Roon Server set to launch at startup. Roon, Roon appliance, RAAT Server are all allowed in the firewall. I have toggled Roon/Roon Server in the network settings like I have read about. I even uninstalled Roon and reinstalled.

Right now I am set on having to remote into the M1 and unlock it every day I want to use Roon. Rather annoying at the moment and it’s making me feel like an idiot for not being able to figure this out :smiley:

1 Like

Hey @Gordon_B and @C_M2,

Thanks for the additional information and sorry to hear your issues persist. If you both could, please reproduce the issue, share the approximate date and time, and then please use the directions found here and send over a set of Roon logs (not Roon Server) to our File Uploader?

Thank you!

Got it, thanks for sharing the above info @Rumpole,

As a next step, could you please reproduce the issue, share a specific date, time of when you aren’t able to get it recognized, and then again when you, and then please use the directions found here and send over a set of logs to our File Uploader?

We’ll be on standby for your reply! :+1:

@Benjamin Ben for what it is worth (we have posted on this subject matter elsewhere) my conclusions are that it is absolutely nothing (every other non-Roon application continues to work) to do with my power-line adaptors. However, some more observations.

  1. Connectivity from my MacMini remote is ALWAYS fixed by toggling off / on Local Network access.
  2. However, occasionally I get the ‘this is taking longer than expected’ message and after a good 2 mins it eventually connects!
  3. Sometimes it just works first time.

Uploaded files this morning (Fri. 10/18 about 8:40 a.m.). I uploaded 2 zip files, first one is when I first open roon this morning (no eversolo), second file is after router reboot (shows eversolo properly and not just eversolo via airplay). I forgot to mention earlier in this thread that eversolo shows up only as airplay option until I reboot the router, only then does the regular eversolo show up. How can I delete the airplay option in roon? Does it matter? Don’t use nor need it.

As far as I am aware there is no way to hide the other transport options for a device. So just do not active the additional protocols and they do not show as an endpoint option.

Thanks, Craig.

Hello @Rumpole ,

Can you confirm if disabling and reenabling the network interfaces on your Mac also solves the issue temporarily?

Noris, at the risk of sounding like a dunce, I’m not sure what you are asking me to do. I’m not terribly computer literate but I can usually follow a set of instructions.

noris, deactivating and reactivating the network connection on the mac did work without having to reboot the router. After reactivation, the eversolo immediately showed up in roon “audio” settings. I’d rather not have to do these extra steps just to get Roon to see the eversolo. Is there a fix? Is it some network setting that needs to be tweaked or something?

Any word on this problem?