core: Cast Devices Unavailable - 0.78
Home Assistant release with the issue: 0.78
Last working Home Assistant release (if known): 0.77.3
Operating environment (Hass.io/Docker/Windows/etc.): Docker
Component/platform: Cast
Description of problem: Not 100% sure but after https://github.com/home-assistant/home-assistant/pull/16471, almost all of my cast devices go unavailable in a very short period of time.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Traceback (if applicable): No Traceback. Cast devices just drop off and will not become available until an HA restart.
Additional information:
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 60 (32 by maintainers)
Agreed. I just wanted to point out that “revert that damn PR and never touch the code again” is also not a good option.
No, I already tried that. It just doesn’t reconnect, that’s all. Still bad enough though…
@awarecan, probably you could raise a new PR for 78.1 to revert #16471 and then try to find a solution that solves all issues?
EDIT: If you need a tester, try me - I run 7 CC devices of different kinds.
I am going to reopen this issue. For the users still experienced disconnection issue after 0.78.1, please post your cast config and debug log.
In current implementation, the re-connection feature rely on an “internal-discovery” function, which is not depends on the general discovery components. However, this “internal-discovery” function would not be enabled for the scenario
castplatform configuration methodhostconfig, see: https://www.home-assistant.io/components/cast/#advanced-useSo, I am not going to fix scenario (1) since it is deprecated (although it may be fixed as side effect of fix scenario 2). I will try to fix scenario (2) by extend “internal-discovery” to support
hostconfig.I hope you can help to provide more information to confirm my findings.
Can confirm same cast issue, I’ve manually edited my cast.py until a fix with the connection retry limit is found.
Hi. Same here, all devices unavailable and no spoken notification…
Thanks @edif30! It’s from 0.78. I managed to get all my casting devices back on by wiping and resorting my hassio instance with a backup I had from 0.78.0b0. Also I restarted my router to refresh all IP addresses. I hope the issue doesn’t come back again after they go offline. Thanks for taking time to respond anyway. Cheers
@awarecan <=0.77.3 I can unplug all of my cast devices while HA is running, see them go offline, restart HA and HA starts up just fine. I can also stop HA, unplug all cast devices, start HA and HA starts up just fine. #14956 is an edge case.
@awarecan thats not true, I have devices offline that reconnect just fine and do not block HA start up. I think we should revert the change and start over and submit once you have a sufficient amount of testers.