New micro wake word 2 m5stack-atom-echo.yaml
#242
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pfefferle
reviewed
Jul 22, 2024
The program size (2104013 bytes) is greater than maximum allowed (1835008 bytes)
Co-authored-by: Matthias Pfefferle <[email protected]>
substitutions:
name: m5stack-atom-echo
friendly_name: M5Stack Atom Echo
micro_wake_word_model: okay_nabu # hey_jarvis and hey_mycroft are also supported
packages:
m5stack.atom-echo-wake-word-voice-assistant: github://HarvsG/firmware/wake-word-voice-assistant/m5stack-atom-echo.yaml@patch-3
esphome:
name: ${name}
name_add_mac_suffix: True
friendly_name: ${friendly_name}
api:
encryption:
key: !secret m5_stack_api_key
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_passwordThis is working well for me. |
|
Do you think using a selector like firmware/wake-word-voice-assistant/esp32-s3-box.yaml Lines 534 to 538 in a7db5f3 Edit: I have done this in 807c9b5 |
Evanito
reviewed
Jul 22, 2024
Evanito
approved these changes
Jul 22, 2024
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
pfefferle
reviewed
Jul 23, 2024
Evanito
approved these changes
Jul 26, 2024
jesserockz
approved these changes
Jul 28, 2024
|
Do you have any thoughts on how to roll the microwave wake word forward to ESPHome 2024.9.0? This is the output when trying to build: INFO ESPHome 2024.9.0 speaker.i2s_audio: [source /data/packages/23002489/wake-word-voice-assistant/m5stack-atom-echo.yaml:65] [mode] is an invalid option for [speaker.i2s_audio]. Did you mean [i2s_mode]? |
I'm seeing the same error with my m5stack-atom on ESPHome 2024.9.0. ☝️ |
Try changing |
|
Can anyone confirm that MicroWakeWord works on their Atom Echo? All my builds with ESPHome version 2024.7.1, 2024.8.3, 2024.9.0 result in unstable software. It does connect with Home Assistant and entities are shown and e.g. listen light can be toggled. Below are 2 logs, the first one is where my log stop before I reset the device, the logs stop with: Could anyone point me into directions? After I reset device, the logs append with the following: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Micro wake word 2 is possible on the M5 Stack Atom Echo since 2024.7.0
However it's end of speech detection was affected greatly by the issue fixed in esphome/esphome#7109 so this version targets 2024.7.1
This firmware is adapted from
https://github.com/esphome/firmware/blob/main/voice-assistant/m5stack-atom-echo.yamlThere are some notable changes:
use_wake_wordtoggle that used to switch between steamed audio to 'click to converse' is replaced by a toggleuse_micro_wake_wordthat switches between micro wake word and steamed audio.Example firmware built on 2024.7.1 807c9b5 which can be flashed by https://web.esphome.io/
(Note because the URLs in the firmware point towards this repo, if you try to adopt via the ESPHome dashboard it will overwrite this PR with the old, non mww2 firmware until this is merged)
Until merge, if you would like to install your own via ESPHome dashboard then this config should work