· Something’s not working in the Roon interface (buttons, displays, lyrics, etc.)
Describe the issue
I use Roon to listen to music on two Bluesound Pulse Flex 2i's in a stero pair. Ever since I updated the Bluesound firmware 2 versions ago, I when click the Mute All button on the Roon interface, only one of the speakers will mute. The volume up and down works as normal, and adjusts the volume of both speakers, however it's just the Mute All button that is no longer working as designed. I confirmed that the mute button on BluOS software will mute both spreakers as designed. I have tested removing the stereo pair, and connecting to both speakers independently and using Mute All, which works on both speakers when they are not in a pair. As soon as I reconfigure the pair, the Mute All will just mute one speaker.
Thank you for the clear explanation — we want to confirm one detail so we can proceed correctly.
From your description, it sounds like:
When the two Pulse Flex 2i speakers are grouped inside Roon, Mute All works correctly on both.
When they are configured as a stereo pair in the BluOS app, Mute All only mutes one speaker in Roon.
Volume controls still affect both speakers normally in both cases.
Could you please confirm that this understanding is correct?
If so, please do the following: 1. Create a stereo pair again in the BluOS app. 2. Reproduce the Mute All issue once more in Roon. 3. Send us the exact timestamp (date + time) when the issue occurs.
This will allow us to pull the correct diagnostic slice and check what Roon receives back from the BluOS RAAT implementation during the mute command.
Thank you — we’ll continue from there once we have the timestamp.
All points are correct apart from the first one ’ * When the two Pulse Flex 2i speakers are grouped inside Roon, Mute All works correctly on both’ - I did not group the speakers in Roon, I just tested the Mute All function on both speakers independendly.
I reproduced the issue Monday 1st December 11:15 PM UTC.
Based on the diagnostic data, both nodes responded with a success code. I would recommend reaching out to Bluesound to understand where the culprit is.
Just checking in to see if you had a chance to review our last message.
Whenever you’re ready, feel free to share an update — we’re here and happy to continue troubleshooting.
Thanks for reviewing and providing the logs. I have submitted a case with BlueSound and just awaiting their reply. I’ll provide another update once I get some feedback from them. Cheers, Glenn
Thanks for the update. Let us know once you hear back from them, or if it takes a bit longer and then thread auto-closes in the meantime, feel free to open a new thread and reference this one (ref#WFABUJ). Thanks!