The contents here are provided as-is by me and analysis is purely my own opinion. Its totally possible I am completely wrong about all this…. 😉
If you have had a Chord Poly since launch, you know that its… umm… “challenged” to say the least. There has been a ton of negative feedback and in fact, of 17 Poly owners I surveyed only 3 declined to add more freeform text complaining it wasn’t ready for prime time.
At best 14 out of 17 people aren’t impressed.
I have also worked with a sniffer to point out that they’re not implementing IGMP or DLNA properly, and so on “smart networks” its not a surprise it’s a dead duck and doesn’t even show up in a list of DLNA devices at all…
If this was the level of quality out of just discovering DLNA servers… we had to strap in because it was going to be a bumpy ride.
Amazingly there are reviews that have no mention of any of the issues despite the greater than 80% of users weighing in negatively. The closest they get is “difficulty setting up”
But… its actually not Chord’s fault at all..it’s been outsourced I believe
Here, courtesy of a Head-Fi person are the innards of a Chord poly.
Notice the http://www.disignconsultants.com text on the top of the picture?
My poly also performed an update a few days ago, and imagine what I found in my Meraki Dashboard showing all traffic from Poly in the last week:
disignupdate.com was the only external site – and 2.4MB was downloaded by Poly.
You may also notice that the device is advertising that it does 2.4GHz AND 5GHz, which is not the case – its supposed to only have a 2.4 radio…
Clearly the hardware and software for Chord poly came from http://www.disignconsultants.com who, as it turns out, are in the UK and do consumer music players:
Unfortunately, this is going to mean slower updates and quite frankly, that some of this is out of Chord’s control.
Now, as I dug into the sniffer traces, I see some of the SSDP broadcasted packets from the device, including details of the software stack running. Here is a packet from the Chord Poly broadcast on my network:
As you can see this is running MiniDLNA v1.1.5. The trouble is that MiniDLNA, which is now called RedyMedia, is actually at version 1.2.1. and 1.1.5 was updated in September 2015: Interestingly a subsequent update just 3 months ago fixes a discoverability issue.
It also turns out that by looking at some of the packets, we can see this, in in fact, a linux box. You can see yourself by hitting it with a browser:
Chord Poly:JPoly [Server]
Chord Poly on Linux