Hi Everyone, here because Linn Support advised I raise a case with Roon as they don’t think there is any fault their end. Is this an appropriate way to reach Roon Support?
Situation is that I just lose visible of the RAAT players within Roon itself, randomly, more on that later. The players work will all other sources when this occurs, they just drop from roon as a playback device. A reboot sorts it for a while and the drop always happen overnight, but not every night. I’d like some help to understand if the logs in roon could give me an idea as to when or why the players are lost within roon.
Personally if feels to me like the RAAT software within the player is failing, but both at the same time!?!?
Just need some assistance to dig deep as the issue while minor it’s a pain to have to fix.
Hope someone can help.
I think I’ll switch from RAAT to Linn Streaming to see if that makes any difference.
I have the same issue with my Selekt DSM Edition which happens from time to time, once a week for example. Only hard on/off of the Selekt restores the visibility.
I opened a ticket with Linn, waiting for their follow up. @silkie have you had any luck with Roon support?
Thanks
No, I never posted in the support section, will do it now. I have an Edition also and it happens on both. Oddly the 2024 Classic will last maybe 48 hrs, the Edition can last a fortnight before having to hard reboot. Glad I’m not the only one.
After providing additional information I’m still waiting for them to come back.
The latest firmware has a lot of issues, so I’m hoping it will be fixed in the next version.
Hi, @silkie
For your reference, this is mentioned in the release notes of the recently released beta version, Davaar 112 Build 566 (4.112.566). I’m planning to try it out to see if it improves things in my environment.
Reboot device on Roon error to combat discovery issues
@simonc - Simon, you’ve been helpful here in the past. Can you tell us anything more about this about the issue and this pending fix?
I have a Selekt DSM: Edition which I use in Roon Ready mode and it currently has no discovery or error issues that I’m aware of. My concern is that there may be errors occurring which I’m not aware of because the system is somehow recovering from them and it would be very unfortunate if my device started rebooting unnecessarily. Or when I’m using it with my turntable, for example.
We have released a Beta version of firmware that will reboot the DSM when the issue occurs, this is not ideal, but will mean you don’t have to do anything. This is a work around until Roon come back to us with a way to remedy the issue.
After 7 months where I have problems almost every day.
@benjamin - could you please tell us wenn this will be fixed?
This is a really unfortunate situation. I suppose, for you, having the device reboot won’t make your problem any worse than it is.
@benjamin - can Roon help with this? I appreciate that Roon and Linn aren’t publicly pointing fingers at one another but this issue has been impacting Torben, and maybe others, for a long time and this pending fix may be worse than the actual problem.
This is a temporary workaround to what we believe is a bug in code from Roon which runs on your DSM. The workaround is triggered when this code gets into a certain error state that we know will render the DSM as undiscoverable to Roon Cores. The error state is normally associated with activity on a Roon Core (e.g. closing it), so will often come at the end of a listening session. It may happen at other times too.
We are in contact with Roon Support about the underlying issue and will remove the reboot when this can be resolved. For now, while we agree that a reboot is undesirable, we have judged its impact to be less bad than having your DSM silently disappear from Roon.
Thanks for the information. Since I haven’t run into the issue, it sounds like I’m unlikely to see reboots. That’s good. I appreciate your response and transparency and I hope you and Roon are able to figure something better out. Thanks again.
This seems more like a streamer/network issue than a DAC specific issue. I don’t think we have enough information to figure out what models are impacted and it might conceivably also have something to do with configuration or networking gear.
I find it frustrating that Roon hasn’t publicly acknowledged the issue. I wish they had a public issue tracker of some sort, but that’s very far from how they operate.
I’m trying out the beta version Davaar 113 after seeing the release note: “Fix Roon session error and remove forced crash. Improves overall device stability.”
Even after performing a manual Roon backup, the device stays connected. I’ll keep monitoring to see how it goes.
I tried several Roon backups and Roon Server upgrade, and there were no issues. It seems to be fixed. The official release of Davaar is also now available.
