In my case, (see post here) playback was simply halting on ALL devices, no error message given. The suggestion from the response team was basically check your cables. Horribly frustrating.
After doing my own deep dive into Nucleus One logging - I’m a retired software dev - I came to understand that RAAT is very finicky about all devices being in perfect sync, and will halt playback to ALL devices if any one device can’t keep up. ONE of my audio devices had poor WIFI connectivity, and the logs were very clear about it. ChatGPT helped me figure that out and isolate WHICH device was the problem. That device I had foolishly hemmed it in on all sides with metal and other devices. I moved it a few feet and my problem was effectively resolved.
The Roon server could very easily communicate to client apps something like “Playback was halted on all devices because MY_DEVICE_NAME (IP: 192.168.x.y) has poor connectivity. If the problem persists verify connectively for this device.”
The fact that RAAT will halt all playback if only one device has high latency is critically vital information! And the fact that the server knows which device is causing the issue needs to be communicated!! Imagine all the support loops and frustrations this would save.
The best server logging you can write conveys WHY something happened. WHAT happened is obvious. There was a streaming problem. If you can provide the WHY, that is actionable.
