# Certifying Chord 2go

**URL:** <https://community.roonlabs.com/t/certifying-chord-2go/117708>\
**Category:** Chord\
**Created:** [August 18, 2020, 12:48am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708 "2020-08-18T00:48:24Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![xred](https://community.roonlabs.com/letter_avatar/xred/32/5_5575768a8748004e209b776fc1b2916d.png) [@xred](https://community.roonlabs.com/u/xred)\
**Post date:** [August 18, 2020, 12:48am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/1 "2020-08-18T00:48:25Z")

</div>

Hi, folks. Any plans certifying Chord 2go?

 ![snapshot 2020-08-17 at 5.46.23 PM](https://roon-community-uploads.s3.amazonaws.com/original/3X/6/0/60726e00cef69ed5dde2cf6b4c1504d6e049fef5.jpeg)

---

<div class="post-metadata">

**Author:** ![Fernando\_Pereira](https://community.roonlabs.com/user_avatar/community.roonlabs.com/fernando_pereira/32/55606_2.png) [@Fernando\_Pereira](https://community.roonlabs.com/u/Fernando_Pereira)\
**Post date:** [August 18, 2020, 3:08am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/2 "2020-08-18T03:08:04Z")

</div>

I don’t know Roon’s or Chord’s plans, but the 2go works fine with my Roon setup, except for very occasional drops that are I think a consequence of Chord’s decision to only provide 2.4GHz WiFi, which suffers from a lot of contention in my neighborhood, rather than dual 2.4-5GHz.

---

<div class="post-metadata">

**Author:** ![xred](https://community.roonlabs.com/letter_avatar/xred/32/5_5575768a8748004e209b776fc1b2916d.png) [@xred](https://community.roonlabs.com/u/xred)\
**Post date:** [August 18, 2020, 3:47am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/3 "2020-08-18T03:47:14Z")

</div>

Thanks, @Fernando_Pereira. No quarrel about compatibility, 2go (with Hugo2) does work fine, but in the Roon app it’s marked as Uncertified, as the pic is showing. Hence, the question.

---

<div class="post-metadata">

**Author:** ![sanj\_oh](https://community.roonlabs.com/letter_avatar/sanj_oh/32/5_5575768a8748004e209b776fc1b2916d.png) [@sanj\_oh](https://community.roonlabs.com/u/sanj_oh)\
**Post date:** [August 28, 2020, 4:46pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/4 "2020-08-28T16:46:49Z")

</div>

I would also be interested in knowing when the 2go receives full certification. ATM many people are experiencing difficulties with random pops and clicks and a lack of full hires steaming. ( frequent drop outs at 192 and dsd 256 rates). Full certification would mean that these issues would be addressed, I hope!

---

<div class="post-metadata">

**Author:** ![xred](https://community.roonlabs.com/letter_avatar/xred/32/5_5575768a8748004e209b776fc1b2916d.png) [@xred](https://community.roonlabs.com/u/xred)\
**Post date:** [August 28, 2020, 5:10pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/5 "2020-08-28T17:10:59Z")

</div>

For what it’s worth, I too have seen 2go dropping at higher bit rates. Placed 2 feet away form the gigabit access point.

---

<div class="post-metadata">

**Author:** ![sanj\_oh](https://community.roonlabs.com/letter_avatar/sanj_oh/32/5_5575768a8748004e209b776fc1b2916d.png) [@sanj\_oh](https://community.roonlabs.com/u/sanj_oh)\
**Post date:** [August 30, 2020, 4:02am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/6 "2020-08-30T04:02:34Z")

</div>

Can someone at roon please comment on the status with the 2go? It would be helpful to know if there are improvements in the pipeline with respect to streaming with the 2go. Chord are essentially absent in 2go forums but roon does have a responsibility towards its customers who buy ‘roon ready’ products.

---

<div class="post-metadata">

**Author:** ![Fernando\_Pereira](https://community.roonlabs.com/user_avatar/community.roonlabs.com/fernando_pereira/32/55606_2.png) [@Fernando\_Pereira](https://community.roonlabs.com/u/Fernando_Pereira)\
**Post date:** [August 31, 2020, 3:49am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/7 "2020-08-31T03:49:23Z")

</div>

> [@sanj\_oh](#):
>
> It would be helpful to know if there are improvements in the pipeline with respect to streaming with the 2go.

Works fine for me almost the time, all PCM, any rate/bit depth, local or Qobuz. I do get neighborhood congestion on 2.4GHz WiFi occasionally, which is the reason I say “almost.”

Chord does advertise the 2go as “Roon Ready,” on their site, so it would make sense for Roon to make sure Roon’s and Chord’s expectations vs each other are correctly portrayed to customers. But Roon would never comment publicly on the state of their relationship with a partner.

---

<div class="post-metadata">

**Author:** ![Fernando\_Pereira](https://community.roonlabs.com/user_avatar/community.roonlabs.com/fernando_pereira/32/55606_2.png) [@Fernando\_Pereira](https://community.roonlabs.com/u/Fernando_Pereira)\
**Post date:** [September 4, 2020, 1:38am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/8 "2020-09-04T01:38:11Z")

</div>

I’ve had occasional dropouts as I carry my Hugo 2+2go around the house, as just now as I was walking from my study to the garden. All the evidence I have is that our WiFi is very solid (AmpliFi mesh, base access point + 3 mesh points) but the 2go seems to have a very touchy WiFi transceiver or network stack. It seems to go totally nuts if it is placed next to any larger piece of metal, in this case a bracket under the kitchen counter. That combines with Roon RAAT’s intolerance of any network glitches, and drop outs+skipped tracks follow. I don’t know who needs to fix what, but clearly this is not close to “Roon Ready.”

---

<div class="post-metadata">

**Author:** ![Justas](https://community.roonlabs.com/letter_avatar/justas/32/5_5575768a8748004e209b776fc1b2916d.png) [@Justas](https://community.roonlabs.com/u/Justas)\
**Post date:** [September 9, 2020, 3:22pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/9 "2020-09-09T15:22:03Z")

</div>

And here is what are we waiting for… ☹

> [@Important Changes to How Roon Interacts with Uncertified Roon Ready Network Players](https://community.roonlabs.com/t/important-changes-to-how-roon-interacts-with-uncertified-roon-ready-devices/120204):
>
> When we first started our [Roon Ready network player certification program](https://roonlabs.com/roon-partner-programs), our goal was to provide a way for our customers to know that they were getting the best possible experience with their audio devices. People have come to trust Roon Ready devices to not only sound great, but work seamlessly in their homes with Roon. Every Roon Ready device goes through a rigorous certification process, and when manufacturers release their Roon Ready implementation before it’s ready, this impacts Roon us…

---

<div class="post-metadata">

**Author:** ![xred](https://community.roonlabs.com/letter_avatar/xred/32/5_5575768a8748004e209b776fc1b2916d.png) [@xred](https://community.roonlabs.com/u/xred)\
**Post date:** [September 9, 2020, 6:57pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/10 "2020-09-09T18:57:36Z")

</div>

I have reached out to Chord Electronics this morning with the question about 2go certification. Below is their reply.

Can Roon Support comment on this?

_Dear Sir,_

_The 2Go has been with Roon Labs awaiting sign off since before it went on sale and we have worked with Roon to swiftly answer any follow up queries that have been asked. Naturally, we hope that Roon is also working to ensure that this deadline is met for items that are awaiting certification to ensure a seamless transition to these new rules._

_All the best_

_ **Ed Selley** / Customer Support_  
_[support@chordelectronics.co.uk](mailto:support@chordelectronics.co.uk) / (+44) 01622 721 444_

\ ***Chord Electronics Ltd.** \*  
_The Pumphouse, Farleigh Bridge_  
_Farleigh Lane, East Farleigh, Kent, ME16 9NB, United Kingdom_

_[https://www.chordelectronics.co.uk](https://www.chordelectronics.co.uk/)_

---

<div class="post-metadata">

**Author:** ![Fernando\_Pereira](https://community.roonlabs.com/user_avatar/community.roonlabs.com/fernando_pereira/32/55606_2.png) [@Fernando\_Pereira](https://community.roonlabs.com/u/Fernando_Pereira)\
**Post date:** [September 9, 2020, 7:55pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/11 "2020-09-09T19:55:56Z")

</div>

> [@xred](#):
>
> _Naturally, we hope that Roon is also working to ensure that this deadline is met for items that are awaiting certification to ensure a seamless transition to these new rules._

How disingenuous (I’m trying to be polite). I own a 2go, which is the least reliable Roon endpoint I’ve ever owned, including several that never claimed to be Roon Ready. If I were in the business of certifying it, I’d give it a FAIL.

---

<div class="post-metadata">

**Author:** ![xred](https://community.roonlabs.com/letter_avatar/xred/32/5_5575768a8748004e209b776fc1b2916d.png) [@xred](https://community.roonlabs.com/u/xred)\
**Post date:** [September 9, 2020, 10:23pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/12 "2020-09-09T22:23:02Z")

</div>

Followup response from Chord - need confirmation from Roon:

_I believe that has been done. I am sure that come the notional change in the rules in mid September, things should be OK._

---

<div class="post-metadata">

**Author:** ![Robert\_Derham](https://community.roonlabs.com/letter_avatar/robert_derham/32/5_5575768a8748004e209b776fc1b2916d.png) [@Robert\_Derham](https://community.roonlabs.com/u/Robert_Derham)\
**Post date:** [September 9, 2020, 11:26pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/13 "2020-09-09T23:26:50Z")

</div>

This really angers me as a customer. Between the Chord Electronics and Roon it is the customer who wears the risk if uncertified past Sep 21. Customers do not care about which camp the current action resides. We just want the worry removed and certification given. Arguments like early product release or not our issue just doesn’t cut it. I have other tier one brands and the experience is the same whether its with software compatibility, bugs & fixes with Roon or just the streamers short product shelf life before being superseded and going out of support.

By no means does this fall solely at Roons feet. Its all the vendors that play in the streaming park to create the product and the services we consume. Right now it feels very immature as a business model and as I said earlier the user wears all the risk with product going in and out of support/certification.

About 4 weeks ago I sat on the fence with a 2go. I was going to purchase another certified device such as a Ultra Rendu…but having the Chord 2 went with the 2go. This is on top of all the other Roon certified devices I have purchased across my 5 zones with a $ outlay essentially car money. My expectation from a premium product and service is its reassuringly reliable albeit expensive and certainly supported.

Right now this feels just expensive and I am quickly getting disillusioned with the industry in general. Does the voice of the customer matter any more today…

---

<div class="post-metadata">

**Author:** ![Fernando\_Pereira](https://community.roonlabs.com/user_avatar/community.roonlabs.com/fernando_pereira/32/55606_2.png) [@Fernando\_Pereira](https://community.roonlabs.com/u/Fernando_Pereira)\
**Post date:** [September 10, 2020, 12:31am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/14 "2020-09-10T00:31:50Z")

</div>

> [@Robert\_Derham](#):
>
> This really angers me as a customer. Between the Chord Electronics and Roon it is the customer who wears the risk if uncertified past Sep 21.

No, the fault is totally on Chord’s side. If they had not advertised the 2go as Roon Ready, I would not have bought it, nor the Hugo 2 I got at the same time. They did, I got it, it kind of works as a Roon endpoint, but it fails too often. I really like how it sounds when it works, but I’m often frustrated by clicks and skips that undermine my music experience. I now use it only when I have no choice, and mostly from a microSD card rather than Roon. If I were not so busy, I’d be pursuing a refund for the whole package for failing to provide what they advertised.

Roon is just defending their IP and reputation. I feel Chord thought they could play fast and loose with Roon Labs because Chord is a famous high-end name who “everybody” respects. I don’t like to be caught in between, but I totally do not blame Roon for standing up to the bully.

---

<div class="post-metadata">

**Author:** ![Robert\_Derham](https://community.roonlabs.com/letter_avatar/robert_derham/32/5_5575768a8748004e209b776fc1b2916d.png) [@Robert\_Derham](https://community.roonlabs.com/u/Robert_Derham)\
**Post date:** [September 10, 2020, 4:21am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/15 "2020-09-10T04:21:51Z")

</div>

Its a valid view, but its not black and white and I think to point only at the manufacturer you are loosing leverage. Don’t forget you are also a customer to Roon through subscription (or lifetime payment) and as a customer to their service they need to manage UX irrespective of where the issue lies to protect their own customer base.

Im hopeful Roon will be reading these forums for feedback. If they are my recommendation is to manage this very closely and get a clear communication out listing those devices scheduled for Sep 21 certification.

---

<div class="post-metadata">

**Author:** ![Andreas\_Philipp1](https://community.roonlabs.com/user_avatar/community.roonlabs.com/andreas_philipp1/32/300324_2.png) [@Andreas\_Philipp1](https://community.roonlabs.com/u/Andreas_Philipp1)\
**Post date:** [September 10, 2020, 4:30am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/16 "2020-09-10T04:30:13Z")

</div>

> [@Robert\_Derham](#):
>
> Im hopeful Roon will be reading these forums for feedback.

They certainly are, and they are reacting on the feedback received today. @danny tonight announced on another thread that they were looking into options to not block uncertified devices from functioning with Roon after the September 21 deadline. We will know tomorrow what they will come up with.

---

<div class="post-metadata">

**Author:** ![Robert\_Derham](https://community.roonlabs.com/letter_avatar/robert_derham/32/5_5575768a8748004e209b776fc1b2916d.png) [@Robert\_Derham](https://community.roonlabs.com/u/Robert_Derham)\
**Post date:** [September 10, 2020, 4:32am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/17 "2020-09-10T04:32:42Z")

</div>

Thanks Andreas

---

<div class="post-metadata">

**Author:** ![Fernando\_Pereira](https://community.roonlabs.com/user_avatar/community.roonlabs.com/fernando_pereira/32/55606_2.png) [@Fernando\_Pereira](https://community.roonlabs.com/u/Fernando_Pereira)\
**Post date:** [September 11, 2020, 2:29am UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/18 "2020-09-11T02:29:06Z")

</div>

> [@Robert\_Derham](#):
>
> Its a valid view, but its not black and white and I think to point only at the manufacturer you are loosing leverage. Don’t forget you are also a customer to Roon through subscription (or lifetime payment) and as a customer to their service they need to manage UX irrespective of where the issue lies to protect their own customer base.

Nope. Chord did the deed when they sold us gear that is not only mis-advertised, but also malfunctions randomly as a Roon endpoint. Everything else follows from that. Roon has zero responsibility to support misuses of their software. That they worked out a way to grandfather uncertified equipment already owned by Roon users is going well beyond their obligations to us.

If you bought a counterfeit Rolex and presented it for warranty repair to a Rolex dealer, would you expect service?

---

<div class="post-metadata">

**Author:** ![xred](https://community.roonlabs.com/letter_avatar/xred/32/5_5575768a8748004e209b776fc1b2916d.png) [@xred](https://community.roonlabs.com/u/xred)\
**Post date:** [September 11, 2020, 5:05pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/19 "2020-09-11T17:05:23Z")

</div>

Folks, we can argue this back and forth forever. I asked Chord, they quickly responded. Said: _"we have worked with Roon to swiftly answer any follow up queries that have been asked."_ I would now like to hear from Roon. What is the status of this certification? Is it in progress? If so, what’s outstanding? What is the ETA? Etc. So far - at least on this thread - Roon has been quiet.

---

<div class="post-metadata">

**Author:** ![Fernando\_Pereira](https://community.roonlabs.com/user_avatar/community.roonlabs.com/fernando_pereira/32/55606_2.png) [@Fernando\_Pereira](https://community.roonlabs.com/u/Fernando_Pereira)\
**Post date:** [September 11, 2020, 10:39pm UTC](https://community.roonlabs.com/t/certifying-chord-2go/117708/20 "2020-09-11T22:39:09Z")

</div>

> [@xred](#):
>
> What is the status of this certification?

According to @danny 2 days ago:

> [@Roon Ready Certification](https://community.roonlabs.com/t/roon-ready-certification/91655/258):
>
> You have not spoken to the right person at Chord. This is not the case. We are waiting for new firmware from them.

[Next page](https://community.roonlabs.com/t/certifying-chord-2go/117708.md?page=2)
