UI synchronization issue after updating to Roon 2.0 Build 1629 (ref#L0UTHO)

[knutselsjord]

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

· Hi Roon Support,I am experiencing a persistent UI synchronization issue that started immediately after updating to Roon 2.0 (Build 1629).The Issue:While music is playing perfectly to my Lumin T3, the playback cursor (the progress bar showing elapsed/remaining time) stands completely still. However, the "audio activity" icon (the blue moving bars next to the track name) shows activity, confirming that Roon knows music is playing.This happens consistently on all my remotes: Windows PC, iPhone, and iPad.Setup:• Core: Roon Nucleus (Rev B)• Endpoint: Lumin T3 (connected via Ethernet/LAN)• Network: Wired connection directly to the router.• Previous state: This setup was 100% stable before the latest update, even when using an optical converter (TP-Link) which has now been removed to rule out hardware interference.Observations:• Restarting the Nucleus resolves the issue temporarily, but it returns after a few days.I have also re-installed the Roon softeware in the Nucleus- to no avail.• The Lumin native app works perfectly, confirming the streamer and network are stable.• The issue persists even after re-installing the Roon apps on my mobile devices.Since this coincided exactly with Build 1629, I suspect a handshake/RAAT synchronization bug between the Nucleus and the Lumin T3 in this specific version.Could you please look into my logs to see why the GUI sync is dropping while the audio stream remains active?Thank you!

Tell us about your home network

· Hi Roon Support,I am experiencing a persistent UI synchronization issue that started immediately after updating to Roon 2.0 (Build 1629).The Issue:While music is playing perfectly to my Lumin T3, the playback cursor (the progress bar showing elapsed/remaining time) stands completely still. However, the "audio activity" icon (the blue moving bars next to the track name) shows activity, confirming that Roon knows music is playing.This happens consistently on all my remotes: Windows PC, iPhone, and iPad.Setup:• Core: Roon Nucleus (Rev B)• Endpoint: Lumin T3 (connected via Ethernet/LAN)• Network: Wired connection directly to the router.• Previous state: This setup was 100% stable before the latest update, even when using an optical converter (TP-Link) which has now been removed to rule out hardware interference.Observations:• Restarting the Nucleus resolves the issue temporarily, but it returns after a few days.I have also re-installed the Roon softeware in the Nucleus- to no avail.• The Lumin native app works perfectly, confirming the streamer and network are stable.• The issue persists even after re-installing the Roon apps on my mobile devices.Since this coincided exactly with Build 1629, I suspect a handshake/RAAT synchronization bug between the Nucleus and the Lumin T3 in this specific version.Could you please look into my logs to see why the GUI sync is dropping while the audio stream remains active?Thank you!

[alex_h (Alex)]

Hello @knutselsjord ,

Thanks for sharing this problem with us.

We have reviewed the diagnostics report from your machine and could have spotted that there are frequest drops in connection with your remotes and especially of the service that is responsible for displaying realtime playback data.

In this case it most likely means there are some misconfigurations in your local network setup (since all of your remotes are being dropped).

We’d recommend you to do following:

1. Reboot your networking gear: Please try a full power cycle of your local network. Unplug your router, any network switches, and Wi-Fi access points for about 30 seconds, then power them back on. After the network is fully restored, restart your Nucleus.

2. Check IGMP Snooping settings: Roon relies heavily on multicast routing to maintain a real-time connection between the Core and the Remotes. Please log into your router’s web interface and look for a setting called IGMP Snooping(usually found in LAN, IPTV, or Multicast settings). Try toggling this setting (if it is enabled, disable it, or vice versa) to see if it stabilizes the connection.

3. Separate Wi-Fi Bands / Disable “Smart Connect”: If your router uses a single network name (SSID) for both 2.4GHz and 5GHz bands (often called Band Steering or Smart Connect), it may cause routing drops for mobile devices. Try separating the bands into two different names (e.g., MyNetwork_2G and MyNetwork_5G) and connect your iPhone, iPad, and PC exclusively to the 5GHz network.

4. Check for AP / Client Isolation: Ensure that features like “Client Isolation”, “AP Isolation”, or “Guest Network” are disabled on your router. These settings prevent devices on the same network from communicating with each other directly, which is required for Roon Remotes.

If the issue persists after these steps, could you please let us know the exact make and model of your main router and time when the issue did happen last time, as well as any network switches or mesh access points you are using? This will help us provide more specific guidance tailored to your equipment.

Looking forward to your reply.

[benjamin]

Hi @knutselsjord,

We wanted to give this thread a quick bump - let us know if you’re able to run through the above. Thank you!

[knutselsjord]

’ done everything on your list. Except splitting the router bands which is not possible on my router. My option would be to buy a new router to extra costs. However, I notice the Roon comments on the latest software update : That the annoying issue I have had, as well as many others, is addressed in this update and possibly solved. I notice that yet another update is under way as I write this. And intend to go on with my current set up to see if a solution really occurs.

[vadim]

Hello, @knutselsjord

Thank you for the update. From the diagnostic data, we can see that you have updated the system to the latest version on both the server and remotes. Please confirm whether the issue still occurs after updating and following @alex_h’s recommendations.