Every night home assistant (docker) crashes due to Chromecast issue

[gvdhoven]

The problem

Every night my home assistant docker install (latest version) crashes due to issues with Chromecast. Therefore none of my automations work in the morning, which is starting to irritate my wife ;)

I think that (a) py-chromecast should not give errors but warnings when it fails to connect and (b) that one single part of Home-assistant should not be able to bring down the service - or increase the retry-delay and only fail after 10 attempts or something. 5 seconds is a bit short.

I do wonder however if this is related to Home assistant or not, but since HA is affected by it, i wanted to report here at first.

What version of Home Assistant Core has the issue?

2025.1.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Chromecast

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2025-01-12 02:02:57.510 ERROR (Thread-8) [pychromecast.socket_client] [...(192.168.1.43):8009] Error reading from socket: socket connection broken

2025-01-12 02:19:09.641 ERROR (Thread-4) [pychromecast.socket_client] ...(192.168.1.41):8009] Error reading from socket: socket connection broken

2025-01-12 02:19:09.677 ERROR (Thread-4) [pychromecast.socket_client] ...(192.168.1.41):8009] Failed to connect to service HostServiceInfo(host='192.168.1.41', port=8009), retrying in 5.0s

2025-01-12 03:38:14.293 ERROR (Thread-5) [pychromecast.socket_client] [...(192.168.1.53):8009] Failed to connect to service HostServiceInfo(host='192.168.1.53', port=8009), retrying in 5.0s

2025-01-12 03:38:15.599 ERROR (Thread-11) [pychromecast.socket_client] [...(192.168.1.52):32128] Error reading from socket: socket connection broken

2025-01-12 03:38:15.645 ERROR (Thread-11) [pychromecast.socket_client] [...(192.168.1.52):32128] Failed to connect to service HostServiceInfo(host='192.168.1.52', port=32128), retrying in 5.0s

2025-01-12 04:11:23.297 ERROR (Thread-7) [pychromecast.socket_client] [...(192.168.1.46):8009] Failed to connect to service HostServiceInfo(host='192.168.1.46', port=8009), retrying in 5.0s

2025-01-12 04:17:43.146 ERROR (Thread-9) [pychromecast.socket_client] [...(192.168.1.50):8009] Error reading from socket: socket connection broken

2025-01-12 04:17:43.203 ERROR (Thread-9) [pychromecast.socket_client] [...(192.168.1.50):8009] Failed to connect to service HostServiceInfo(host='192.168.1.50', port=8009), retrying in 5.0s

2025-01-12 04:32:44.160 ERROR (Thread-10) [pychromecast.socket_client] [...([::ffff:c0a8:134]):8009] Failed to connect to service HostServiceInfo(host='[::ffff:c0a8:134]', port=8009), retrying in 5.0s

2025-01-12 04:37:39.414 ERROR (Thread-6) [pychromecast.socket_client] [...(192.168.1.47):8009] Failed to connect to service HostServiceInfo(host='192.168.1.47', port=8009), retrying in 5.0s

Additional information

No response

[HereticBG]

Same issue here on Home Assistant OS. HA would become unresponsive nightly (not responding to pings, not letting me access it) until I reboot it by unplugging it. Looking at the logs after reboot, I always see the same errors regarding my Chromecasts failing to connect to HostServiceInfo.

Going to disable Google Cast integration for now to see if it helps.

[gvdhoven]

Any updates on this? Updated yesterday to latest dev container, same issue.

[vjenne]

Yes same problem here!