· None of the above quite fits
· None of these quite match
· Since updating I'm getting roon error audio device refused to switch to roon. Seems to be random after a bit. Never had the issue before, haven't changed anything other than doing update.
· Tp-link
It may be helpful for support to know what kind of Roon Server and what kind of audio device you are using
I’m using an node2i connected via Ethernet. No hardware changes in years.
Exhibits by streaming stopping seemingly randomly but I think always when starting the next song in the queue.
I wanted to point you to a similar case with a Node2i but you already found it. Let’s see what support says 
Hello @david.l.holzman,
We reviewed your logs. On Oct 2 at 12:21 PM local time, Roon asked the NODE 2i to switch to the next track’s stream and the NODE 2i did not respond, so the zone could not start playback. The same kind of failure shows up on other days in your logs, and it matches a pattern we have seen on other NODE and NODE 2i units. This is with R&D.
Please also report this to Bluesound support, since the NODE 2i stops answering Roon’s request at a track change and the fix has to include the player. We are in contact with Bluesound on our side, and more reports from owners help.
If it happens again, please power-cycle the NODE 2i by unplugging it for a few seconds, which should get playback going again. We do not have a fix or a timeframe yet.
Just an FYI, power cycling the node2i did not work. I had to then follow with rebooting the roon rock server.
Reported to Bluesound but they told me it was a Roon issue..
Hi @david.l.holzman,
Thank you for following up with Bluesound, and for telling us the power-cycle didn’t help.
There are two separate problems here:
1. Playback stops: this starts on the NODE 2i. Your NODE 2i is wired, so this isn’t a network issue. At a track change, Roon sends the NODE 2i a request to set up the next track. In each failure in your logs, the NODE 2i stopped responding to Roon at that point. It didn’t reject the request; it went silent and stopped answering everything after it. Before each of those, it had answered the same kinds of requests in under a second. Roon can’t play to a device that has stopped replying, so the fix for this part does need to come from Bluesound.
2. Why a reboot of your ROCK is needed: this is on our side. After the NODE 2i goes silent, Roon should give up on that connection and reconnect, and it doesn’t. That’s why power-cycling the NODE 2i didn’t help: Roon was still waiting on the old connection. We’ve reported this to our development team.
If it happens again: restart Roon Server on your ROCK, either by rebooting the ROCK or through its web page. You don’t need to power-cycle the NODE 2i.
If you go back to Bluesound, please pass this on: “The NODE 2i stops responding to Roon’s RAAT setup request at track changes and stays connected without replying. Roon has logs showing this and is in contact with Bluesound.” That should help get it to the right team.
Thanks for your patience.
Thank you very much for looking into this. I am just wondering if you are at all in contact with Bluesound. They closed out my issue, telling me that it was a Roon issue. I will try to resubmit what you said but do not hold a lot of hope for that.
This is exactly the same Roon/Bluesound issue I’m having with my open support post.
Constantly restarting the Roon server and the bluesound components. I’m super frustrated and feeling like it’s time to take the Roon Ready status away from Bluesound.
Yeah bluesound support has been less than impressive.
It seems bluesound introduced a bug and it’s exhibited in Roon due to how they respond to the situation.
Hopefully bluesound is dealing with it behind the scenes. Not sure because frontline support washed their hands of it.
But yeah takeaway their Roon certification if they don’t take responsibility.
Hi @david.l.holzman and @Daniel_Rice,
Yes, we’re in contact with Bluesound. Our partner team has shared what we found in the logs directly with their team, and that conversation is ongoing. We’re sorry that their frontline support closed your ticket. That team often won’t know about partner escalations that are already open.
We’d still ask both of you to contact Bluesound support yourselves, even if it feels like you’re repeating yourself. Our partner team can tell Bluesound what the logs show, but Bluesound sees how many owners are affected by counting the tickets they receive. Every report from a NODE or NODE 2i owner adds to that count and helps them decide how urgent this is.
When you contact them, it helps to include:
On our side, the second problem is still with our development team. That’s the one where Roon keeps waiting on the stalled connection, which is why a restart is needed. Until there’s a fix, restarting Roon Server on your server (through the ROCK web page, or a reboot) is the quickest way to get playback going again. You don’t need to power-cycle the NODE. 