· Other
· I'm having trouble with my Nucleus hardware
· Other
new router and roon not detecting a network device
I have a new TP-link router and a TP-Link switch.
Hello @Michael_Wasserman ,
Thanks for reaching out. Can you please confirm the model/manufacturer of the device that is not showing up? What is the model/manufacturer of the new router? Was the router added onto your previous network? If so, it is possible that you have two subnets set up, and for the devices to work properly with Roon, they must be on the same subnet.
TY for helping. Meridian 218 Streamer is the device not showing. As I may have mentioned, the formerly 2 devices in my office that were connected to Roon are now both showing up as the Sonos wireless connection in the office whereas only one should be. The Meridian is not showing up at all in Roon Audio. I have no clue how to check the subnets so please address my ignorance. The router is the following: TP-Link - Deco BE65 Pro BE11000 Whole Home Tri-Band Wi-Fi 7 Mesh Router System with two 5-Gig Ports (3-pack) - White
Model: Deco BE65 Pro(3-pack)
Thank you for supplying that information. We’ve taken a close look at network diagnostic logs from the Nucleus+ at the time of a Meridian disconnection event.
The Nucleus+ is actually experiencing network-wide disruptions that temporarily interrupt connectivity to upstream servers, cloud services, and other devices on the local network. Connectivity recovers after a period of about one minute, allowing most of the upstream requests to retry. However, device discovery has already timed out, requiring you to force a device discovery cycle by either restarting RoonServer or hitting the “refresh” button in Settings → Audio.
What does this mean, and how can you prevent it? In the context of your TP-Link mesh network, the most likely culprits are the settings for client isolation and band steering. The mesh network is trying to optimize traffic between the nodes by shifting through the various network bandwidths that can carry WiFi and by re-routing traffic between mesh nodes on the fly. These settings can interfere with Roon, which relies on a diverse and delicate combination of ports and network protocols.
In the Deco app or router settings page, navigate to More → Advanced and look for options like “Client Isolation”, “AP Isolation”, or “Device Communication”. Make sure AP isolation is turned off, and/or “allow devices to see one another” is turned on.
In the WiFi Settings page, look for an option called “Fast Roaming” and disable it. This might restrict the Deco mesh network to a single band.
What is the switch you’re using, and where it configured in your network topology relative to 1) the Nucleus+, 2) the router, and 3) the Meridian?
Certain managed network switches implement settings by default that can prevent device discovery of Roon Ready Zones.
We’ll watch for your response! Thanks!
Thank you for this. I will try and review and/or implement over the weekend.
M
Great! We’ll keep an eye out for your update on how that goes. Please let us know if you need any help with that.
We wanted to check in since some time has passed. If you need additional time to make the aforementioned changes to your network setup, please let us know so we can prevent this thread from auto-closing due to inactivity.
If you’ve reviewed and implemented some of the network recommendations at this point, we’d love to hear if you’ve noticed an improvement in device discovery. We’re eager to ensure your setup is stable moving forward.
Thanks!
Hi. I have not yet had time to address this but I hope to soon. I appreciate the help but am slammed with too many projects combined with very poor sleep in recent days. I have also noticed that the Roon home office connections are now mislabled with the Meridian still not working at all. The one that was just called Office now works with the wireless SONOS device and the wired non-functioning Meridian is now labled Office Sonos. TY again.
Hi @Michael_Wasserman ,
Thanks for letting us know. When you have a chance for us to pick this back up, do keep us posted. As for the naming aspect, I see that your Meridian is listed as Office Krell in our diagnostics, and the Sonos listed as Office Sonos is named just Office according to Sonos. Are you perhaps setting up the name in the Sonos app? In any case, do let us know when you’re ready to pick this back up, thanks!
Hi. Restarting RoonServer did nothing. I am confused by your answer regarding TP-Link and Deco. The Meridian device is wired so I do not understand why WiFi is being discussed. The working audio in the home office is to a Sonos device using WiFi and working just fine. The switch is TP-Link TL-SG108 8 Port Gigabit Unmanaged Ethernet Network Switch, Ethernet Splitter Plug & Play Fanless Metal Design Shielded Ports Traffic Optimization. The Nucleus+ is connected via an ethernet cable to the switch. The Meridian is connected via an ethernet cable also to the switch. For reasons I cannot begin to understand, the non-working Office device showing under Audio via Roon shows it connected via AirPlay2 and then showing the same IP address as the working WiFi Sonos device. I am clueless. Again, thanks for the help!
Hello @Michael_Wasserman
Thank you for the update.
TP-Link Deco is not only responsible for the WiFi it also manages the network traffic that comes through the devices, and in case if your network devices are connected to different Deco nodes or the network is coming through them, it may cause issues.
AirPlay devices do not rely on standard network discovery protocols like SSDP or mDNS used by some other platforms. Instead, they use Apple’s proprietary Bonjour protocol, which is based on mDNS (Multicast DNS) for service discovery. * Bonjour/mDNS (Multicast DNS) is designed to work even when there’s no central DHCP server or router.
After changing the router, your LAN subnet addresses may be changed, and probably your device still has the static IP address set up on the device itself, which may lead to discovery issues. Have you set up a static IP address in the Meridiann app ?