For the KEF integration (a speaker) there are a bunch of services that can adjust settings (see this.
Settings such as
kef.set_desk_db
kef.set_wall_db
kef.set_treble_db
kef.set_high_hz
kef.set_low_hz
kef.set_sub_db
These have a fixed number of allowed options or fixed number ranges. It would be a natural option to have input_numbers, input_selects, and input_booleans for this (inputs that have a graphical representation in Lovelace).
Then, when adding an integration, one could simply add the correct entities to the UI (without having many automations) and it would look like:
So if I understand you correctly you’d like t to be able to tie these input_* directly to a service from the helper interface? I’m struggling to understand what it is you propose.
Right now, it is not allowed that integrations create input_* entities. I don’t mean that there is some helper interface, but that this is fixed at the Python code level (without requiring a user to add inputs themselves.) An integration can create a sensor for example, but for reasons I do not know, we cannot add input_*s.
Maybe I am just ignorant and there is a very good reason for this…
Ah Thanks, that makes sense! For that to work though, such an entity would also have to be tied to specific services, otherwise the user would still have to make the specific automations (or these would also have to be auto-generated).
