YAML Configuration option to hide entity (programmatically implementing new UI supported feature from 2022.4)

Feature Requests
1

Please read before closing this as potentially irrelevant, or workaround present, as I think this has much broader applications then the workaround I am attempting to use it for in my description below.

Yes in a perfect world this PERHAPS might not be needed but an intellectually pure programing model often makes for (un/less) usable products, something I debated many times with Avie durning my time at Apple, but I digress.

I have an integration that doesn’t produce a unique entityID (Onkyo integration). The integration is rather generic in the device it produces with more output zones than physically exist on the model I have. (ie - media_player.onkyo_receiver_zone_3)

I would like to hide the spurious output zone(s) in Lovelace as I do with other entities, which I of course can not do using the new UI hide function in 2022.4 (not uniqueID).

This lead me to the potential to modify using the configure entity override in the Home Assistant YAML config. Customizing Entities with YAML config The documentation leads one to assume this is the place one might LOGICALLY declare a given entry should be hidden IF the functionality were supported. As stated above since the release of 2022.4 the functionality does now exist but of corse doesn’t support UI modifications to non-unique entries, this would seem a reasonable and consistent feature/function to addition to the Customizing Entities YAML.

Again I know there other options (go manual rather then use auto-generated dashboard), live with the spurious field in the generated dashboard, however I suspect there are many out there who have similar situations where they have devices that do not have generated uniqueIDs for given entities/devices and may wish to modify not only the name/icon/stating_state of a device but for completeness with the current version of Home Assistant ALSO exist it’s disability.

Thanks for your consideration…
Tom

2

The problem with that… is that if there is no unique ID, it can’t be registered in the registry, and without that we don’t have a registry item to mark as hidden (because its not the entity that is hidden, its the registry entry that is marked as hidden).

Every integration can provide an unique ID (like all of them), but it needs to be added to the integration.

So, IMHO the best solution is not to work around / find solution on how to make it work for things without a unique ID. Instead, the integration needs to be updated to have a unique ID! (which unlocks lots of more functionality).

3

Thanks for the speedy response!

Then I guess I should open a PR for the standard Onkyo Integration though I did look into that first but since it was integrated into HA core there has been no activity and several other filed bugs about extraneous zones have been closed due to inactivity. HA Core - Onkyo integration issues

Unfortunately (as you can tell from the PR I filed) I am still learning about the internals of HA and the why things are the way they are so I’m able to dig into the source for the integration and push an update for the component. Any sugestions?