Hello @APV
Thank you for your patience. We have reviewed the logs in detail and found the exact cause of the lockup.
What happened at 4:15 PM
At 4:08 PM you paused the track “Again” by Snow Strippers at the 0:08 mark. Roon sent a stop command to your Bluesound Node 2i and received a clean confirmation:
06/06 23:08:58 Trace: [Bluesound NODE 2i @ 192.168.1.102] SENT {"request":"stop"}
06/06 23:08:58 Trace: [Bluesound NODE 2i @ 192.168.1.102] GOT {"status":"Stopped"}
Five seconds later, Roon suspended the zone to release the audio device (this is normal behavior) and sent a teardown command to the Node:
06/06 23:09:03 Trace: [zone Yamaha Living Room 2i] no playback for 5s, suspending to release audio device
06/06 23:09:03 Trace: [Bluesound NODE 2i @ 192.168.1.102] SENT {"request":"end_stream"}
06/06 23:09:03 Trace: [Bluesound NODE 2i @ 192.168.1.102] SENT {"request":"teardown"}
06/06 23:09:03 Trace: [Bluesound NODE 2i @ 192.168.1.102] GOT {"status":"Success"}
The end_stream was acknowledged. The teardown was not - no reply came back from the device.
When you pressed Play again
Between 4:09 PM and 4:09:47 PM you pressed Play four times. Each time, Roon sent a request_source command to the Node asking it to resume. The Node did not respond to any of them:
06/06 23:09:22 Trace: [Bluesound NODE 2i @ 192.168.1.102] SENT {"request":"request_source"...}
06/06 23:09:32 Trace: [Bluesound NODE 2i @ 192.168.1.102] SENT {"request":"request_source"...}
06/06 23:09:34 Trace: [Bluesound NODE 2i @ 192.168.1.102] SENT {"request":"request_source"...}
06/06 23:09:41 Trace: [Bluesound NODE 2i @ 192.168.1.102] SENT {"request":"request_source"...}
06/06 23:09:47 Trace: [Bluesound NODE 2i @ 192.168.1.102] SENT {"request":"request_source"...}
No GOT reply appears after any of these lines. The TCP connection to the Node was still open - the device was reachable on the network - but it had stopped reading and responding to RAAT commands entirely. This caused the full lockup you experienced.
What is causing this
After receiving the teardown command, your Bluesound Node 2i enters a state where it stops processing incoming RAAT messages on the existing connection. Roon keeps the connection open and continues sending commands, but the device is no longer listening. The only way out is a reboot.
This is a behavior issue on the Bluesound side - the device should either acknowledge the teardown and remain ready, or cleanly close the connection so Roon can reconnect. It is doing neither.
What to do
We recommend reporting this directly to Bluesound support with the following description:
After a teardown is sent over the RoonReady RAAT connection, the device stops responding to subsequent request_source commands on the same TCP session. The connection remains open but the device processes no further messages until rebooted. This results in a full playback lockup in Roon.
Reference your BluOS version (4.16.6) and device model (NODE 2i / POWERNODE 2i). Bluesound’s team will be able to reproduce this from that description.
From our side, we will also ask our partner’s team to reach out to Bluesound as well.
