Help with chromecast configuration : unamed_device

Configuration
1

Hi everyone,

I have an issue with my home assistant configuration.

I decided to disable discovery in my configuration.xml file. Mainly in order to be in control of what appears and what is used. So far so good, everythink works well, except for my chromecast.

I declared my two google casts that way:

cast:
  media_player:
    - host: 192.168.0.135
    - host: 192.168.0.136

If I start Home assistant with the chromecast on and accessible, it is perfect. Its entity id is media_player.chromecast_salon.

But if I start home assistant with the chromecast off, then its entity_id is media_player.unnamed_device.

It could not be an issue, but when I switch the chromecast on, its entity_id remains media_player.unnamed_device, and its status is always Off.

Am I missing something ? Is there a way to refresh it status, after all it is still the same IP address.

I did not find more information in the documentation.

The google mini is always on, so there is no cast problem there.

Thank you in advance, any help will be appreciated.

2

I had problems detecting my CC group and a CC that HA decided to give it another name. The only thing that solved my issues was let HA to discovery them. It may work for you. Before, I declared them in configuration, as you did.

3

Thank you for your answer.

What I just tried was to remove my cast declaration in the configuration.yaml, and all the existing entities.

After a restart, I used the integration gui to add the casts. And now it works.

I presume if i set the cast in the configuration file, it will try to set them on startup. And as the cast is not available, it can not get its name, and the entity_id is wrong.
But if I use the integration, the entity_id is already there, and it just flag its state as false.

4

I am glad that it worked for you too… :slight_smile:

1 Like
5

I am having the same issue with Chromecasts. It looks like defining cast in the config file breaks chromecast discovery. For more information check out this issue I opened:

Since googling my problem led me here I just want to confirm that a fix for now is to use discovery and not define the Chromecast’s in the config file. Users that have their chromecast on another subnet will not be able to use this fix though and will have to wait for this bug to be fixed.

1 Like