Assist - how to use 'lists' function in custom intents

Hi, I’m very new to home assistant and making assist conversations my first project. I’ve got an intent/intent_script but have a couple of questions and I’m struggling to find any good documentation for assist. There seems to be little bits dotted everywhere, so question one have I missed a good resource for getting started with assist?

Question two, rather than build a huge configuration.yaml is there a way to add them to another folder that will be parsed like the custom_sentences/en/ is?

Question three is more specific, I’m expecting to have an issue when I start using voice and trying to head it off now. I have a binary sensor called ‘minnie’, no doubt voice will interpret this as ‘mini’ and then not find the sensor. Is lists the right approach to convert any input of ‘mini’ into ‘minnie’? I’ve tried the below code without success:

language: “en”
intents:
CatLocation:
data:

  • sentences:
  • “Where is {name}”
  • “Is {name} [at] home”
  • “Is {name} outside”
  • “Is {name} inside”
  • “Is {name} indoors”
  • “Is {name} outdoors”
  • “Is {name} [in] [the] house”
  • “Is {name} [in] [the] garden”
    lists:
    name:
    values:
  • in: “mini”
    out: “minnie”

Thanks in advance.

Depending on what you mean by “very new to home assistant”, I don’t know that I would recommend this as a first project. You’re time will probably be better spent setting these up as automations using Sentence triggers. Doing it that way will mean you learn a little about trigger variable and Jinja templating which have broader applications within HA than the specifics of voice/conversation integrations.


Some Voice/Assist Resources:

HA - User Docs:
Voice Control (Make sure to check out the 20+ links in the sidebar)
Voice-related Integrations

HA - Developer Docs:
Template Sentence Syntax
Built-In Intents

Github:
Hassil

Personally I prefer using the Packages method, as I find it less complicated and more flexible than the other methods.


Regarding Question 3:

Please format your code blocks properly as directed in Questions Guideline #11, so we can tell if the syntax is correct.

Just add alias mini for this device.
You don’t need to reassign internal variables (name, area, floor).

Your idea could be implemented in some ASR like vosk or speech-to-phrase.

Thanks, that works

Splitting the file was easier than I expected. Thanks