Roon Ready WiiM Pro Plus not recognized (ref#DGUHER)

Support
1

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon Ready WiiM Pro Plus

Tell us about your home network

· Roon installed on a MS laptop, 3 x WiiM pro plus all on the same network
1 WiiM is showing as Roon ready while the other 2 are not

2

Hey @nick_sarnadas,

Thanks for writing in and for sharing your report! We were able to review fresh Roon Server logs and can confirm Roon identifies all three WiiM Pro Plus units correctly. The device-db autodetect matches them cleanly as Roon Ready:

[devicedb] [autodetect] Match ...[Type=RoonReady Vendor=Linkplay Technology Inc. Model=WiiM Pro Plus] => WiiM Pro Plus

All three run identical firmware (Linux 4.9.113, kernel build Jul 9 2025), so there’s no model or version mismatch. The problem seems to be at the RAAT connection/handshake layer, on the device side, not identification.

Since the two failing units behave identically to the working one at the identification stage, focus on getting their RAAT service and network path healthy:

  1. Power-cycle the two problem WiiMs (full unplug, not just standby). A hung RAAT service is the most common cause of "session timed out during initialization," and it's the fastest fix.
  2. Set DHCP reservations / static IPs for all three. The logs show the units bouncing across .113/.114/.115 with changing ports, that churn suggests unstable leases or possible address contention, which breaks RAAT reconnects.
  3. Check WiiM firmware and re-enable Roon Ready in the WiiM Home app for the two units (toggle the Roon output off/on), this restarts the RAAT endpoint.
  4. Rule out multicast/mDNS blocking between the laptop and the two units (WiFi vs. wired, AP isolation, "IGMP snooping"/multicast filtering, or a mesh node). The working unit and the two failing ones likely sit on different network segments or a weaker WiFi path.
  5. If a unit still won't complete the handshake after that, it points to that specific WiiM's RAAT stack, a factory reset / firmware reflash on that unit is the next step.
We’ll be monitoring for your reply, thank you Nick! 👍