I’m using discovery component to detect 2 chromecast audio in a group. Home-assistant identifies 3 chromecast media instances. The 2 CC’s puls the group. The name of the individual CC’s is correct, but the group appears with the same name as one of the individual CC’s.
This also gives some problem if you want to send a stream to the group since there is no different entity_id to do so.
Thanks.
Yeah I see basically the same. The group named the same as one of the chromecasts but with _2 on the end.
If send media content to the _2 entity It does seem to work for me.
Might be worth logging it in the issue tracker: https://github.com/home-assistant/home-assistant/issues
It depends. In some cases the group appears has the name of one of the CC’s and the actual CC appears with _2.
But it works if you send the media content to the correct one.
Thanks.
Yeah… Looking at a tcpdump of the mdns traffic, it looks one of the CC’s owns the group and perhaps listens on a different port.
I guess it then gets discovered twice with the same name and whichever is found second is _2.
Definitely looks like a bug anyway. The groups are visible in mdns as “md=Google Cast Group” and the name like “fn=All Speakers” hopefully discovery can be adapted to identify them.
Huge kick, but i’m having the same issue as mentioned before. Is there a solution for this?