· Immediately after updating the FiiO M11 Plus ESS to firmware 1.0.4, Roon no longer recognizes it as a certified Roon Ready device. Instead, the device appears as Uncertified and cannot be enabled. Prior to the firmware update the M11 Plus worked normally. Marantz Model 40n, FiiO SR11, Sonore microRendu and ultraRendu are all functioning properly. FiiO support responded to my issue by sending me a manual for Roon. Any help that you could provide would be greatly appreciated.
Tell us about your home network
· Verizon Fios CR1000A router and the CE1000A extender that is hardwired to the router. The router is connected to the TP-Link TL-SG105S-M2 | 5-Port Multi-Gigabit 2.5G Ethernet Switch and the extender to a TP-Link TL-SG108S-M2 | 8-Port Multi-Gigabit 2.5G Ethernet Switch. I have been using Tailscale for a couple of years on my Mac Mini M4 for a stable connection when using Roon Arc.
Thank you for reaching Roon support. The device changed its advertisement. We have forwarded your request to the appropriate department for further review.
Thank you for your patience while we looked into this.
We checked with our partners team, and the cause has been identified: a FiiO firmware update changed the device’s advertised name from
FiiO M11 Plus
to
FiiO M11 PLUS
and this mismatch is what’s behind the behavior you’re seeing.
This kind of change does happen with vendor firmware from time to time. Our partners team will raise it with FiiO from our end, and we’d ask you to report it to FiiO support as well - a report coming directly from an affected customer usually helps move things along faster.
We’ll keep you posted on any developments. Thanks again for your patience!
I just installed an .apk file sent to me by an engineer at FiiO, and everything is functioning smoothly once again. I appreciate the quick response from Roon support, which allowed FiiO to promptly release a fix.
Trevor’s issue was caused by a firmware change on FiiO’s side (the M11 Plus started advertising its name differently after their 1.0.4 update), and FiiO already provided him a fix directly.
If you’re running into the same thing, please reach out to FiiO support with the details, they’re the ones who can get you sorted.
@Trevor_Arnold , thanks for confirming the fix worked and for reporting it back to FiiO.