Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@kahrendt
Copy link
Contributor

@kahrendt kahrendt commented Apr 23, 2025

Start and continue conversations need special care, especially since the Echo doesn't support duplex audio. This PR makes changes to avoid stopping the voice assistant or starting microWakeWord in the middle of a start/continue conversation.

Updates the yaml to no longer compile with esp-idf v4.4, as the i2s_audio driver will be updated to correctly work on IDF5 with ESPHome 2025.5.0.

ESPhome 2025.5.0 will support configuring on-device wake words through the HA interface (including via the wizard). Three wake word models are included by default on the device: "Okay Nabu", "Hey Mycroft", and "Hey Jarvis". Only "Okay Nabu" will be activated by default.

Closes esphome/issues#7025

@kahrendt kahrendt changed the title Modify M5 Stack ATOM ECHO to support start and continue conversations Modify M5 Stack ATOM ECHO to support all voice assistant features May 11, 2025
@MichaelMKKelly
Copy link

I tried this and it seems to mostly work functionality wise.
However the speaker appears to sounds different and noticeably worse

example of pre-2025.5 HERE
example of 2025.5 with this change HERE

I am not sure what causes this issue but probably should be addressed.
I initially thought my speaker might have gone bad but have gone back and forth and its definitely a change that comes with 2025.5 and/or this config.

@kahrendt
Copy link
Contributor Author

kahrendt commented May 21, 2025

I tried this and it seems to mostly work functionality wise. However the speaker appears to sounds different and noticeably worse

example of pre-2025.5 HERE example of 2025.5 with this change HERE

I am not sure what causes this issue but probably should be addressed. I initially thought my speaker might have gone bad but have gone back and forth and its definitely a change that comes with 2025.5 and/or this config.

Are you building with ESPHome 2025.5.0 or an older dev branch? I did encounter this issue when testing it initially, but esphome/esphome#8738 fixed it for me.

@MichaelMKKelly
Copy link

Are you building with ESPHome 2025.5.0 or an older dev branch? I did encounter this issue when testing it initially, but esphome/esphome#8738 fixed it for me.

definitely building with 2025.5. just tried clearing the build files and recompiling and still have the issue.

@kahrendt kahrendt force-pushed the m5-echo-continue-conversation branch from 215aad1 to a342c90 Compare May 21, 2025 17:25
@kahrendt
Copy link
Contributor Author

Changing the channels to stereo seems to consistently fix the audio quality issues. Using the previous settings would occasionally have good quality if you constantly restarted playing an audio file. I'm guessing there is some issue with how the new IDF5 driver handles mono audio. We do swap every other sample like the documentation says, but I don't believe that consistently fixes it.

@kahrendt kahrendt marked this pull request as ready for review May 21, 2025 17:44
@jesserockz jesserockz merged commit fe181a5 into esphome:main May 21, 2025
11 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators May 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error when trying to compile firmware for M5Stack device on Beta 2025.5.0b2

5 participants