· Hi I had a topic ID is #FPA3J6 and at the beginning of that I thought the nucleus had a problem but it was closed. Now in the meantime I had 2 other issues. I have the nucleus and the Eversolo A6 wired. And at 23 of February I didn’t get a signal from roon on the eversolo so I turned the nucleus on and off and it worked. Now just an hour ago I also got no signal but I investigated. I started up the eversolo app and it got no connection with the app, not when booting it up or putting the internet cable in and out. I could use the touchscreen and remote control. Only after booting the nucleus on and off I got connection with the eversolo app and it was recognised in roon. And yes when eversolo was down I could use roon to play on the Ipad.
In all the time I have had the nucleus (3 months) I never had problems with my pc connecting to the nucleus. I will report back when it happens again and if you have Idees so you can monitor it better please tell me. I already know for you it’s better to first restart the nucleus so I will do that.
Thank you for reaching out. We’re of course eager to continue troubleshooting and we apologize that your previous thread closed prematurely.
When you restart the Nucleus, it initiates a device discovery cycle. That will send out broadcast traffic across the network, requesting available devices to announce themselves. It sounds like the Eversolo responds to these discovery requests, but some network conditions change and then render the device invisible to RAAT after a certain period of inactivity.
This is almost certainly a resolvable local network issue. In your previous thread, you mentioned you had a modem/router combination from Ziggo as your main router in this setup.
Is this your only router? Are the Nucleus and Eversolo connected directly to this router or to separate mesh nodes/switches/access points? Please list any other network hardware in this setup.
Try hardwiring the Eversolo to the same switch/router as the Nucleus if you haven’t already and see if you can reproduce these network dropouts.
We’d like to take a closer look at RoonServer logs to see if we can pinpoint dropouts, but your Nucleus has so far not responded to automatic log requests. At your convenience, please use the directions found here and send over a set of logs to our File Uploader? We specifically need the logs within the RoonServer folder.
I’m sorry there is a change in setup. I have moved the eversolo to another room and am using a tp link tl-pa7017p kit. The nucleus is put in a TP-Link TL-SG105 which is linked to the ziggo. It’s now
The diagnostic traces show that there are two completely different subnets active on your network. We can see IP addresses being assigned in both the 10.5.x.x range (specifically 10.5.0.2) and the 192.168.178.x range.
Roon relies heavily on Multicast to discover and maintain connections with audio endpoints, and this requires all devices (your Nucleus, the Eversolo, and your remote devices) to be operating on the exact same subnet. If the devices are split across these two different subnets, they will inevitably lose sight of each other.
To resolve this, please check the following in your router and network settings:
Single Subnet: Confirm your network topology and ensure that both your Nucleus and the Eversolo A6 are connected to the exact same subnet (most likely the 192.168.178.x network).
Device Isolation: Ensure that any form of AP Isolation, Client Isolation, or Guest Network settings are completely turned OFF on all of your routers and access points.
Multicast: Verify that Multicast routing (and IGMP Snooping, if applicable) is enabled on your network equipment so discovery traffic can flow freely between devices.
Please let us know what you find when checking your router configuration!
Hi I’ve given the eversolo the exact same ip address as the nucleus now the eversolo a6 first row the one with the ip address in has fallen away when I’m in the browser of the modem. Is that bad?
Yes, that is definitely causing the new issue you are seeing! Do not worry, as this is a very common mix-up when dealing with network settings.
By giving both devices the exact same IP address, you have created what is called an IP Address Conflict.
Think of a subnet like a street, and an IP address like a house number.
Being on the same subnet means both devices need to start with the same first three numbers (for example, 192.168.178.x).
However, the last number (the x) must be completely unique for every single device on that street.
When two devices have the exact same “house number,” your router gets confused and does not know where to deliver the data. As a result, both the Nucleus and the Eversolo will lose their network connection and stop working properly.
Change the Eversolo’s IP Address: Go back into your Eversolo network settings and change its configuration from “Static/Manual” back to DHCP (Automatic). If you prefer to use a static IP, you must choose a final number that is not being used by the Nucleus or any other device in your house.
Reboot the Devices: Once you have changed the setting on the Eversolo, completely restart both your Nucleus and the Eversolo. This forces your router to recognize them freshly and assign them proper, unique IP addresses on the same subnet.
