Skip to main content

Template Sentence Syntax

Template sentences are defined in YAML files using the format of Hassil, our template matcher. Our template sentences are stored on GitHub and are organized by having for each language a directory of files in sentences/<language>/:

  • _common.yaml - Lists, expansion rules and skip words to be used across all template sentences.
  • <domain>_<intent>.yaml - Template sentences for a single intent and domain.

Besides the data in _common.yaml, template sentences can also use the lists name and area. These lists are made available by Home Assistant during intent recognition.

# Example light_HassTurnOn.yaml
language: "en"
intents:
  HassTurnOn:  # Intent name
    data:
      - sentences:
          - "<turn> on [all] [the] (light | lights) in [the] {area}"
          - "<turn> on [all] [the] {area} (light | lights)"
          - "<turn> [all] [the] (light | lights) in [the] {area} on"
        # Optional; used to set fixed slot values when the intent is matched
        slots:
          domain: "light"

The above example will match the sentence turn on all the lights in the living room to the intent HassTurnOn and extract the area living room. The domain value is set to light. In Home Assistant, when the intent is executed, it will turn on all entities of type light in the area living room.

Responses​

A sentence template file may contain a response "key" for a group of sentences:

# Example light_HassLightSet.yaml
language: "en"
intents:
  HassTurnOn:
    data:
      - sentences:
          - "set {name} brightness to maximum"
        slots:
          brightness: 100
        response: "brightness"

In the example above, the response key "brightness" refers to a template inside the file responses/en/HassLightSet.yaml:

language: en
responses:
  intents:
    HassLightSet:
      brightness: '{{ slots.name }} brightness set to {{ slots.brightness }}'

If no response key is provided, then "default" is assumed.

Response templates uses Jinja2 syntax and may refer to the slots object whose attributes are the matched intent's slot values.

See all translated responses for more examples.

Sentence Templates Syntax​

  • Alternative word, phrases, or parts of a word
    • (red | green | blue)
    • turn(ed | ing)
  • Optional word, phrases, or parts of a word
    • [the]
    • [this | that]
    • light[s]
  • Slot Lists
    • {list_name}
    • {list_name:slot_name} (if intent slot is named different)
    • Every value of the list is a different option
    • In YAML, list_name should be under lists
    • Use values for text lists, range for numeric lists
  • Expansion Rules
    • <rule_name>
    • The body of the rule is substituted for <rule_name>
    • In YAML, rule_name should be under expansion_rules. If the rule_name wraps a slot name, it should match the slot name. Otherwise it should be in the native language.

The common file​

The common file _common.yaml contains lists, expansion rules, and skip words that are used across template sentences for all intents and domains.

Lists​

Lists are possible values for a slot. Slots are data that we want to extract from a sentence. For example, we can make a list color to match possible colors.

lists:
  color:
    values:
      - "white"
      - "red"
      - "orange"

Intent handlers in Home Assistant expect color to be defined in English. To allow other languages to define colors, lists support the in-out format. This allows you to define a list of values in the native language, but the intent handler will receive the values in English.

lists:
  color:
    values:
      - in: "rood"
        out: "red"
      - in: "oranje"
        out: "orange"

A list can also be a range of numbers. This is useful for defining a range of brightness values or temperature that you want to match.

lists:
  brightness:
    range:
      type: "percentage"
      from: 0
      to: 100

Specific numbers can also be matched by a list, like returning 100 from the keyword maximum. To use this list to set the brightness in a sentence, use the following syntax: {brightness_level:brightness}. This will get the value from the list but put it in the slot for brightness. 

lists:
  brightness_level:
    values:
      - in: (max | maximum | highest)
        out: 100
      - in: ( minimum | lowest)
        out: 1

Wildcards​

Wildcard lists can match any text, for example:

language: en
intents:
  PlayAlbum:
    data:
      - sentences:
          - play {album} by {artist}
lists:
  artist:
    wildcard: true
  album:
    wildcard: true

will match sentences such as "play the white album by the beatles". The PlayAlbum intent will have an album slot with "the white album " (note the trailing whitespace) and an artist slot with "the beatles".

Local lists​

Sometimes you don't need a slot list available for all intents and sentences, so you can define one locally, making it usable only in the context of the intent data (like a collection of sentences) where it was defined. For example:

language: en
intents:
  AddListItem:
    data:
      - sentences:
          - add {item} to [my] shopping list
        lists:
          item:
            wildcard: true

Expansion Rules​

A lot of template sentences can be written in a similar way. To avoid having to repeat the same matching structure multiple times, we can define expansion rules. For example, a user might add "the" in front of the area name, or they might not. We can define an expansion rule to match both cases.

Expansion rules can contain slots, lists, and other expansion rules.

expansion_rules:
  name: "[the] {name}"
  area: "[the] {area}"
  what_is: "(what's | whats | what is)"
  brightness: "{brightness} [percent]"
  turn: "(turn | switch)"

Local Expansion Rules​

Expansion rules can also be defined locally next to a list of sentences, and will only be available within those templates. This allows you to write similar templates for different situations. For example:

language: en
intents:
  GetLocked:
    data:
      - sentences:
          - is the door <state>
        requires_context:
          domain: binary_sensor
        expansion_rules:
          state: "{binary_state}"

      - sentences:
          - is the door <state>
        requires_context:
          domain: lock
        expansion_rules:
          state: "{lock_state}"

lists:
  binary_state:
    values:
      - in: "locked"
        out: "off"
      - in: "unlocked"
        out: "on"
  lock_state:
    values:
      - "locked"
      - "unlocked"

The same template is the door <state> is used for both binary sensors and regular locks, but the local state expansion rules refer to different lists.

Skip Words​

Skip words are words that the intent recognizer will skip during recognition. This is useful for words that are not part of the intent, but are commonly used in sentences. For example, a user might use the word "please" in a sentence, but it is not part of the intent.

skip_words:
  - "please"
  - "can you"

Requires/Excludes Context​

Hassil returns the first intent match it can find, so additional context may be required if the same sentence could produce multiple matches.

For example, consider the following template:

language: "en"
intents:
  HassLightSet:
    data:
      - sentences:
          - "set {name} brightness to maximum"
          - "set {area} brightness to maximum"
        slots:
          brightness: 100

If you have an entity named "kitchen light", then you will be able to say "set kitchen light brightness to maximum". Similarly, "set kitchen brightness to maximum" will work if you have an area named "kitchen".

But what if you have a media player named "kitchen"? The same sentence could match either the area or the media player. Hassil will require more context to know what to do:

language: "en"
intents:
  HassLightSet:
    data:
      - sentences:
          - "set {name} brightness to maximum"
        requires_context:
          domain: "light"
        slots:
          brightness: 100
      - sentences:
          - "set {area} brightness to maximum"
        slots:
          brightness: 100

We've split the sentences into two groups. The first group is for individual entities, and now has requires_context with a domain of light. This ensures that Hassil will only produce a match if the entity from {name} has the correct domain. Since areas do not have domains, we need to move the {area} sentence to its own group.

Context is also useful if you want to want different responses within the same intent:

language: "en"
intents:
  HassTurnOn:
    data:
      - sentences:
          - "activate {name}"
        excludes_context:
          domain: "cover"
        response: "default"
      - sentences:
          - "activate {name}"
        requires_context:
          domain: "cover"
        response: "cover"

The first sentence group uses excludes_context to skip over cover entities, while the second group specifically matches cover entities and uses a different response.