-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for controlling entities in an area based on a partial name #976
Comments
As a workaround you could define an alias "ceiling lights". I assume this should work, as long as you indeed only call the intent with the area as well. |
You sure about that? |
It should work, if you define an alias "alcove lights" (or in the first example "ceiling lights") for person room ceiling lights. So no support for generic entities but you can rename entities to match your needs. |
so the home assistant matching logic can match "area" "entity" as an entity name? But IMO, in should probably be suported too, if only for consistency with the other actions. And feels more natural in an english sentence to me. But that's probably out of scope of this particular issue I suppose. And I still think having some kind of partial/fuzzy matching for entities would probably be beneficial for the user experience. Assuming it doesn't perform an action on a low-confidence match I suppose. |
Partial/fuzzy matching will come later when we use the sentences from this repo to train actual machine learning models. For example: generating all possible sentences and using snips-nlu to train an English model. |
for example
entity name: person room ceiling lights
area: person room
sentence: turn on the ceiling lights in person room
I notice that at present, it expects a mostly exact match with the entity name or aliases, and this sentence form would be more natural in my opinion.
Not sure if this is the right place to be asking this though.
The text was updated successfully, but these errors were encountered: