Hey, all!
The new Roon EA build includes improvements for Google Cast device discovery on your network, along with overall stability improvements. If you have Chromecast Audio devices, Google Home, or other devices that play via the Google Cast protocol, please watch for stability issues like zones disappearing mid-playback, device duplication, etc.
This is the thread where we’d like to ask you to post your feedback so that we can consolidate it in one place.
cc: @Stephen
Thanks!
–
Ivan
Hi, Is this the fix for this issue from October '22
I still had this issue as recently as Monday morning.
So let’s hope it does fix the duplicate Chromecast Groups issue.
Many thanks
Hi, @simon_pepper, we hope so, please give it a try and if you are still able to reproduce this, let us know and we will collect the diagnostics report from your machine.
Thanks!
—
Ivan
The tl;dr; of this chromecast effort was that I joined Roon and had a ton of chromecast devices and was getting annoyed that they were all working 
So, it is a broad mix of getting things like Sony TVs (I don’t have one so couldn’t really test it) and LG TVs to finally show up as chromecast targets. It also involved improving streaming to various devices like nest displays, audio casts, etc. Other minor things such as showing the chromecast group name before you enable it, etc.
IF you run into issue please, please tag me. I’m still working on a few issues I’d like to try and get in before the final release.
@Stephen
Did you ever get to a win here ? My LG OLED (OLED77C14LB on WebOS6.5.3) still doesn’t want to play ball as a Roon chromecast display.
My LG C3 worked perfectly back in 2024 when I first got Roon, but there was some webOS update that made it stop maybe late 2025, and we never came to a resolution. Hopefully this is solved, but I am on production channel and not EA, despite enjoying the EA threads here.
Chromecast not functioning on LG C3 TV (ref#R6PEIG) - Support - Roon Labs Community
I have an LG C2 and C4 at home. I’ll test on that first thing tomorrow morning.
I’ll add this to my list to double check.
@ncpl I did a little digging, and it seems like the C1 never had chromecast support built into the TV. I’m not sure if it requires hardware or just firmware, but it doesn’t sound like they are going to add it either 
I have to factory reset and update my LG C2 in order to get chromecast working. It seems like the LG C2 barely made the cut?
Just sent off some more changes to QA. The next EA release (soon?) should have some more minor improvements and fixes.
Not sure if anyone else has hit this, but I did discover while testing that if you run some kind of ad blocker network wide it can potentially block some of the LG domains which prevents the LG TVs from working correctly. Namely, being able to install or run chromecast on them. 
Hi, Getting duplication of Google Chromecast Groups with this latest EA Build.
This has been a recurring issue, reported here Duplicated Chromecast Groups [Ticket In] in October '22, so its coming up to 4 years.
The latest entry on that thread was there is a fix coming, and then the thread was closed, without any further confirmation on the resolution of the issue.
As you can see below, it is not resolved.
All of the Chromecast devices are on static assigned IP addresses in the DHCP table, they are powered on 24/7, self managing in terms of FW updates (i.e. latest versions) and all on the same network as the Roon Server. The network only has 1 WiFi Access point, and the devices are connected to the same SSID.
I understand from the investigation that a stale ChromeCast group gets created but Roon is not distinguishing this group from the active group.
Have you had a chance to test the latest release?
There was one success report for LG in production here:
I have that Build now and will observe if there is duplication of Chromecast Groups over time.
Thanks
There is still one minor glitch: while you can now use chromecast to make the TV display now playing content, the TV itself doesn’t know that the display is in use. It thinks there’s inactivity and the screensaver comes on after whatever you set it to come on by (you can’t bypass the screensaver and the maximum inactivity period is 30 minutes).
I’m creating a ticket for this issue. When I get a chance I’ll see if I can figure out how to fix this issue.
As soon as I’m clear of all the Apple 27 release stuff I think I have a patch to fix this issue too
Will this be making it to 2.74? Thanks
Not 100%, but I’ll see what I can do.
So far, it isn’t looking great at getting it into 2.74, but I’m still working on it. While testing the changes I had I’ve discovered several more issues and fixed them. So, good news & (likely) bad news.
I’ll update as I have new information.
