[pychromecast.socket_client] Failed to connect, retrying

Can someone please try debug this - running home-assistant in docker.

Made no changes - but just restarted the docker container.

I now get the following:
2018-08-03 16:30:29 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=107 from 2018-08-03 14:29:24.485346)
2018-08-03 16:30:31 ERROR (SyncWorker_8) [pychromecast.socket_client] Failed to connect, retrying in 5.0s

I have disabled everything I can think of in the configuration.yaml file - and still get the above.

I’ve deleted and recreated the docker container - nothing works?

It looks as if it has something to do with the Google Home / Cast devices - but I’ve disabled them where ever I can find them, including entity_registry.yaml

This is highly frustrating - I have now unplugged all cast devices - deleted the entity file - now its empty… and this is all I get:
2018-08-03 17:01:07 DEBUG (SyncWorker_3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-08-03 17:01:12 DEBUG (SyncWorker_3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-08-03 17:01:17 DEBUG (SyncWorker_3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-08-03 17:01:22 DEBUG (SyncWorker_3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-08-03 17:01:27 DEBUG (SyncWorker_3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-08-03 17:01:32 DEBUG (SyncWorker_3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-08-03 17:01:37 DEBUG (SyncWorker_3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-08-03 17:01:42 DEBUG (SyncWorker_3) [pychromecast.socket_client] Failed to connect, retrying in 5.0s

getting this to, and my db file is growing like crazy ( its over 18gig in less then 20h)

Mine eventually started up - had to literally shutdown every single device on my network, took about two hours.

I couldn’t even get it started with a new installation’s configuration.yaml file.

what version? if you revert to 69.1 does it stop?

This morning home-assistant won’t start up again - same error.

Tried rolling back the version - doesn’t help.

So now I probably have to shutdown my entire network again. Joy.

Looks like its specific to the Chromecast Ultra’s - if they’re on the network, HA doesn’t start up periodically. I have two, unplugged them - and HA starts up.

i’m also having this issue :frowning: ERROR (SyncWorker_8) [pychromecast.socket_client] Failed to connect, retrying in 5.0s

i have one chrome cast ultra on the network, will now disable it and give it a go.

OMG!!! it was my chrome cast ultra that was causing the Home Assistant UI not to load up. Turned it off, restarted HA and all is working well.

Thanks all, hope there will be a fix for this.

I have the same issue even fresh install and HA UI won’t load too.

I suspect the Ultra issue becomes a problem when upgrades are triggered - haven’t tested it yet though, but I’ve noticed I’m usually able to restart successfully, and then near to when I do an upgrade/downgrade, HA won’t come online with the Ultra’s on the network.

I seem to be having this issue also, now on 0.75.3. I can’t restart HA with my android TV on, or else the UI won’t load at all.

has anyone figured out what the problem is please? I am getting the same error and the webui won’t load up, but I only have a Google Home Mini at home… and one interesting thing is if I add this into my config

cast:
media_player:
- host: 192.168.XXX.XXX # Google Home Mini.

then it seems to HA seems to startup just fine.
but then it keeps tracing the below in the log
[homeassistant.components.media_player] Platform cast not ready yet. Retrying in 90 seconds.

I also believe this started to happen after some update to the google mini few days ago as well.

actually while typing this, I noticed if I go to Hassio UI - > “Configuration” -> Integrations -> Google Cast -> the trash can to delete it. then I don’t have any problem with restarting my HA anymore…

I have the same issue and I only have minis and google home/hub. Did you ever get this solved?

1 Like

Same issue here, no news on this?