Intel i5-7600 CPU 3.5 Ghz
16 GB RAM
64Bit
Windows 10 Pro
v22H2 - up to date
Networking Gear & Setup Details
PC /Core on Ethernet
Fiber to the Home and using internet providers modem
Switch is Duxbury 24 port gigibit POE
There is a smaller newly replaced 8 port TPLink switch involved to feed some access points
I use Unlocator Smart DNS on PC with Roon Core
Connected Audio Devices
Roon moves from the Core on the PC to an ipad controller to an ethernet connected Matrix Element i2 Streamer in music room. It also supports an ethernet connected ifi Zen streamer in Living Room. Upstairs it feeds a pair of wifi’ed B&W Flexs.
Number of Tracks in Library
77K Tracks
Description of Issue
Having trouble with my ipad seeing the Roon Core. I see “Waiting for Roon Core…” and option to select a different core. This behaviour is hard to pin down. Via my ipad controller (Ipad Mini OS16 and now OS17), downstairs, I have not been able to access Roon Core in my Music room for a few days but have had no issue accessing and playing in my Living Room.
Upstairs, i typically have no connection issue either, but now my ipad or iphone don’t see Roon core. This happened once before a number of weeks ago but righted itself almost immediately so i let it go. The Roon Core on the PC is not picking up the B&W Flexs connected by Wifi but the iphone B&W app does see them.
We have had some power outages which abruptly turn off the PC and network.
I am a bit confused and am hoping for some help to get this all back in line. The set up has typically been so robust!
PS - Separately, how does the PC look for running Roon core? It is several years old. Are specs still strong?
Does it work without this? VPN could be troublesome.
PC itself seems powerfull enough. Roon hasn’t changed its minimum spec in ages (or ever??) It might be an issue if the PC is heavily used for other software running at the same time.
Not completely clear to me how everything is connected. Did the trouble start when introducing the new TPLink? My own experience is everything to do with Roon connected to one switch works best.
Try to switch off everything and disconnect the non essentials. See if Roon works. And if not: first get Roon working again before connecting the other stuff.
(just my 2 ct)
The Smart DNS (not VPN) has been applied for years and had not interfered before.
PC does Roon only 95% of the time. Sometimes also browsing.
Hard to pin when trouble started. Might be related to TPLink but doubtful. That is a dumb switch and replaced an old one that wasn’t fully functional, e.g. it didn’t effectively pass ethernet to the Matrix streamer.
Wifi is working around the house - Roon core does not seem happy with ethernet / Wifi don’t appear to be happy.
Roon is working in living room and from the core. It seems not to work so well via Wifi…through the ipad controller.
Clear. I don’t use Roon through WiFi myself and don’t have any experience with doing so. Am I correct in assuming all in all it’s Roon with WiFi which is not working? I think you can find a lot of issues with WiFi and Roon on this forum and possibly solutions as well, e.g. Why is Roon so demanding of Wifi - Roon Software Discussion - Roon Labs Community
What model is the Duxbury switch, is it managed or unmanaged?
Have you verified IP addresses have not changed after power outages.
Have you rebooted everything cleanly after the power outages? Starting at the first device working out to the last device so that all devices get good IPs?
For WiFi have you done a site survey for signal strength and channel saturation to optimize throughput? Wifi analyzer or similar app can be used for this.
I will have a look at other discussions. I have not had any issue with wifi before - i have gone for months (years) without an issue so thinking there is a fundamental change. While i search, i hope for Roon technical support feedback too.
I don’t know enough to answer if it is managed or not managed. I like the idea of reviewing the IP addresses, but unsure how to do this. I have rebooted all cleanly… I have not done a wifi site survey.
I moved into the home about a year ago and replaced the switch about 10months ago and have had no issue with Roon before. Wifi is working well all over the house - except for Roon and my ipad/iphone. But still - there is clearly some kind of issue.
As far as I can tell the DUX2524P is an AI managed switch. Is there a reason you need a managed switch? If so, I would get the manual out and see how you get into it and check how it is set-up. Roon typically does not like managed switches unless they are “properly” managed… YMMV
For the IPs I would log into the router/AP and see what it tells you. You can use a command prompt on windows and “arp -a” to list all the IPs being used on the network. You could also use an app like “Fing” to scan the network for more details.
It seems to me you have some “intricacies” with your network that you need to sort out to make sure everything is configured properly and can talk to each other reliably. Power outages can confuse and corrupt these devices in strange ways (IME at least) and may need to be “re-configured” to work properly.
I like to use “dumb” switches as much as possible so that there is less chance of some ghost in the machine jacking up the addresses and settings.
For the WiFi I use “WiFiAnalyzer” and walk around the house (and yard) to check signal strength and channel saturation. Then adjust the channels and locations of Access points to get the best signal possible. This would also tell you if there are other WiFi networks and/or interference in the area that may be clogging up the airwaves. I used to live in an apartment that was really congested and needed to do a survey monthly to optimize. Luckily now I live in the country and no other outside signals, just my own devices to deal with. Still need a survey to check coverage through walls and appliances…
The managed switch or intricate network was not the issue. Signal strength was ok too. Indeed nothing with the switch or the access points changed.
The issue was with the modem that allow internet into the home. The short non-technical explanation was that is was scrambled and was not talking with a number of devices. How this happened is a mystery, but once replaced and reconfigured, all was back to normal.