Roon Ready Playback Failing to Initialize After Update to 2.58, Restart Potential Workaround [Fix in latest production]

Support
42

Hello @Henk-Willem_Kleij ,

Thanks for reaching out with your report. We are looking into similar reports, can you please let us know the exact local time + date + track when you are able to next observe this issue? We’ll enable diagnostics for your Roon Server.

43

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

· I updated the firmware to both of my DMP A6 the other day. I now suspect a RAAT registration/handshake regression in the current Eversolo DMP-A6 firmware.

Tell us about your home network

· Araknis Router AN-310-RT-4L2W
An Araknis WiFi AN-700-AP-I-AC.
One DMP A6 is hard wired with dedicated IP address, the other is wifi.

Additional Information

  • Hardware
    • Two Eversolo DMP-A6 units
    • Other endpoints on the same Core: OPPO UDP-203, Marantz AV7705
  • Core
    • Roon Server running on macOS (Mac mini)
    • Network otherwise stable
  • What’s happening
    • After updating firmware on both DMP-A6 units, they no longer stay visible as Roon Ready endpoints.
    • In Settings → Audio, a DMP-A6 may briefly appear with no name, then disappear within a second.
    • The endpoint never becomes stable or enable-able.
    • This happens even when powering up one DMP-A6 at a time.
  • What still works
    • Both DMP-A6 units appear and function normally as AirPlay targets.
    • Other RAAT endpoints (OPPO UDP-203, Marantz AV7705) work normally and reliably.
    • Confirms network, multicast, and Core are functioning.
  • Earlier behavior (before full power cycle)
    • Prior to power cycling, both DMP-A6 units would sometimes show as “playing” (animated bars in zone selector) but controls were unresponsive.
    • Disabling and re-enabling the zone immediately restored playback.
    • Restarting the Core also resolved it temporarily.
  • Logs
    • RAATServer logs show repeated RAAT session timeouts (~10s) followed by session destruction.
    • Endpoint appears to advertise itself but fails during RAAT capability/handshake phase.
    • Core believes playback/session exists, but endpoint does not complete registration.
  • What’s been ruled out
    • Pi-hole (disabled for testing)
    • Network issues (other RAAT endpoints stable, AirPlay works)
    • macOS firewall / permissions
    • Roon database corruption
    • Control point issues
  • Conclusion
    • Strongly appears to be a RAAT registration/handshake regression in the current Eversolo DMP-A6 firmware .
    • Endpoint advertises but fails to complete RAAT initialization, resulting in unnamed “flash then disappear” behavior.
44

Hi Noris,
I think this will be tomorrow morning. At this moment everything works fine.
I’ll contact you tomorrow before I switch on my Copland DAC. I hope these actions will also help my friend..
Thanks!

45

Hi there,

did an automated software update from 2.57 to 2.58 couple of days ago.

Now, my two Auralic Aries devices show drop outs / don’t start playing music. :sob: Both, streaming service based (Tidal) and local stored music. Haven’t had any issues before with 2.57. :smiling_face_with_three_hearts:

So, quick question would be, how to get back to 2.57?

Many Thanks
Best
Sven

P.S. Disabling RoonReady Device Auralic Aries and Re-enabling does solve the issue temporarily - strange

roon running on MacMini OS X Ventura 13.7.8 with 8GB RAM and all music stored locally on SSD
roonready endpoints connected via LAN

46

Hey @Babayaga,

Thanks for taking the time to write in and share your report, as well as providing such through troubleshootings steps so far!

We’ll share this with our partners team immediately. Have you reached out to Eversolo directly yet?

In the meantime, if you haven’t yet, I’d reboot your router and network gear alongside your server and endpoints just to be thorough.

Thanks for your patience in the meantime! :folded_hands:

47

Uploaded a secondary log file name “dtdcampbell 2”. Did the following steps below.

  • Attempted playback at 4:36pm est, failed
  • Reboot initialized from Nucleus One from web interface 4:39pm est
  • Normal playing of tracks at 4:40pm est
48

Hi @Sven_Eschholz,

Thanks for taking the time to write in and share your report! Sorry to hear about your playback issues.

This is unfortunately not available at this time, but our team is actively investigating similar reports that have trickled in since the latest update.

If you haven’t yet, could you please:

  1. Power cycle your audio devices, roon server machine, and router
If you hit the same issues, let’s see if refreshing your RAATServer database may help:

You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings -> Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:

  • Create a Backup of your current Roon database
  • Exit out of Roon
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RAATServer”
  • Rename the “RAATServer” folder to “RAATServer_old”
  • Restart the Roon App to generate a new RAATServer folder

Thank you! :raising_hands:

1 Like
50

Hi @alex_h / @benjamin ,

While waiting for the Devices Team’s review, I went ahead and conducted a final controlled cross-device stress test to help narrow things down further (Feb 6th).

The following sequence was performed back-to-back within 15 minutes:

  • 12:01 - 12:03: Roon → Lumin U2: FAILED
  • 12:04 - 12:06: Lumin Native App → Lumin U2: SUCCESS (Played instantly)
  • 12:07 - 12:09: Roon → Lumin U2: FAILED
  • 12:10 - 12:12: Roon → Hegel H390: SUCCESS (Played instantly)
  • 12:13 - 12:15: Roon → Lumin U2: FAILED

Technical Summary:

  1. Hardware/Network Isolation: Since the Lumin Native App worked perfectly at 12:04, the Lumin hardware and its network connection are clearly 100% functional.
  2. Server/OS Isolation: Since Roon played to my Hegel perfectly at 12:10, the Roon Server (Mac mini), the OS environment, and the network backbone are all 100% functional.
  3. The Specific Bug: The failure is exclusive to the Roon-to-Lumin RAAT handshake.

I’ve provided these exact timestamps so the Devices Team can look at the diagnostic logs for my account during this 15-minute window. This clearly points to a logic regression in RAAT specifically affecting Lumin endpoints.

I hope these timestamps are useful for the Devices Team’s investigation. Happy to provide any additional testing if needed.

51

Goodmorning!
I’m ready to start my system. Please tell me when you’re ready to start your logging

52

Okay,
I’m in Rotterdam (UTC+1.00h)
10.58 starting up dac
10.59 trying to play local music. Abraxas Santana. Singing winds, Crying birds
Nothing . Counter stays 0.00
Jumps to next track etc
Next 11:03
Album from Qobuz: Lambchop, The Bible. Reservationd
Nothing. Counter stays 0.00 etc
Btw: the Lumin stayed OFF during this… normally it should automatically start
I restart my nuc at 11:04
I close Roon app on my tablet
11:07 open Roon on my tablet
Start Lambchop: everything works normal

That’s all.
Thank you

53

Hi Noris. After all worked fine, I got a message for an update session for my Lumin. After the update, I could play music via the Lumin, but via Roon the issue was again there.. So I had to restart my NUC again (BTW: the Lumin was then ON)
Perhaps tomorrow everything is okay. I’ll let you know tomorrow

54

Hello @dtdcampbell

We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.

You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.

55

Hello @Ian_Spencer,

Thank you for working through all of those steps — at this point, we’d like to pause further changes and capture a clean diagnostic snapshot.

To move this forward, could you please do the following:

  1. Restore the setup to the original state (the one where playback fails):
  • Roon Server running on the NUC
  • Luxman NT-07 connected to the network
  • NT-07 connected to the D-10X for playback
  • No temporary workarounds (AirPlay-only zones, alternate outputs, etc.)
  1. Once everything is back in that original configuration, please reproduce the issue:
  • Start Roon normally
  • Attempt playback to the Luxman zone
  • Confirm that playback does not start unless the server is rebooted
  1. Please note and share:
  • The exact local date and time when playback fails
  1. Restart the core and update us here

With the system in this failing state and a precise timestamp, we can pull the correct diagnostics and see why the Luxman endpoint is not re-initializing correctly after the device state change.

Thanks again for your patience — once we have this timestamp, we can continue the investigation.

57

Hello @Henk-Willem_Kleij

We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.

You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.

58

One other note…
If I disable the Eversolo device and re-enable it, it works as usual…

59

Hello @atletico

Thank you for the update.

We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.

You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.

61

Oké, thank you!

62

Hello @Babayaga

We’ve discussed this with our senior QA and development teams. The team is investigating some possibilities here and, as soon as that investigation is complete, we’ll be sure to follow up ASAP.

You have our apologies for the trouble here, and we’ve greatly appreciated your patience as we continue investigating this tricky issue. We’ll be in touch as soon as we can.

63

A reboot of my Roon server has solved this issue for me.

64

Thanks for your latest mail. I have done exactly as you asked.
16.05 (all GMT) Rebooted server
16.08 Played streamed track successfully at high res.
16.09 Switched D-10X function to CD and played CD
Returned function to stream
16.10 Unsuccessfully attempted to stream
16.11 Rebooted server
I hope this helps you save the problem.
Thanks,
Ian