Roon app drops audio device icon and crashes upon enable/disable (ref#RME9JU)

[stf4me]

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

· The Roon app keeps dropping one of my connected audio devices. When playing a track, the audio device icon (which you can usually click on to select which audio device you would like to use, if more than one device is available) in the left does not appear. Instead a fuzzy dot is displayed.

If I go in the settings menu and to audio and click disable on the device and then click enable the Roon app window closes.

When I play a track it turns on and plays music on one of my two audio devices. I cannot select which device as the usual audio device icon in the left is not present.

I have two audio devices connected (hardwired, Ethernet cable) to the Roon Nucleus, a Cambridge Audio Edge NQ and Cambridge Audio EVO150. A reboot of the Nucleus and/or the EVO150 does not resolve the issue.

Tell us about your home network

· Roon Nucleus, Cambridge Audio Edge NQ, Cambridge Audio EVO150

[benjamin]

Hey @stf4me,

Thanks so much for taking the time to write in and share your report! We were able to review a fresh Nucleus diagnostic report, and saw that every single drop event in the logs follows the same pattern — the Edge NQ sends a “status”:“Lost”,“reason”:{“reason”:“standby”} message back to Roon while a track is mid-play. Roon receives this, logs “Track Stopped Due to LostEndpoint,” and the zone suspends.

This is the device itself going to standby unprompted, not a network issue or a Roon bug.

For example, on 05/03 at 11:27, the Edge NQ started playing Waltz for Debby and dropped into standby just 9 seconds into the track. On 05/01, it played Rhapsody in Blue for about 1 minute 22 seconds before going to standby. The EVO 150 has similar (but separate) drops, also triggered by source_deselected or standby from the device side.

There’s also a secondary issue: the RaatServer localhost @ 192.168.40.203:9200 loses its client connection repeatedly (sometimes every 10 seconds for several minutes). This is what causes the “fuzzy dot” and the missing device selector icon — the RaatServer process loses its internal connection and the zone becomes unresolvable until it reconnects.

For some next steps in troubleshooting:

1. Disable auto-standby / sleep on the Edge NQ

   Go into the Edge NQ’s own settings menu (on the device itself or via the Cambridge Audio app) and look for an auto-standby or sleep timer setting. The device has “is_standby_supported”:true and is clearly using it aggressively. Setting the standby timer to “off” or the maximum delay should stop the drops entirely. On Cambridge Audio units this is sometimes called “Network Standby” or “Auto Standby” and may default to something like 20 minutes of input inactivity

2. Check the Edge NQ firmware version

   Log into your Cambridge Audio account or check the StreamMagic app for any available firmware update for the Edge NQ.

3. For the EVO 150 drops : The EVO 150 is dropping due to source_deselected — meaning something is changing the source away from Roon (e.g., someone pressing a button on the unit, or a network/app interaction switching inputs). Check whether anything else (the StreamMagic app on a phone/tablet, a physical remote, or a preset) might be inadvertently changing the EVO 150's input.

We’ll be monitoring for your reply and results 🙏

[stf4me]

Hello Benjamin,

Thanks for reading my report a problem and very response along with suggestions. I have checked for updates in StreamMagic. There was one for the Edge NQ not one for the EVO150.

Unfortunately, I am still having a problem with Roon showing both of the devices. This is a new issue. I’ve been running this set up for three years without having this problem.

I was recently experiencing the issues that you are aware of with dropping songs from Qobuz. That appears to be resolved. Now there is this issue of not finding the device.

I do not have any other devices that would be switching the input on the EVO150.

I’ll continue to troubleshoot on my end looking at what can be done on both the Cambridge Audio devices.

It appears I’m finding some other chats in the Roon support of others whose device devices are not recognized.

Please continue to investigate if there’s an issue with the Roon app which may be causing room not to find devices.

Thanks,

Chris

[stf4me]

P.S. I can select Roon Ready from StreamMagic using the EVO150 and press play and it is playing in a shuffle mode.

However, I cannot see/connect to the EVO150 on the Roon app where I can usually select which device to choose for playback.

[stf4me]

[stf4me]

[stf4me]

Hello Benjiman,

Now my Roon app is playing on my EVO150, and does not show the availability of the Edge NQ. Whereas previously it was only playing on the Edge NQ and not showing the EVO150.

[benjamin]

Hey @stf4me,

Thanks for the update and additional information! From a fresh Roon Server diagnostic report, we can see both devices ARE being discovered and connected correctly.

Every time Roon Server starts or reconnects, both the EVO 150 and Edge NQ are found via SOOD, RAAT sessions initialize successfully, and zones are created with. The devices themselves are not the root problem.

The real issue is a repeating zone destroy/recreate cycle triggered by client reconnections. The pattern visible across multiple logs is:

1. A Roon Remote client (your iPhone) connects or reconnects
2. SOOD refreshes its device list
3. Within seconds, one or both zones are destroyed and immediately recreated — sometimes while actively playing (confirmed on 05/04 at 12:15:51: destroyed zone EVO150 was playing? True)
4. After recreation, only one zone tends to be "in focus" for the active client, causing the other to appear missing from the UI

The Edge NQ is also potentially running outdated firmware.

Some next troubleshooting steps to try:

1. Force a firmware update on the Edge NQ. You mentioned StreamMagic showed an update for the Edge NQ — apply it if you haven’t, or verify in StreamMagic that it’s fully applied. The RAAT version gap (1.1.38 vs 1.1.43) between the two devices is a meaningful discrepancy and the most actionable firmware-level fix. After updating, reboot the Edge NQ completely.

2. Disable the EVO 150’s AirPlay advertisement or rename it consistently. The “Evo 150 Living Room” AirPlay zone is confusing the transport layer. In StreamMagic on the EVO 150, find the device name/AirPlay name setting and make sure it is set to something that clearly aligns with how Roon refers to it. Alternatively, in Roon Settings → Audio, ensure there is no lingering disabled AirPlay zone for the EVO 150 listed separately from the Roon Ready zone.

3. Investigate the iPhone’s network stability. The frequency of iPhone disconnects and reconnects (sometimes every 10–30 seconds) is abnormal. Check whether the iPhone is on Wi-Fi and whether Wi-Fi Assist or any VPN is active. Each reconnect is triggering a chain reaction that can disrupt which zone is displayed. Disabling Wi-Fi Assist on the iPhone is a quick thing to try.

4. Assign static (reserved) IP addresses to both Cambridge Audio devices on your router. Both devices appear to have stable IPs in these logs (.93 and .115), but DHCP lease renewals could cause brief disappearances. Binding their MAC addresses to fixed IPs in your router’s DHCP settings will eliminate that variable entirely.

Let me know if any of the above help, thank you @stf4me!

[stf4me]

Hello Benjiman,

Thanks for the follow up. I uninstalled the Roon app on my phone and reinstalled it, and both devices are now recognized.