-
Notifications
You must be signed in to change notification settings - Fork 155
add "FSM" satellite type #258
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
base: master
Are you sure you want to change the base?
Conversation
As long as we don't have a mechanism to interrupt the response, your solution looks quite interesting I've tried replacing files and restarting the service, but got no change. |
Sorry but I would love to implement this, is this already supported in some way ? |
the changes are implemented in this PR, we're just waiting on the project owner to respond about accepting these changes into the main repo. For now you should be able to apply these commits locally if you need this feature. |
To use the FSM stat you must enable both VAD and wakeword detection from the cli |
Hi Emma, I was wondering if you’d mind sharing some example values that work well for the FSM system you’ve implemented? I’ve tried various combinations, but I just can’t seem to get a smooth conversation flow. For example, when I give a command and the wake word is triggered, sometimes I don’t even have time to say anything before I get a response from Home Assistant. It all feels too fast — with multiple overlapping sounds: the wake sound, the confirmation sound, the response… and I struggle to figure out the right timing for when I’m supposed to talk, when the system is listening, and when it’s Home Assistant’s turn to reply. It’s all a bit chaotic, and I feel like I’m missing that dynamic flow. Maybe you have some default values or a setup that just works for you? I’d really appreciate any tips or examples you could share — I’m a bit stuck right now. Thanks so much in advance! Best, |
I agree that the Pi Zero 2 W is very unstable. I would advise you to switch to esp32S3. I have a configuration on GitHub that implements the same idea — I've been using it for 3 months without any problems. |
Adds a new satellite type designed for advanced back-and-forth conversations. The satellite uses a finite state machine to track conversation state, and uses a combination of VAD and wakeword detection to detect state changes.
States:
State diagram is roughly: