-
-
Notifications
You must be signed in to change notification settings - Fork 31.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cast MediaPlayers go to Unavailable after a while #16924
Comments
Duplicate as #16686 |
Sorry, I did search honest! |
Hi CheeseySandal Did version 0.79 fix your problem? Because for me it did not. My chromecasts still become unavailable for a while. |
It did I'm afraid. |
@nelbs please open a new issue for your case. Chromecast component is complex, the previous fix only address particular configuration. When you open the issue, please provide your debug log, config, and what type of Chromecast device involved. Chromecast, Google Home, or Smart TV, etc. |
Home Assistant release with the issue:
0.78.3
Last working Home Assistant release (if known):
0.77.x (I think)
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio on RP3
hassOS 1.10 & hassOS 1.11
Component/platform:
cast
Description of problem:
After a couple of days, mediaplayer become unavailable.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
I have 7 google casts in the house (1x home, 2x mini, 2x audio, 2x chromecasts) and they're shown in my frontend. I've always had reading from socket errors in the logs, but it's occasional and it always resolved itself after a while.
Since updating to 0.78.x after a couple of days, my mediaplayers will eventually come up as Unavailable and stay like that. All automations around the media players never fire (e.g. automatic sleep timers fail and podcasts are played all night!).
A reboot fixes the issue, but only for a couple of days.
The text was updated successfully, but these errors were encountered: