Roon clients require power cycle after server software update

Roon Core Machine

Linux, Intel i5-8400, 16GB

Networking Gear & Setup Details

Fritzbox 7590 AX

Connected Audio Devices

KEF LS50 Wireless II
Hegel H390
(Firmware fully updated)

Number of Tracks in Library

300 albums (all Tidal)

Description of Issue

Whenever I update Roon Server (at least the last 3 times) it is unable to find any network audio devices. Restarting the server doesn’t help, and waiting a day doesn’t help. Only hard power cycling the clients gets them to show up in Roon again (unplugging them from the wall and plugging them back in).

The clients otherwise work perfectly and show up in e.g. Airplay without an issue.


Description of Issue

As above, my local devices, specifically my Sony TA-ZH1ES DAC/AMP needs to be continuously reenabled everytime Roon updates, or at random times. All other devices that are not connected directly to the PC running RoonServer stay in chosen state.

Running latest RoonServer.

It’s 3 days later. My Hegel H390 appeared immediately when I unplugged it and plugged it back in. I haven’t crawled under my desk to unplug the KEF LS50 Wireless IIs, so they are still not showing up.

any update on a fix?

Does someone need to flag @support for this to be read?

My Hegel H390 is gone again. The LS50 Wireless IIs still are not there either. I have arthritis, so this issue makes Roon functionally unusable. Thank you.

Regarding the recent disconnection, I confirmed the server loses network clients when restarted also. So this happens on server restart or software update. Thanks.

Hi @palmy,

Thank you for your patience while the Roon team worked through our queue to reach your case.

To isolate the issue, please try removing WiFi as a variable by testing these endpoints hardwired, if possible. The LS50 Wireless II should have an ethernet port you can use; please attach via ethernet and then restart RoonServer to reproduce the issue.

The team will pull diagnostics in the meantime to investigate potential multicast issues in your network and follow up from there.

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.