#HassTurnOn extension for voice satellites with area

1 messages · Page 1 of 1 (latest)

drowsy mirage
#

Prerequisites:
I want to have aliases for my devices, that can repeat in every room (e.g. "Fan", "Top light", "Mood light", "Purifier" etc.
Then i could use simple phrases on my voice satellites to turn them on/off.
HassTurnOn has name_area type of call. So i extended it like this:

HassTurnOn:
    data:
      - sentences:
        - "<turn> on [the] <name>"
        - "<turn> [the] <name> on"
        slots:
          domain: "light"
        requires_context:
          area:
            slot: true

This works perfectly fine for cases i made.
However, because in this case the sentence is the same as for name only, it basically discards the calls to every other device. So i can't turn on anything that isn't in same area that my satellite is in. Same commands from phone or web are working good, since they don't have area.

So i believe HassTurnOn intent script itself should be changed to respect optional area, when only name was called, and there are duplicates.

drowsy mirage
#

@tidal wave @pastel dew sorry for tagging - don't want it to be lost, since i believe it's important.

drowsy mirage
#

I guess i'll have to fork HA and make this myself. Knowing how long that PRs from non-owners are hanging there, it will take some time. 🙂

pastel dew
#

i understand what the issue is. you don't have to fork HA, though. well, you do, but only to add a PR
can you please first raise an issue describing the behavior and then link to a PR fixing it? i think the solution is to also try (as a fallback) matching without sending the satellite area, in case matching with the satellite area does not work

#

until then, i'm fairly certain that you can control your devices by adding the <area> in your uttered sentence (e.g. turn on the TV in the kitchen, where kitchen is another area than where the satellite is)

#

btw, even my own PRs to the core take months to get merged (if at all) 🙂

drowsy mirage
#

@pastel dew thank you for thorough explanation. 🙂
One question: should I raise issue, or feature request?

pastel dew
#

it sounds more like an issue, imho