Hello @Rob_DeMillo ,
Apologies for the slow response here, our support team has recently undergone some changes to keep up with needed volume, and we’re working hard to catch up with all of our users.
We have been discussing this issue in-house since your Reddit post, and while we are seeing some of the cast disconnects you are seeing in our logs, they are nowhere near as often as on your end and are not leading to significant resource usage.
Please note that Roon Build 970 addressed a few memory leaks, and this may have had something to do with the RAM usage you were seeing. I’d be curious to know if you are still seeing this even after updating to build 970 or above.
After some internal discussion, it looks like mDNS is involved in the issue, when we see the cast lost on our end, it looks like there is also a TTL=0 mDNS packet and TLS errors, like so:
Info: [cast] lost device Chromecast Ultra because we got a TTL=0 mDNS packet
Info: [cast/client] [Chromecast.local] Unable to authenticate TLS connection
Are you seeing the same on your end when the issues occur?
Can you provide any more details on how these devices are grouped? Do you have significant amount of grouped zones under the Google Home app?
It would also be good to see if the current database has any impact on this issue. If you can please confirm if you see this on your end with a fresh database, this would be a very useful data point to have, I have provided instructions below on how to achieve this:
- Create a Backup of your current database
- Exit out of Roon
- Navigate to your Roon Database Location
- Find the folder that says “Roon”
- Rename the “Roon” folder to “Roon_old”
- Reinstall the Roon App from our Downloads Page to generate a new Roon folder
- Verify if the issue persists on a fresh database before restoring the backup
Please, do let us know your thoughts on the above when you have a chance, thanks!