Receiver with Chromecast built in detected as two devices

Configuration
1

Hey everyone. I have an interesting problem after upgrading from 0.64 to 0.67.1:

I have a Pioneer receiver that has “Chromecast built in” functionality. I used to configure it for controlling the receiver itself and just ignore the chromecast part of it, but with 0.67, it seems to be automatically detecting the chromecast as well as the receiver, even though I don’t have discovery turned on.

That’s all well and good, but it screwed up all my automations because the chromecast became [EntryID] while the previously configured receiver has now become [EntryID]_2. I can always add _2 to all my existing automations, but I’m not sure if the built-in chromecast will always be the device that gets detected first. Is this deterministic?

I’m not sure how to differentiate the two devices, as they have the same IP; they’re physically the same device, and I had previously tried to avoid exposing the built-in chromecast to HA.

Any suggestions?

2

Answered my own question. I was able to rename the Chromecast entity_id in the entity_registry.yaml file.

3

I have a simlar issue with my TV. So did you change the two entities over? or force them into one entity name?

4

I had previously configured the receiver entity with the device’s IP… The Chromecast entity only showed up after I upgraded to 0.67.1, so I just renamed the Chromecast entity and left the receiver entity as it was.