core: HA loses connection to chrome cast and does not reconnect
Description of problem: Several users report that HA loses connection to chrome cast and does not manage to reconnect until HA is restarted. Unfortunately, this is not possible to debug without logs.
If you have this problem, please help by
- Enable debug logging for the cast integration and its dependencies:
Logger options in
configuration.yamllogger: default: info logs: homeassistant.components.cast: debug homeassistant.components.cast.media_player: debug pychromecast: debug pychromecast.discovery: debug pychromecast.socket_client: debug zeroconf: debug - When the issue is reproduced:
a. Use the Google home app to verify that the Google home app can reach each cast to which the connection is lost, and also confirm the IP address of each disconnected cast (found at the end of the device settings menu in the Google Home App). Note the time and confirmed IP address. Please note that sharing of private IP addresses such as 192.168.x.x or 10.x.x.x is not an issues as those IPs are only accessible within your own network.
b. Restart HA to recover connection to the cast
c. Add a comment to this issue including:
- The time at which connection to the casts is lost
- The name of the casts that are turned on but can’t be connected to by HA
- The IP addresses manually checked for each failing cast, and the time of checking
- A complete HA log - from start of HA until connection is lost and HA is restarted and the connections to the casts are reestablished. The log can be uploaded to https://gist.github.com/ or similar service, or attached as a file.
- Describe if you have manually configured the casts in
configuration.yamlor if the casts have been discovered.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 2
- Comments: 70 (23 by maintainers)
I also have the same problem, since a looong time ago, thats my only errors in the log. I have tried both with the integration and the media_player: in configuration.yaml. It can dissapear for some hours, but then it goes on again.
I’m also having these errors in log. Nothing has changed in my network setup, just update Home Assistant to 0.104.2
ERROR (Thread-36) [pychromecast.socket_client] [record[a,in-unique,*********-0da7-df86-b52356bf7c3d.local.]=120/119,192.168.1.11:8009] Failed to connect, retrying in 5.0sThis is happening to me quite a bit (I just rebooted so that’s why my numbers are low, normally they are much much higher). I’m on HassOS 0.101.3
[MIBOX3:8009] Failed to connect to service MIBOX3-60460d34b20bf3d0fb2ce51e8f105b81._googlecast._tcp.local., retrying in 5.0s 9:34 PM /usr/local/lib/python3.7/site-packages/pychromecast/socket_client.py (ERROR) - message first occurred at 9:27 PM and shows up 3 times [ MIBOX3:8009] Heartbeat timeout, resetting connection 9:33 PM /usr/local/lib/python3.7/site-packages/pychromecast/socket_client.py (WARNING) - message first occurred at 9:27 PM and shows up 5 times
k upgraded to 92.2 and I don’t lose connectivity to the speakers/hubs. Still see disconnects in the logs though.
2019-05-10 11:39:09 ERROR (Thread-15) [pychromecast.socket_client] [Soundbar Speaker:8009] Failed to connect to service Chromecast-Audio-d79e7a5247f2c03411d4945d28aaedbc._googlecast._tcp.local., retrying in 5.0s
@ttaidapos Having the exact same issue, but only a global disconnect of Google devices. My Hue bridges (2), do not disconnect. All devices recover themselves and are usable. Not running tts.
looks like it’s working, file size doubled original after 20min. Original was running for more than a week. Hopefully it doesn’t take long so it will be less garbage for you to sort through. Appreciate the help here!