You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading to 0.103.0, Home-Assistant does not start. The log stops at
INFO (SyncWorker_3) [pychromecast] Querying device status
and then HA consumes 100% cpu but never finishes startup.
The chromecast device is reachable on the network and streaming works, so this may be a different problem to what has been reported before (see below). Going back to the docker image for 0.103.0 does work.
Note that I have not manually added a cast component to yaml, it was auto-discovered and added via the frontend and the only place it shows up is in core.entity_registry.
Additional information:
Similar problems have been reported a few times in the past:
Home Assistant release with the issue:
0.103.1
Last working Home Assistant release (if known):
0.103.0
Operating environment (Hass.io/Docker/Windows/etc.):
Docker on Debian Linux
Integration:
https://www.home-assistant.io/integrations/cast/
Description of problem:
After upgrading to 0.103.0, Home-Assistant does not start. The log stops at
and then HA consumes 100% cpu but never finishes startup.
The chromecast device is reachable on the network and streaming works, so this may be a different problem to what has been reported before (see below). Going back to the docker image for 0.103.0 does work.
Note that I have not manually added a
cast
component to yaml, it was auto-discovered and added via the frontend and the only place it shows up is incore.entity_registry
.Additional information:
Similar problems have been reported a few times in the past:
The text was updated successfully, but these errors were encountered: