core: Chromecast entity wont show up unless powered on when HA starts when using config instead of discovery

Home Assistant release with the issue:

Running latest as of posting. 0.100.3

Last working Home Assistant release (if known): Unknown. I know it worked some months ago but then a HA update broke it. I think it was the change from a component to an integration that broke it but I am not 100% sure on this.

Operating environment (Hass.io/Docker/Windows/etc.):

Running in docker container on an Unraid system.

Integration:

https://www.home-assistant.io/integrations/cast/

Description of problem: Whenever I update Home Assistant or restart it I have to make sure all of my chromecast devices are powered up and available otherwise they will not show up in HA even when they get powered on.

When I look for the entity in the states list in the UI the entity does not exist in that list if the device was un-powered when home assistant started up.

All of my chromecast devices are plugged into TV’s USB ports and only powered when the TV is turned on. I guess I could just have them always powered but that is a waste of electricity so I prefer this option.

This is really strange as it used to work perfectly. Something changed in the last couple months that caused it to stop working the way I want. I think it may have been when cast was moved into it’s own component. It used to continually try to connect to the chromecast (would show up in log) but now it looks like it only tries once and gives up. Here is the single log row:

Wed Oct 23 2019 01:18:39 GMT-0600 (Mountain Daylight Time)
[192.168.1.30:8009] Failed to connect, retrying in 5.0s

When I powered on the chromecast after HA started nothing happened (no messages in log).

Problem-relevant configuration.yaml entries: Casts manually configured:

cast:
  media_player:
    - host: 192.168.1.10

Traceback (if applicable):

Additional information: