· Roon will suddenly hang up after a random period of time, it may prompt "Uh somethings not right, can't find the server" and then after a few minutes reconnects, other times I have to quit it repeatedly for it to finally start again. Other times it loses a device. The system is hardwired from the router to a switch and directly to the Roon Nucleus and my Lumin PI is also hardwired - as is my laptop I'm using most of the time to choose my music. So in my mind they're all on the same hardwired network. The switch is 1G unmanaged and has been fine for years. Sometimes other roon endpoints hang up and drop out too.
Tell us about your home network
· cable router is eero pro 7, switches are netgear 1 g unmanaged.
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
it happened this morning around 6 to 630 AM Eastern time. It showed it had lost connection to the Roon server and hung up for several minutes and then slowly reconnected again. Often when it does this it is hung up and unable to reconnect for 15-30 minutes. Some days it can do it once in a 1 to 2 hour listening session, other days it’ll do it several times. It does it almost every session.
Well this is convenient. It just stopped playing at 8:47 AM Eastern in the middle of a song - the earlier drop out between 6 and 630 am eastern was when I was using a PS Audio Directstream. Just now it was when I was/am using an Eversolo DMPA6- it makes no difference what end point. So in two hours or so this morning I’ve had two sudden shut downs, looking for Roon server episodes. Just imagine how many times this occurs daily and how painful it is to deal with. Thanks
The diagnostic logs from the morning hours confirm that the root cause of these dropouts lies within the local network infrastructure, rather than the Nucleus hardware itself.
The system is recording clear DHCP failures—meaning the network is struggling to assign and maintain stable IP addresses for your devices. Additionally, there are severe communication delays with the audio endpoints themselves. For example, exactly at 6:15 AM, right before your PS Audio DirectStream DAC disconnected, the system recorded a critical data transmission delay (long rtt sync), followed immediately by a complete loss of connection.
Since these symptoms point directly to a physical connection or traffic routing issue, please take the following foundational steps to stabilize your setup:
Simplify the Network (Crucial Step): Unmanaged switches can sometimes hang, block discovery protocols, or drop DHCP packets. Please temporarily remove the Netgear switch from the chain and connect the Nucleus directly to the back of your Eero Pro 7 router.
Swap Ethernet Cables: Try replacing the cables connecting your Nucleus and your streamers. Even a slightly damaged cable can cause intermittent dropouts.
Change Ports: Plug the cables into different, alternative ports on both your router and switch to rule out a dead or failing port.
Would you please test the system with the Nucleus connected directly to the Eero and let me know if these sudden disconnects stop?
Thanks. Not sure I can connect the nucleus directly to the eero as its output is feeding a switch which then branches out several (6 or7) ethernet cables to feed my tv, a bluseound node, a sound bar etc. In addition, one of the ethernet cables runs thru the floor down to another switch and a TV and then from that switch an ethernet cable goes into my media room to another switch which has about 6-8 devices attached ( the lumin, the nucleus, a blusound node, another TV and a couple other devices) I can move the nucleus closer to the Eero router as doing so would require removing ALL ethernet devices in the house f rom the network. What do you advise? thanks
Thanks for the detailed explanation of your network layout — that helps clarify things.
Based on your description, your setup includes multiple cascaded switches and several downstream branches feeding many devices. While this can absolutely work, it does increase complexity and the potential for DHCP instability, broadcast congestion, or intermittent routing issues — which aligns with what we’re seeing in diagnostics (DHCP failures and endpoint communication delays).
If moving the Nucleus directly to the Eero isn’t practical without disrupting the entire household network, placing it on the first switch connected to the Eero (as you suggested) would be a good next step for testing.
That said, given the size and layering of your network, this may go beyond simple cable/port troubleshooting. At this stage, if the behavior continues after basic isolation tests, I would strongly consider having a network engineer review the topology and traffic flow. A professional analysis (checking DHCP lease behavior, packet loss, spanning tree issues, loop detection, and switch health) would likely identify the root cause much faster than iterative trial-and-error.
From the Roon side, the diagnostics consistently point to network-layer instability rather than a Nucleus hardware issue. Here is the random example:
Another related question that I was looking into last night is assigning a fixed or static (?) IP address to the Nucleus and or to the PS Audio and the Lumin? Some articles said it was good to do when you have devices that get lost on the network, others said it was not useful- both articles said that the unmanaged switches just pass the IP address that’s assigned through to the device and the switch itself is nothing more that a pass through device. Eero does have the option to assign/reserve an IP address by device.
Well, after moving the nucleus so it’s connected to the switch closest to the modem I thought it was going to be fine - but no. At 10:07 it just dropped out again and hung up. It seems hopeless frankly. I don’t understand why it keeps losing connection- it’ should be able to be stable connected to a switch leg thats attached directly to the modem. It’s on a new CAT cable too. Its not possible to hook it directly to the modem as it requires taking ever other connected device in the house offline (the modem has one input and one output. Unless a fixed IP address might work for the nucleus I think my Roon days are coming to an end. It’s still down- 10 minutes now- and won’t reconnect. Just suddenly started again. It’s not a bad wire and now it’s literally on an 8 ft cable to a 6 port switch wired to the modem. IT should def be capable of sunning this way as no one wil lbe able to connect the Nucleus directly to the modem.
Ok. I spent an hour and a half with Eero technical support as they looked into my network, watched the nucleus and had me try everything they have to correct what they say is a Nucleus problem only- no other devices on my network ever have any issues.
They did a network system update
They changed and locked the DNS
They reserved an IP address for the nucleus.
They have me move it to only one switch away from the router.
We did a hard reset on the network switch its attached to.
We changed the cable.
We’ve done everything possible from their end and my end. They believe firmly it’s a Nucleus / Roon issue, not a network issue. I tend to agree as its the only device out of 50 on my network that consistently has problems, often several times a day. Every other device has 100 % uptime so why would it be a network issue with just the Nucleus? There’s also many, many people in your forum with similar and ongoing complaints.
I ordered a Mac mini that my local dealer swears will fix the issue as he had had dozens of Nucleus customers with the same issue and once the Nucleus was replaced with the Mac Mini the problems stopped.
Pls look into the technical log again from this morning to note the drop out at 10:07 to see if anything is noticeable.
Thank you for the update and for the extensive work you’ve done with Eero support.
I’ve analyzed the diagnostic logs around the 10:07 AM dropout, and they provide a very specific technical picture. At exactly 10:05:27 AM, the Nucleus recorded a critical event: no data received for >10000ms. Killing connection.
For 10 full seconds, the Nucleus was waiting for a response from the network that never arrived. What is even more telling is what happened when the connection “thawed” around 10:12 AM. Your logs show a massive “burst” of commands from your Bluesound endpoint:
Trace: [zone BlueSound Fireplace] BlueSound Fireplace received transport control from Bluesound NODE: play(this command repeats over a dozen times in a single second)
This confirms that the commands were “queued up” or stuck in a network buffer/switch bottleneck and then suddenly flooded the Nucleus all at once. If the Nucleus were failing, it wouldn’t be able to receive and log this rapid-fire burst of data immediately after the hang-up.
A crucial request for the next occurrence: Because the Nucleus was rebooted, the low-level system logs (which tell us about the hardware and OS health) were cleared. To help us definitively rule out a hardware fault, please do not reboot the Nucleus if this happens again. Just note the timestamp and let us know. This will allow us to pull the persistent system logs and see exactly what the Ethernet port was doing during that silence.
In the meantime, please ensure all “Advanced Security,” “Eero Plus,” or “Disney+ Content Filters” are disabled in the Eero app, as these are known to interfere with Roon’s communication.
Will do. the nucleus/roon were using the blusound node as an endpoint when roon went down. I may have been hitting “play” on the roon app trying to get it to kick in and play again which might explain the commands you saw- not sure.
I wasnt listening more than ten minutes on the PS Audio DAC just now and roon lost connection- it ran all day on the bluseound fireplace no problem. 6:47 pm it went down. I give up at this point, all I get is frustration pure and continual fristration with roon. Its not normal to spend hours on forums and tech support and hours with eero and having your home hard wired all in effort to listen to some streaming that your’e paying for. And it seems absolutely impossible for roon to figure out.
super frustrated and unhappy and exhausted. I just get a drink, turn on my system and sit down and - boom- roon goes dead- again - its every day. We can put man on the moon in 1969 but we can’t get roon to run for more than an hour in 2026.
In this case, the playback failure is being caused by a chain of authentication and connectivity issues between your server and streaming services. Let’s see if the following help:
Go to Settings > Services.
Log out of Qobuz and Tidal completely.
Reboot your Roon Core.
Log back into both services. This forces the generation of fresh security tokens
So…Tidal shows Im already not logged in- I hadn’t noticed that before. When I go to log in it asks for my tidal username and password, accepts them, then roon asks if I want to allow to connect, I say “yes”, it spins, I get a pop up saying its now connected yet the roon screen for services stays greyed out with a blank white square in the middle and it shows tidal is in fact NOT logged in.
thanks, i tried severeal times, then went out to tidal, looged in and out and then tried roon again. My server machine is my nucleus correct? I’ll log out and back into quboz too this morning and then log out of roon too, then log back in or should I just log out/into quboz then reboot by turning off my nucleus ? Unplugging power from the Roon Nucleus is an acceptable way to force a reboot? Do I still need to log out of my desk top roon app or does “quitting” the app on the desktop do the same as logging out ?
