· Since Update 2.58 my Roon endpoint (Wattson Audio Emerson) won't play - unless I reboot Roon server or make an adjustment to any setting in device settings and then save it. Also, all device zone icons across all my Roon endpoints have disappeared and been replaced by defaults.
Tell us about your home network
· BT Smart Hub 2 router. Network Acoustics Tempus switch
Thanks for reaching out and sharing your issue here.
To help us narrow down the cause of the problem, could you please check the following three areas?
Network Simplicity Do you have any network switches or a Mesh Wi-Fi system in your setup?
Test: If so, could you please try temporarily connecting your DAC directly to your main router via Ethernet? This will help us rule out any hardware that might be interfering with the signal.
2. Firmware Updates Please ensure that the firmware on your DAC is fully up to date.
Context: Since we recently released a major update to Roon, many of our partners have also released updates for their devices to ensure continued compatibility.
3. Power Settings Please check your DAC's settings menu and ensure that any "Energy Efficiency" or "Sleep" modes are turned OFF. These settings can sometimes cause the device to drop off the network unexpectedly.
Switch removed from path so DAC is now direct into router. DAC software up to date, and there are no sleep modes etc. Having rebooted Core (residing on Innuos ZENith NG) the zone icons returned, but the Wattson Emerson would not play. Having pressed play I notice that although the progress bar along the bootom stays at 0s at the start of the track, the moving histogram alongside the device icon bounces up and down as though something is playing. Changing and saving a setting (any setting) in device settings clears the problem after which everything behaves as it did prior to Update 2.58. All other Roon endpoints (Linn, Sonos, dCS) are unaffected by this issue. Hope that helps?
Thanks for the update! When the histogram (that little jumping EQ graphic) is moving but the progress bar is stuck at 0s, it means the Roon Server thinks it’s successfully pushing data, but the Wattson Emerson isn’t acknowledging the stream or starting its internal clock.
When you change and save a setting in Roon, the server sends a re-initialization command to the endpoint. It essentially “re-boots” the software connection without power-cycling the hardware. This forces the Emerson to re-sync its clock with the server, which is why it works until the next session.
A few next steps for you to test:
The "Deep" Disable/Enable - Instead of just changing a setting, go to Settings > Audio. Find the Wattson Emerson, click the gear icon, and Disable it. Wait 30 seconds, then Enable it again. This sometimes clears a hung cache in the server better than a simple setting tweak.
Check for "Flow Control" or "Multicast" on the BT Hub Even though the switch is out of the path, the BT Smart Hub 2 is notorious for being "too smart" for its own good with multicast traffic (which Roon uses to find and sync devices).
Ensure "Smart Setup" is turned OFF in the BT Hub settings.
If the BT Hub has a "Power Saving" mode for Ethernet ports, disable it.
Address the "Ghost" Icons - the disappearance of icons is a sign that the server's image cache was corrupted during the 2.58 update. Since a reboot brought some back but the Wattson is still acting up, try this:
In the Roon Remote app, go to Settings > Setup > Clear Image Cache.
Let me know if any of the above help, thanks Simon! 🙌
Thank you Benjamin. All measures you suggest have been implemented, but no change alas. I note that similar issues have been flagged up elsewhere by others so I hope a solution is in the making. With thanks.
Thanks for letting us know. We have made some changes in our Early Access branch which may help with the behavior you mention. If you’d like to give Early Access a try and let us know if it helps in your case, you can follow the instructions below (or wait for it to be published to production), thanks!
We wanted to check in on this thread as it has not seen a response in some time.
What is the network path between your Roon Server machine and the Wattson Audio Emerson endpoint?
The icon issue you reported might have resulted from upstream infrastructural issues that affected Roon’s servers around the time of your first post. Are you still seeing generic icons for your Zones at this time?