Roon server on M1 Mac Mini lost connection to devices after MacOS update (ref#NMIQCP)

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

At some point on October 15, 2024 my Roon Core lost connection to all of my devices. Roon Core is installed on an M1 Mac Mini that is running the current MacOS. The MacOS was updated for more than a week before the devices were dropped from Roon Core. My router is an Eero Pro 6e; also running the current firmware. I ran a new update to the Eero firmware today (October 16) as part of my investigation the Roon Core issue. So, the Eero firmware update was installed after the Roon Core dropped all of my devices. I have read through the Help forum, and see that a couple others have had this same issue. I have restarted the Roon Core, restarted the router (multiple times), disconnected and re-connected device ethernet connections (all devices, except one are ethernet connections), also powered down (and unplugged) my PS Audio Airlens (just one of my devices), and none of these actions has allowed me to have the Roon Core re-discover all of my devices. What can I do to re-connect my devices?

Describe your network setup

Router is Eero Pro 6e; modem is Arris Surfboard S33; main switch is Netgear GS324P; Roon Core installed on M1 Mac Mini running Sequoia 15.0.1. Devices include: PS Audio Airlens (ethernet); (2) Primare NP5 (ethernet); (2) BluSound Pulse speakers (ethernet) and (1) BluSound Pulse speaker (wifi); a Wiim Pro (ethernet).

Take a look at this post, it’s seems to be an issue caused by the latest MacOS update.
The solution for a number of people is here

1 Like

Michael, thank you for the response. I saw that post earlier and checked the settings on MacOS, and the settings did have Roon as allowed. So, I did the cycling and restarted, and still no devices discovered. Nevertheless, I just did the process again in case it would be successful after my various re-starts, and still no change. Again, thank you for the response, but this is apparently not the solution to my issue.

No problem, it just seems similar.

There do seem to be a number of Mac user’s suffering connection issues

Hi @tjparkes ,

Welcome to the forum and thanks for your message. I am looking over your account diagnostics and I see your Roon Server recently registered two IP subnets - 192.168.4.XYZ and 192.168.5.XYZ. Which subnet are your devices supposed to be located on? Have you made any configuration changes in this area recently?

Noris, thank you for the follow up. I also noticed the recent registration of the two subnets in your above comment. Frankly, this is my “front runner” for the source of the problem. I did not make any configuration changes myself, and I have the Eero router set up for automatic IP assignments (and always have had it set up this way). However, I never noticed before having two IP subnets (I previously only had the 192.168.5.xyz subnet). I suspect that Eero (perhaps due to an update) took it upon itself to create these two subnets. So, I did investigate this issue on the Eero forum, and apparently Eero will use two subnets when the number of LAN IP addresses gets to a certain number, and I did recently add a few new devices as part of a separate computer upgrade. However, the Eero folks noted that these two subnets are under the same subnet mask and that all devices from either subnet will be seen as part of the same network. In addition, I checked the Mac Mini that is the Roon Core and the audio devices and they are all still on the 192.168.5.xyz subnet. So, again, my gut is telling me that this may be a factor, but the Eero forum and my own review of the LAN IP addresses is saying that it should not be a problem. That said, I’m striking out on a solution.

@tjparkes is it possible to ensure that all of your Roon devices and the Mac Roon server are on the .5 subnet (or alternately all on the .4 subnet)? Roon requires this, but given that maybe the eero router created a new .4 subnet, it may have re-allocated some of your Roon devices between the subnets.

Robert, thank you for your follow up. So, I have everything working again. Bottom line, Eero did an automatic update on October 14th (I found this in the update logs). I’m pretty certain that at that point, Eero created the two subnets (192.168.4.xyz and 192.168.5.xyz). All of my music devices were on the 5.xyz subnet, including (here’s a partial key to the issue) one of two IP addresses assigned to my Roon Server. However, Eero also assigned a 4.xyz IP address to my Roon Server for ethernet. So, after a very tedious analysis of all my device’s IP addresses, I assigned static IP addresses to the Roon Server in the 5.xyz subnet (for both ethernet and wifi). Then I restarted the Roon Server and my Eero gateway router. AND, NOTHING. So, back to the IP address analysis, and (here is the other key to ultimately resolve the issue) I found that the gateway router IP address was on the 4.xyz subnet, and the Eero app (in the current version) does not have a means to assign a static IP address to the gateway router (at least, not without a full manual assignment of static IPs for everything on the network). So, I went decided to assign static IPs in the 4.xyz subnet for the Roon Server (again, both IP addresses) and all audio devices; restarted the Roon Server and Eero network, and this time all of my audio devices re-appeared in Roon. Hopefully, this helps the Roon team and anyone else that may have a similar issue. Thanks to everyone who responded.

4 Likes

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.