I’ve terminal pinging away at the Core. And, when the Core drops a ping (so far, only ever just a single ping) this precedes the Controller (OSX) losing contact.
If I leave Controller OSX and Controller iOS running and open, they behave differently on “drop events”: Controller OSX reports “Roon is still trying to connect, but it’s taking longer than normal. Check that your Roon Core is on and connected.” This message is replaced in <30 seconds by Roon as usual. Meanwhile, the iOS client reports that the streamer is no longer reachable, but it appears that the Core is 100% fine throughout the event.
As I write this, I realize that the single point of failure is the network switch. But, it is a robust unit, <1 year old, and manifesting no other observed problems.
The only change I’ve made to the network in recent days was to the DHCP server.
The only pieces of networking gear in the path between the Core and Streamer: Ubiquiti UniFi Switch 8 60W and 2x runs of cable. Between the Controller and the Core, there’s Ubiquiti AP and a different run of cable to the switch.
I can imagine how a managed switch might cause trouble in the path between the Core and Bridge. But in this case, I’m nearly certain that there’s trouble (maybe “also trouble”) between Controller and Core. And, I can’t for the life of me understand how a managed switch might be problematic in that path (especially one that’s worked without trouble for 9 months).
Thanks for confirming that the Web UI is also not available during this time. Since this is the case, it’s not necessarily a remote > Roon connection issue — The device isn’t being seen over the network for Web UI access either.
We make a note of some issues that can arise when using a managed switch in our Networking Guide, and have some settings that we recommend here as well. While I understand that things were working previously, we have seen issues like this come up relating to these types of switches, so bypassing that switch as a test would definitely be a great data point for understanding where this behavior is stemming from.