-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
[micro_wake_word] add new VPE features #8655
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #8655 +/- ##
==========================================
+ Coverage 53.70% 56.65% +2.94%
==========================================
Files 50 50
Lines 9408 9907 +499
Branches 1654 1338 -316
==========================================
+ Hits 5053 5613 +560
+ Misses 4056 3945 -111
- Partials 299 349 +50 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Hey there @jesserockz, mind taking a look at this pull request as it has been labeled with an integration ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor thing below I will fix in a new PR to not hold this one up
@@ -79,6 +79,7 @@ | |||
#define USE_LVGL_TEXTAREA | |||
#define USE_LVGL_TILEVIEW | |||
#define USE_LVGL_TOUCHSCREEN | |||
#define USE_MICRO_WAKE_WORD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Last time I checked I came after E 😉
But also, this should go inside the #ifdef USE_ESP32
block below
This enables MWW by default. This has become more important since HomeAssistant recently disabled offloaded WakeWord engines by default in new Assist pipelines, ostensibly because "all" client devices now support it. Currently we are limited to just `hey_jarvis` until esphome/esphome#8655 lands in a release and enables dynamic configuration. This will be fully implemented with the SuperSensor v2.0 coming later this month.
What does this implement/fix?
stop_after_detection
. Defaults to true to mimic current behavior. Can be disabled if the device has duplex audio support (currently requires separate I2S busses) and the user wants to leave mWW always runningThis is a breaking change in that only the first model listed will be enabled on the first boot (currently all models would be enabled).
Types of changes
Related issue or feature (if applicable):
Pull request in esphome-docs with documentation (if applicable):
Test Environment
Example entry for
config.yaml
:Silly example, you probably wouldn't want to enable/disable models in the wake_word_detected action.
Checklist:
tests/
folder).If user exposed functionality or configuration variables are added/changed: