I see what you mean about the delay. It’s slight but I can live with it. You can create a call service for the group in an automation or script and shut them off that way.
- service: homeassistant.turn_off
entity_id: group.<device_group)I’m with you: I’d much rather have perfectly sync’d audio throughout the house. It’s just … way sexier
Well I still get the errors so not sure this is a viable workaround.
Also not sure if related but I always end up with the Client exceeded max pending messages error message:
2017-10-21 00:54:26 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140478209766232: Client exceeded max pending messages [2]: 512
2017-10-21 01:00:30 ERROR (MainThread) [homeassistant.components.websocket_api] WS 140478206615960: Client exceeded max pending messages [2]: 512
2017-10-21 03:20:46 ERROR (Thread-20) [pychromecast.socket_client] Error reading from socket.
2017-10-21 03:20:46 ERROR (Thread-19) [pychromecast.socket_client] Error reading from socket.
2017-10-21 03:20:46 ERROR (Thread-18) [pychromecast.socket_client] Error reading from socket.
2017-10-21 03:20:46 ERROR (Thread-20) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-10-21 03:20:46 ERROR (Thread-18) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-10-21 03:20:46 ERROR (Thread-19) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-10-21 03:21:19 ERROR (Thread-21) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-10-21 03:21:19 ERROR (Thread-23) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-10-21 03:21:23 ERROR (Thread-22) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-10-21 03:50:58 ERROR (Thread-30) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-10-21 03:50:58 ERROR (Thread-32) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-10-21 03:50:58 ERROR (Thread-31) [pychromecast.socket_client] Failed to connect, retrying in 5.0sI always had these kind of errors when the wifi connection to one of my chromecasts in the “whole_house” group was instabile. Meaning when the chromecast reconnected Hass “create” another “whole_house” group. Since I moved the chromecast a bit closer to the Router its running like a charm for about 3 months now. Maybe this applies to your problem as well.
actually I have to revert to CC groups. the gap in sync eventually gets so bad that it can be several seconds apart. Would really like a fix now…
Any news on a fix for this?
I can’t wait speak for everyone else, and hopefully I’m not tempting fate, but I haven’t had any issues with chromecast for the last few updates.
I’m on 0.61.1 and still get these issues… 
sorry to bump this, but on 81.6 we’ still seeing this:
2018-11-21 22:07:46 ERROR (Thread-3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
simply because I powered down my tv to which the chromecast is connected… Is anyone aware of an attempt to finally solve this?
not really sure about that:
is your Chromecast discovered or manually added to your config?
If manually added, it makes sense that if the CC is not powered it doesn’t respond. HA looks for it but can’t find it.
Or am I missing something?
I am also getting the same errors every day. They come in batches at the same time. I assume for each Google home speaker. Mine are auto detected and not manually configured
I have 3 casts, 1 audio and 2 regular . Discovered and displayed on the integration page as Google Cast: Google cast.
Used to have set cast: in the configuration files but taken that out since the new integration feature.