ASUS ZenWifi XT8 - AX6600 (wireless, VPN activated on the Mac)
Connected Audio Devices
Argon Audio Solo Streamer (wireless), connected to Argon speakers with optical cable
Number of Tracks in Library
25000 tracks
Description of Issue
I use Argon Audio Solo as a streamer and it shows up in Roon as “Roon Ready” and I’ve used that as my primary way of playing tracks. After a few days it disappears and the only option that is left Is the “Argon Audio AirPlay” which continues to work. When I reset the Argon Audio Solo to factory settings it’s back as “Roon Ready” but after a couple of days it disappears again.
My apologies for the slow response. We’ve been doing our best to get caught up and we’re almost there.
I have sent a request for diagnostics logging that will return to me once you bring the core back online. I want to check and see what Roon thinks is happening when this happens. That said, I want to explore a few of other options too:
A RAAT refresh. I’m hoping something here is corrupted and is the source of the issue.
You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:
Hi @Wes
I just ran into the same issue, is there any other "soft* way of resolving the issue ? My Argon Solo is visible as a Chromecast and airplay device but no more as a roon ready endpoint.
I fully understand the steps you described but was wondering if we could skip the whole reset ?
This action only resets your audio devices and DSP settings. A full reset may become necessary but I was hoping this reset of devices would do the trick.
Hi @Wes
I contacted Argon guys, and they have no clue, and they also sent me to discuss this here on roon forums (i’m not really sure how and why they are still selling a device advertised as roon ready that it isn’t (at least my device).
Before i do the steps mentioned above, will the RAAT refresh also wipe my listening queues on the end points ? (i kinda have a style per device since they are located in different atmospheres).
Hi @Wes
Reporting back : i did the steps mentioned above, but the Argon Solo is still not visible as roon ready (only visible as Chromecast and Airplay).
Worth noting that despite renaming the folder “RAATServer” to “RAATServer_old” adter restarting the core, the new folder was created but nothing was lost (the simple crossfeed DSP im using with headphones was still saved).
Have you tried turning off your VPN as Roons network discovery may have issues with this for RAAT based zones, AirPlay and Chromecast rely on different discovery methods. It would be my first port of call to try this if not all ready.
Any update on your status? Did you get a chance to try things with your VPN disabled? (you may need to ensure it’s disabled and restart the Mac for normal network operation). I have one more thing to address and will address it below.
@Sky-Watsher, your issue appears to be slightly different. The SOLO is refusing your connection and your Roon diagnostics logging is full of these errors. Today from 15:11 UTC to 15:33 there are over 20,000 connection errors to the device. I recommend you wipe Roon and RAAT folders on your ROCK with the instructions above.
There was a known issue with the Argon SOLO where their firmware update changed how the device reported to Roon. Does either of you show an unknown device in Roon>Settings>Audio? Do you have the option to find your device?
When I look at diagnostics logging I can only see @Martin_Nilsson’s SOLO initialize and this was back on 2/13. At that time, the device was running firmware version p15235.125.0 but it has since disappeared from the account. Was there a firmware update around the time that the issue started? Can you both confirm your current firmware version?
I think I know what’s happening here. For you at least
The steps I quoted above are what I’d like to see done. This won’t in any way affect your databases but will reset audio devices. You might have to re-enable your devices and lose custom DSP configurations.
I’m thinking that the device identifying itself differently post-firmware update is causing this never-ending connection loop. This will help greatly.
Hey @Wes
Same story, did the steps, device not visible as roon ready (still visible as Chromecast & Airplay end point).
Worth re-noting : after the steps above, roon creates a new RAATserver foldr, but i’m not loosing the DSP applied to my primary endpoint (a desktop dac), Crossfeed is applied and it is still there after the steps.
So here’s what I see and it’s no different than what I have seen before you made changes.
02/22 22:19:45 Trace: [raat] [Argon Audio SOLO () @ 192.168.1.148:50732] lost client connection. Retrying
It’s repeating continuously. It’s worth a complete power cycle of network elements, Roon core, and endpoints for this reason.
After that, it’s possible there’s a DB issue at play but only one sure way to know and that’s to wipe Roon folders completely and see if connectivity is restored. Do this with a fresh DB and test it before re-importing the DB to test again. Please note, you should back up your database before embarking on this!
Hi @Wes
i actually did something i should’ve tried first, which is the well-tried troubleshooting method : Reset the endpoint !
I did reset the Argon solo, and set it again through the google home, and it’s now showing again as a roon ready end-point.
I will watch it for a couple of days and see if it will function properly.
