Roon Ready Certification

Agreed, whilst the majority of Roon Tested devices are USB DACs, it’s wider than that … I forgot about those non-USB device that have also been Roon Tested.

I do appreciate how it easy it is for “Roon Tested” and “Roon Ready” to be conflated.

You didn’t make a copy?

And without knowing the particulars you implicitly put the blame on Roon… not reasonable.


Not sure how that’s relevant ss far as ‘Roon Ready’ certification is involved, but I guess you’re saying you don’t like Roon support. Fair enough.

Point taken. Guess you won’t be renewing your subscription.

Stiil, in your particular case, if the M3 isn’t advertised as being ‘Roon Ready’, then you’re not effected by this at all.

I purchased a life time license!

I nearly lost it today when I read the first announcement. Especially this part:

How will this impact me?

  • If your device is Enabled in Roon’s settings, it will stay Enabled. But if you Disable the device, you will not be able to Enable it again after September 21st.
  • If you purchase a device that is not certified as Roon Ready, you will not be able to Enable it for use after September 21st.

I have eight zones, and none of the devices I have purchased are “certified as Roon Ready.” (mostly Raspberry Pi builds running Roon Bridge) If the policy was as it is stated above and I disabled any of them for any reason after September 21st, they would be gone forever. Horrifying.

Adding the following clarifying paragraph near the top of the announcement and communication would be tremendously helpful:

Roon Bridge is not affected. Community-developed stuff is not affected. This is only about manufacturers who licensed the Roon Ready SDK from us commercially, then violated our license by skipping the Roon Ready certification process. It’s not very many manufacturers. We began communicating with manufacturers about this in 2018 . They have had ample warning to sort things out.

Cc: @dylan


OK, you’re upset, but isn’t this true -

My hardware has a perfectly good implementation of roon (for my needs) without the certificate …
Can’t find a reason why the manufacturer has to invest time and money to get only the approvment from Roon and bother with more features then needed. At the end the product will be more expensive without the customer getting added value. Only Roon are satisfied and play the powerful one … Stupid approach - who is greater - software or hardware.
It is far wiser to go for as much as possible compatible devices, and just dont give full functionality if not certified.
On the other hand hardware manufactures also don’t want to be told how they have to write their software … understandably. If a manufactures dont want to implement particular feature from the roon SDK this should be his Decision. After all that are his customers in the first place, not roons.

Good point. If my hardware is not certified i will never ask for help regarding integration roon. I ask the hardware vendor. Dont see the problem here.

1 Like

You are missing the point.

Only those manufacturers who say ‘Roon Ready’, ostensibly to sell their device, need to actually get Roon certification.

If the manufacturers doesn’t advertise ‘Roon Ready’, they don’t need certification and more than likely the device will still run with Roon.

It IS advertised as being Roon Ready. In Roon the M3 is listed as “Roon Ready - Uncertified”. I am impacted!

Is didn’t know if was uncertified when I bought it and didn’t worry when I saw it was uncertified in Roon. I assumed that it would be certified at some point. I wouldn’t have anything to do with it being uncertified nor didn’t know what that might mean over time I was never informed by Roon until today that Uncertified means it would be unusable if I made any changes after September 21st.

Hopefully Roon will do the right thing and just give me a refund and I will walk away.

I will go to small claims court if I have to and Roon can send a representative to Florida to defend themselves.

1 Like

I think he is. The M3 is a DAC with multiple digital input choices and an optional (!) Ethernet input. @Stephen_Seay claims that it had been advertised on Bricasti’s website as Roon Ready. I have checked and by now this claim in not any more to be found on Bricasti’s web.

Of course, if the M3 is being used as DAC and connected to a bridge via USB or any other digital interface it should work perfectly. But not any more as Roon Ready streaming device connected to the LAN.

Anyway, if Bricasti made a false claim about the Roon Ready certification it seems to me that all blame should be put on them. I believe that Roon has never claimed that particular device to be Roon Ready.


The reason is simply that the manufacturer entered into a binding contract with Roon but then decided not no honor their obligations under said contract. The manufacturer could have instead done what many others do, use RoonBridge in an open-source platform so that their device can work with Roon, but without full Roon Ready certification. Does not speak well of the manufacturer, does it?

If I sell an electrical device and mark it as “UL listed” but I did not go through UL certification, I’ll be sued. How’s this any different?


Slim, you highlight “Unless you do”, but the user might not actually disable the device him/herself.

I know from personal experience, and from reading posts today by other users (on here, and on Headfi), that we have not knowingly “disabled” the device, but a situation arises which means that the device needs “enabled”. In my case I cannot remember what caused it, although I think it might have happened when I was making changes to my network. Another user thinks it might have been after a FW upgrade to his Chord 2Go.
So bottom line, circumstances outwith a users control may cause the device to be “disabled”.


I don’t think this is quite correct. Roon Ready means they have implemented RAAT SDK, which gives deeper integration for a better overall user experience (like volume control, sleep/wake, etc). It’s not about the advertising. The alternative is they use Roon Bridge instead of the RAAT SDK. They lose the deeper integration, but then no longer have to go through certification.

1 Like

I stand corrected on the principle. :slightly_smiling_face:
I was replying to the OP who believed, at least temporarily, that he was being advised to disable his device.

No, if they don’t advertise ‘Roon Ready’ then they are not subject to being disabled and that’s the fear in this thread.

As to whether the device works or not that would be discovered on the first day the device is plugged into Roon.

1 Like

I think that you would have to sue Bricasti rather than Roon, as Bricasti is the one making the false claims.


I like Bricasti. The owner responds same day to questions. I have never received the least bit of support from Roon. Only to say we can’t talk about certifications and the problem is not ours.

That maybe, but living or not liking someone is not the basis for a lawsuit (otherwise I’d be in court most of the time, plaintiff and defendant)


“Roon Ready” specifically means use of the RAAT SDK. It’s not about advertising. If they use the SDK, regardless of “advertising it”, it still shows up in the “Roon Ready” section of Audio Settings. And without certification, will not be enableable after Sep 21.

Instead, they would need to use Roon Bridge, and then they can just say “Roon compatible” or whatever other marketing jargon they want.

OK, let me re-phrase - If a vendor is using ‘Roon Ready’ as a selling point, by incorporating the RAAT SDK in their firmware, then they are liable to this new Roon way of doing things.

If a vendor uses ‘Roon Ready’ in their advertising, then it’s probably in the firmware and if it’s in their firmware then they are probably going to advertise it.

Distinction without a difference, but who’s counting? :smirk: