-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wake word selection does not change if updated in home assistant's Assist configuration #107
Comments
The satellite can be configured as one (and only one) of the 3 following types (depending on parameters in the command line):
For 1 and 2, wake word is configured in Home Assistant as per your screenshot. Regarding your points:
|
@llluis Ahh I see I appreciate the clear feedback, thank you! At some point I got it responding to multiple wakewords.. not sure how to reproduce it at this point though. I'll post steps if I figure it out. My goal is to have #2 VAD. However, passing "--vad" in as a parameter for Docker results in some issues. Note, these issues do not occur if I do not pass this "--vad" parameter. Any idea what could be causing that? Do I even need to pass in "--vad" if I'm supplying a "--wake-uri" already? This is running on a pi 4. |
If you want to have VAD, you must supply I never ran it in Docker, but I see in your log you seem to be missing the silerovad requirement.
If it works, there will be some rework to be done in the setup script to correct everything. |
Yep, that works. VAD isn't crashing anymore and yes it changes dynamically based on the Assist configuration in Home Assistant. Thanks! |
I may be misunderstanding what is happening but, I am finding that:
--wake-word-name
--wake-word-name
value of the wyoming-satellite script.The text was updated successfully, but these errors were encountered: