You could use the entity_namespace: option in the new one to differentiate the naming if it is supported. I don’t have any Apple devices so I can’t say for sure, but I am using it with other media players.
Ok, then is plex probably the other one. You can specify a name tag as well to rename the device (for the Apple TV platform at least). If you don’t want the plex instance, I guess you have to disable it somehow. How you configured that manually too?
Yes, it was just the old media_player.apple_tv showing. Not the new one.
I now have two entries again
But the first one is now the new platform, the second is the old one. So my automations work with the new platform and richer data. Which is good I now want to stop media_player.apple_tv_2 being discovered. I think that is my UniFi device tracker. My Apple TV connects via WiFi and UniFi just sees it and HA creates a record for it.
Ok, that seems a bit strange to me that UniFi would do that. I could understand if it discovered it as a device and created device_tracker.apple_tv. Can you try to disable plex, discovery and apple_tv and see if it still is there? We should probably single out the source.
The solution I offered was simply to allow you to differentiate between the two so you knew which one to display. You didn’t mention about wanting to remove it from dev states. As long the name is different so that you now know which one to include in automation, I don’t really see the problem because as long as you don’t include it in a group or view, you’ll never see it.
This is likely due to some discovery and is a topic we’re discussing in this thread that you might be interested in:
I’m having similar issues because I am testing new components for devs for stuff that will be coming up in the next release. Since some of them are either improvements on existing platforms or in the case of Ring doorbells, taking a device supported in one platform and supporting it directly, I run into the issue of trying to figure out which sensor/device is the released version and which one is the test.
entity_namespace has been a big help in this. Discovery on the other hand has not, as I am sure you know… LOL