Hi @JAM,
Thanks for the reply! We have not yet released any updates, so it’s expected you’ll likely still experience your issues until then.
You aren’t required to continue to share issue timestamps until you’ve fully updated your whole Roon system with our upcoming release.
Thank you!
Hey, @JAM.
We are still working on the current Roon release and the changes that are lined up there. We have not forgotten that you are still waiting on this, and thank you for your patience.
Once the release is out, please let us know whether it helped in your case as well. We will be glad to hear if there’s been progress in resolving the issue.
Thanks for checking in, @noris. I’ll be looking forward to the new release whenever it comes out and will report back on how it’s working for me.
Hey, @JAM.
The new release is out, please test it on your side and let us know whether you see any improvement. We are looking forward to hearing whether it makes a difference in your case.
Thanks for checking in, @noris. So far it seems to be working great. I’ll continue to monitor over the next few days and report back if I run into issues. Thanks Roon support folks for your hard work on this and conscientiousness in following up with me to make sure things are improving.
Hey, @JAM.
Glad to hear that helped. We’ll be standing by while you continue to monitor things, and please let us know if anything changes over the next few days. We’ll keep an eye out for your follow-up.
Hi @JAM, we hope the silence means the music is playing without interruption! We’ll close this thread for now, but if the issue comes back, you’re welcome to reopen it anytime through our Technical Support Request form. Just select “None of the above quite fits”, then “Reopen a previous technical support request.” Thank you!
Hi @JAM,
We’ve enabled some diagnostics for your account that should help us pinpoint the underlying mechanism for some of the dropouts and performance problems you reported previously in this thread.
At your convenience, please simply reboot RoonServer two times and use Roon as you normally would. We’ll gather diagnostics remotely. If you encounter any performance problems or dropouts, let us know, but we’ll find them in the logs regardless.
Thank you again.
Thank you, connor. Just to be sure I did this right, I clicked “restart” on “Roon Server Software” and did it again when it was available. Is that correct? Thank you for your commitment to getting my system working well again.
Hi @JAM,
Those restart steps were correct, thank you for checking. We are seeing Roon logs flooded with these API ping messages:
08/19 11:03:11 [Local 08/19 04:03:11] Trace: [roonapi] [apiclient 192.168.4.22:49153] GOT com.roonlabs.ping:1/ping
08/19 11:03:11 [Local 08/19 04:03:11] Trace: [roonapi] [apiclient 192.168.4.22:49153] COMPLETE Success
Can you please disable this Roon API zone and see if that helps with the issues?
Thank you, @noris. That device is a Tuneshine, so I asked @TobiasFromTuneshine for his thoughts before I disconnect it. He wrote:
"This is expected behavior, and based on my understanding of how Roon works it shouldn’t cause any problems, though I’d be curious what the Roon folks think.
For any extension connected to Roon, the Roon server will send a ping over that extension’s connection every 2 seconds, and if the extension fails to respond within 2 seconds Roon will forcibly disconnect the extension.
When I was stress testing the Tuneshine integration on a degraded network connection, I found that I could keep the connection open more reliably by sending my own pings every 1 second, escalating to every 0.5 seconds if the Tuneshine is getting disconnected frequently, as the Roon server would be more likely to get a ping in every 2 second window. This made it less likely that the Tuneshine would get disconnected due to intermittent network blips, which can be more common with a device like Tuneshine that has a small antenna on a 2.4GHz network.
It’s possible that they are just hoping to make the server logs more readable by removing this noise, but it’s probably worth unplugging the Tuneshine for a bit anyway to confirm or disprove the possibility that it’s contributing to the other Roon issues you’re seeing."
@noris do you still want me to unplug the Tuneshine? Also, I have two of them, so should I disconnect both?
Hey @JAM,
Thanks for the follow-up. Yes, please disable both, reboot Roon Server, and monitor performance. We’ll enable diagnostic mode as well, to analyze things on the back end.
If you’re able to share a fresh timestamp of the issue after performing the above as well, that would be helpful as well. 
Thank you, @benjamin. I disabled the Tuneshine devices, restarted Roon server (twice), and it’s 12:58 PT. I’ll be traveling for much of the week starting tomorrow but will use Roon for today to see how things go.