· I use various audio equipment NAD C658, Bluesound and others. Very often there is a conflict with Bluos and Roon. I then have to stop all devices, decouple Bluos and start agailn, It primarily occurs if one of my housemates use Bluos to link 2 zones. If I looked in the Roon Apps Community but did not find the subject. I also contacted Bluesound but did not got an solution there either. I often receive the error message: Audio device refused to switch input to Roon.
Thank you for your post and for the report. Can you provide, at your convenience, the name of a track that was playing when this last occurred, or an approximate timestamp?
We should be able to pinpoint the event in logs and deduce a cause that will provide a next step here. Thank you!
It does not happen with a specific track or time stamp. It is related to zoning within Bluos I think, or perhaps with the combination Roon - mac’s OSX. When I use Bluos there is no problem.
We will enable diagnostics mode for your account, and when the issue next occurs, please send us the exact local date and time along with the track that was playing. That will let us line up the event with the logs. When you are ready, just post back with those details.
It happened again: 4 October, between 14:00 and 14:30 NL time. The track was Saint Rose by Julian Lage. I restarted Nad and Roon and then it played again.
We went through the Roon Server logs for October 4. Between 14:00 and 14:30 the NAD C658 (the KAMER zone) was playing normally. Saint Rose by Julian Lage started at 14:22 and we do not see a failed input switch anywhere on that day.
What we do see in that window: at 14:27:48 the NAD itself sent a pause command to Roon, right as the track reached its end. Roon released the device a few seconds later, and playback resumed without any error at 14:27:58 when it was started again. We also see the Roon Remote on an iPhone disconnect and reconnect between 14:26 and 14:27. We do not see the NAD or Roon Server restart in the logs.
The error you describe does show up earlier, on September 29 (from 10:49 to 11:21 and from 13:20 to 13:53) and on September 30 (from 11:07 to 11:18), when Roon could not reach the NAD for a while. We do see BluOS groups in the logs (for example KAMER+KEUKEN on October 2, 4 and 5), but those failures do not line up with any of them, so we need a bit more detail to connect the two:
Please tell us what you saw on screen around 14:27 on October 4: the “Audio device refused to switch input to Roon” message, or only that the music stopped?
Please tell us whether you pressed pause on the NAD or in the BluOS app around that time, and which Roon app you restarted (the Mac, the iPhone, or both).
When your housemate links two zones, please tell us whether that is done in the BluOS app or in Roon, and which device is the group leader. Grouping in Roon works differently, and it is covered here: How do I link zones so they play the same thing simultaneously?
The next time the error appears, please post the exact time here before restarting anything.
Two more guides apply to your setup. Networking Best Practices covers the Fritz OS 7 note and the “simplify then rebuild” method we may ask you to use.
As far as I recall I did not see anything on the screen. The music just stopped
I did not press any button, I was reading and listen to music. I tried to restart Roon, probably on the iPhone and on the Mac.
The housemates only links 2 zones (mostly Kamer + Keuken) via Bluos. The reason for that is that my wife finds Bluos more easily than the Roon interface. I only link zones via Roon.
I will.
In the coming days I will apply the “simplify then rebuild method”