Roon Ready Devices Disappear When Grouped in BluOS (ref#FONOXV)

Support
1

What best describes your playback issue?

· My DAC, streamer, or speaker doesn't appear as a Zone in Roon

What type of Zone is affected by this problem?

· *Network Zones* are affected.

Is the affected network Zone connected with Ethernet or WiFi?

· WiFi

Which network audio protocol is the Zone using with Roon?

· RoonReady

Does the device show up at all in Roon Settings -> Audio?

· The Zone is listed under the wrong protocol

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· Both the device and RoonServer are connecting to a *single router*

Try to disable any additional networking interfaces on your RoonServer machine.

· Disabling network interfaces had no change in behavior

Check to make sure RoonReady mode is selected on the device.

· I've checked this and the issue remains

If the device has multiple output options, do the other options work as expected?

· Only one output type is affected while the other output type works as expected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· Now

What are the make and model of the affected audio device(s) and the connection type?

· See post

Describe the issue

I’m trying to group BluOS products into a home cinema system. All the products are individually recognised as Roon Ready but as soon as I set up a fixed group in BluOS they disappear from Roon Ready. I’ve also tested the surround rear speakers setting them up as a stereo pair and the same thing happens - I can stream to them individually but as soon as I pair them they disappear from Roon Ready. I’m using a NAD M10 v3 and two Bluesound Pulse Flex 2i as surrounds. All firmware up to date. What’s the fix please?

Describe your network setup

Eero router all connected on same subnet via wifi

2

I don’t believe Roon can communicate with speakers grouped in BluOS. They would need to be grouped in Roon. That is likely the reason Roon doesn’t see them as Roon Ready once the grouping has been done elsewhere.

3

This isn’t true.

I group 2 pulse mini 2i speakers and a sub into a single endpoint in bluOS and it shows as a single device in roon.

I did see someone post about issues with the lastest firmware though, so I have avoided updating.

1 Like
4

OK, good to know, I wasn’t aware of that.

1 Like
5

Of course as a good new user to BluOS (not Roon), I blindly clicked all the “let’s update your firmware…” options as I was installing everything! Still, it’s good to know that it should work - it hopefully means it can be located and fixed at some point - unless I’m missing something?

6

Lets be honest you should be able to update firmware care free. I dont blame you, its best practice to be running the lastest firmware on setup.

I would raise a ticket with Bluesound somehow

7

I have done, so hopefully they’ll be in touch. I’ll try to remember to report back what they say.

8

I would love to know what they say. Would be useful.

9

Hi @Carbon_Underground ,

Can you please reproduce the issue and let us know the exact local time + date when you try to group them again and they disappear from the Roon app? After, we’ll try to enable logging to see if we can find further clues, thanks!

10

I just deleted the home cinema grouping and added it again and this time Roon seems to still see the M10, so I’ll come back if I see further issues. Thanks for the prompt assistance

11

Happy to hear that things are working better @Carbon_Underground , let us know how they hold up after further testing!

12

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.