What kind of performance/speed issue are you experiencing?
· The app takes a long time to respond to commands
Please try to reboot your Roon Server
· Yes, rebooting helps, but the issue returns after some time
Please try to reboot your networking gear (Router/Switches/etc.)
· No, the issue is still the same even after a reboot
Is there any change in behavior if you try to navigate to Roon Settings -> Library and set both Background and On-Demand Audio Analysis to Throttled or Off?
· No, the issue is still the same
Does the issue happen on multiple Roon Remotes (controllers) or just one?
· Issue happens on multiple remotes
Router Domain Name System (DNS) change
· I don't know how to do this
What is the operating system of your Roon Server host machine?
· Roon Optimized Core Kit (ROCK)
Timestamp of issue occurrences
· For the past few months.
Describe the issue
Roon reacts very slow to commands, and especially slow on opening the play queue.
Describe your network setup
Telia, Technicolor - Telia WiFi-router Plus, TP-LINK Deco wi-fi extenders, NUC and Ropieee device connected via Ethernet.
I see this issue mostly on my iPhone 13 Pro and iPad Pro 11” (2018, A1980), and not so much on my MacBook Pro M1. On the iPad opening the queue can even stop playback and force some sort of reboot, where I see the ropieee channel gets lost to later appear a few minutes later.
Navigating, pausing/resuming and navigating to the queue is most of the time insanely slow. It didn’t use to be like this, and I have not changed anything in my setup to my knowledge.
Thank you for the detailed breakdown of your setup. The specific behavior you mentioned—where opening the queue on your iPad stops playback and causes the wired Ropieee endpoint to drop offline for a few minutes—is a massive clue.
We have reviewed your system diagnostics, and your Roon Server software on the NUC is actually running perfectly stable; it is not crashing or restarting itself. This means the bottleneck is happening at the network layer.
When your iPad attempts to load a heavy UI element like the Play Queue, it requests a large amount of data from the NUC. It appears that your local network is struggling to route this specific burst of traffic between the Wi-Fi and Ethernet segments, causing the network connection to your Ropieee to temporarily drop and playback to fail.
To pinpoint exactly where the breakdown is happening and stabilize your system, please try the following steps:
Reproduce and Share a Timestamp
Before making any major network changes, we want to look at the logs at the exact moment the network drops the connection.
Please reproduce the issue using your iPad (navigate and open the queue until playback stops and the Ropieee drops). Note the exact local date and time this happens and share it in your reply.
Verify TP-Link Deco Operating Mode
Mesh systems like the Deco are notorious for causing extreme latency and communication drops with Roon if they are running their own routing layer on top of your main ISP router.
Open your TP-Link Deco app, go to Advanced settings, and check the Operating Mode. Because your Telia router is handling your main network, the Decos must be set to Access Point (AP) mode. If they are in “Wireless Router” mode, please switch them to AP mode.
The Bypass Test
To confirm definitively if the Deco mesh is the bottleneck for your iOS devices:
Temporarily unplug the TP-Link Deco nodes from power. Connect your iPad directly to the Telia router’s primary Wi-Fi network. Open the Roon app and navigate to the Play Queue. Does the app respond snappily and continue playing music without dropping the Ropieee?
Have not disabled the Deco nodes, but switched to the router’s primary wi-fi network.
When switching to the primary network of the router, things definitely improve. Sometimes even good performance. But still it does slow down to a crawl even when on that network. No complete drop outs though, just slow performance of the endpoints.
Will this weekend try switching Deco off to see if there is any difference compared to just switching to primary network.
Let us know how the testing goes. Did you, by any chance, restore an iPad backup to an iPhone, or vice-versa? Also, does the issue occur only when you’re using them simultaneously? Your updates will help us pinpoint the cause of the problem. Thanks!