I have many large input_select entities and it would be great to be able to have at leats two additional services to set and clear a filter that would filter the options or better it should be built into the widget.
Here is one use case.
An input select populated from a local JSON file with 5000+ music artists. Here is a view of how it looks:
Now I do know that I can type one letter and jump to say “Z”.
I would much rather type into some input_text something like "John*"and reduce the list to only that. I am sure there are many more use cases for “something” or just “west” and give me any item with “west” in it. This is very common in usuable interfaces especially when lists can get large,
I suppose I could do this:
Create two lists
Populate the first list with everything
Then have a filter widget that you type in the filter and an automation to filter the first list to the second and populate the second one.
so instead of having:
music_artist_list (supporting filtering)
I have to have:
music_artist_list_all
a text_input for the filter (that updates when it is typed into which is whole different bug as they do not update)
an automation
music_artist_list_filtered
Seems prone to issues, plus delays in updates etc. when in-situ filtering should be supported. Especially in a house with two PCs. 6 phones, 5 wallpads that all access HA.
The context sensitive selection of entities supports this, why not the core helper widgets?