In the last few days, we’ve been asked what’s going on with Mytek’s Brooklyn Bridge. We were hoping to stay out of this, but part of being Roon Ready means we keep our users informed on issues that could impact their Roon Ready support.
It is our understanding that Mytek is in dispute with their ex-business partner, a company named HEM. An action has been taken by HEM that is bringing customers into the dispute. These 2 companies need to resolve this situation themselves, and hopefully, they can do that without affecting existing customers any further.
We are willing to share what we feel is important for Roon users to know if they are using the Roon Ready integration of the affected product (the Mytek Brooklyn Bridge).
We love the Brooklyn Bridge. It’s one of our favorite Roon Ready integrations.
In regards to the dispute, our relationship has been with Mytek Digital USA, and our primary contact has been @michal_jurewicz1. Mytek Digital USA, specifically @michal_jurewicz1, has led and been involved in all aspects of the Brooklyn Bridge’s Roon Ready certification. He has delivered all the devices to us, managed the development efforts, and dealt with us on all marketing activities. All of the web and manual links that are shown point to the website Mytek Digital USA and @michal_jurewicz1 owns.
We do not have any relationship with HEM, although they do seem to have created Roon community accounts in the last few days to post here.
Right now there is device firmware that has been released by HEM that some devices have taken which changes the branding of the Mytek Brooklyn Bridge to HEM branding, while still reporting itself to Roon as a Mytek device. Because this is just a firmware update on a device that was already certified, it is now being inconsistent in that it displays Mytek branding in Roon and HEM branding on the device.
This firmware was not certified by Roon and is not in compliance with the Roon certification requirements. We can’t recommend changing to firmware that has not been tested by Roon Labs, especially one that creates confusion and inconsistency. Please avoid this firmware.
If you have been impacted by this, you should contact firstname.lastname@example.org, who can help you get back on track.