The wake word "Hey Dicio" causes difficulties to many people, who asked to have their own custom wake word. However, to do so, you need some technical knowledge, including building your own fork which is not very convenient.
For a non-technical solution, we could offer other generic choices, like what Alexa devices do (they have 5 built-in presets, so you are not forced to use "Alexa").
To get some inspiration for presets, I had a look at this article about HomeAssistant approach about wake words.
You can see they offer many presets, from classic ones to more originals:
- alexa
- hey jarvis
- hey mycroft
- hey rhasspy
- ok nabu
- computer
- framboise
- manzana
- stachelschwein
My preference as a French would go to "Alexa", "Framboise" or "Manzana", but other language speakers may prefer others. Someone in #238 suggested "Scotty" for example.
If you can take care of generating the wake words (or re-using the ones from Home-Assistant if the license allows it?), I can make a PR (unless you want to do it yourself).
I see two ways (they don't oppose each other, so both could be implemented):
- the first way would be to have a limited list of built-in wake words. That means a new preference with a list of preset choices (with "Hey Dicio" as the default one).
- the second way would be to offer a new preference "custom wake word" and the user would import the wake word. Generated wake words would be available to download from a Wiki page or something. That would allow more choices to choose from, however I have some security concerns about file importing: is there a way to check a tflite file is sane?
The first way is more convenient for the user (no need to go to an external page, download and import) and easy to technically implement, while the second is more technically challenging but more flexible and long-term proof.
What do you think?
(Thanks for reading)
The wake word "Hey Dicio" causes difficulties to many people, who asked to have their own custom wake word. However, to do so, you need some technical knowledge, including building your own fork which is not very convenient.
For a non-technical solution, we could offer other generic choices, like what Alexa devices do (they have 5 built-in presets, so you are not forced to use "Alexa").
To get some inspiration for presets, I had a look at this article about HomeAssistant approach about wake words.
You can see they offer many presets, from classic ones to more originals:
My preference as a French would go to "Alexa", "Framboise" or "Manzana", but other language speakers may prefer others. Someone in #238 suggested "Scotty" for example.
If you can take care of generating the wake words (or re-using the ones from Home-Assistant if the license allows it?), I can make a PR (unless you want to do it yourself).
I see two ways (they don't oppose each other, so both could be implemented):
The first way is more convenient for the user (no need to go to an external page, download and import) and easy to technically implement, while the second is more technically challenging but more flexible and long-term proof.
What do you think?
(Thanks for reading)