I’m confused by the different elements of HA’s voice assistant sentences.
-
What’s the difference between a
conversation
and anintent_script
? Per HA’s custom sentence example, aconversation
has anintents
sub-element, and anintent_script
doesn’t. Does aconversation
’sintent
merely declare the element that will respond to the sentence, while anintent_script
is purely the response (i.e., does anintents
point to anintent_script
)? -
HA then explains that while the example above defined the
conversation
andintent_script
inconfiguration.yaml
, you can also defineintents
inconfig/custom_sentences/
. Should you use both of these methods simultaneously or will it cause conflict or degrade performance? I wouldn’t think you should define the same sentence in both places, but the data structure for their 2 examples are different - is 1 better than the other?
In configuration.yaml
:
conversation:
intents:
YearOfVoice:
- "how is the year of voice going"
In config/custom_sentences/en
:
intents:
SetVolume:
data:
- sentences:
- "(set|change) {media_player} volume to {volume} [percent]"
- "(set|change) [the] volume for {media_player} to {volume} [percent]"
- Then they say
responses
for existing intents can be customized as well inconfig/custom_sentences/
. What’s the difference between aresponse
and anintent_script
? It seems likeintent_script
can only be defined inconfiguration.yaml
andresponses
can only be defined in config/custom_sentences/` - is that right?
Thanks for any clarification you can share.
Thanks for all that info, @RandomLegend@lemmy.dbzer0.com!
Currently I’m running HA on a mini-pc with a celeron CPU with some Atom Echos around the house, and it takes 15-30 seconds for HA to respond to a voice command. I have a server with a GeForce 4060Ti (8GB) so I’m going to try to install whisper on it and direct HA to use that whisper service, hopefully reducing the response time to something reasonable. I don’t use Portainer but I think I’ll be able to figure out how to build the images and customize the
docker-compose.yaml
, thanks to your info.Oh my that 4060Ti will reduce the response time to the bare minimum that whisper is capable of i am sure!
You don’t have to customize the docker-compose at all. That’s the plug’n’play part. You have to make sure to build the docker image so it uses the makefile and the run.sh file.
Also make sure your docker environment is able to use the 4060Ti.
Easiest way is to run
docker run -it --rm --gpus all ubuntu nvidia-smi
and see if you get a proper nvidia-smi