Home assistant has a consistent UI for exposing entities to Google Home, and to Alexa, but is inconsistent in how it applies to “Siri” (HomeKit)
I would love to see a default HomeKit controller setup and exposing to HomeKit via this interface, as making things available to Siri is really bad UX at the moment - especially as it doesn’t support the entity selection style as available in things like automations - it’s just a massive multi select
HomeKit controller does not “expose” any entities to Apple Home (the ecosystem formerly known as HomeKit), perhaps you’re thinking of HomeKit bridge?
The HomeKit Bridge config is desperately in need of improvement, but there is already at least one FR addressing that.
Edited to add: upon further consideration, this proposal has some merit. HomeKit Bridge is inconsistent, not only with the other ecosystem bridges (e.g. Google Home and Alexa) but with other integrations (it provides no new entities or services). It also causes confusion about the difference between “bridge” and device/controller when together on the Integrations list. Furthermore, HomeKit isn’t even the name of the ecosystem anymore, it’s only one of the protocols used by Apple Home ecosystem. Of course, Apple Home is more than Siri (same wrt Google) so renaming “Voice Assistants” to “Assistants and Bridges” might be less confusing, while providing them all a superior “expose” UX. My last request is a method to do per-entity configuration which can only be done in YAML for HomeKit bridge today. You got my vote.