#Where did the 'Use Wake Word' switch go on my m5stack Atom Echo?

1 messages · Page 1 of 1 (latest)

fast ore
#

My Atom Echo started behaving differently after the ESP Home 25.2.1 update and changing the package to github://esphome/wake-word-voice-assistants/m5stack-atom-echo/m5stack-atom-echo.yaml@main to avoid the "This feature is not avaialble for the IDF framework version 5" error.

The 'Use Wake Word' switch has gone from the device panel, and I can't find a way to configure the device to start listening when I press the button and dont use the wake word. This is how I used to have it configured before these updates.

What have I done wrong to loose that capability?

fast ore
#

Is there a version of the ESP config that includes a 'Use Wake Word' switch?

proper vector
fast ore
#

Yes, the config I used has the micro_wake_word section in it

#
  on_wake_word_detected:
    - voice_assistant.start:
        wake_word: !lambda return wake_word;```
proper vector
#

microwaveword runs on the device instead of the HA server which openwakeword does which requires it to stream all the time

#

at the top of the config you will see something like this

  name: m5stack-atom-echo
  friendly_name: M5Stack Atom Echo
  micro_wake_word_model: okay_nabu  # alexa, hey_jarvis, hey_mycroft are also supported```
#

for specifing the supported wake words

#

you select "on device" as the "wake word engine location" and it should work

fast ore
#

I do have that section at the top of the YAML.
The engine location option is set to On Device.

#

The wake word "ok nabu" works.

#

I don't want to use the wake word. I want to press the M5 button and then say my command. This is how it used to be prior to last months update and the subsequent "this feature is not available" error.

#

There used to be a switch in the above GUI config panel that allowed you to turn off the wake word,

proper vector
#

oh right, you want to start assist from the button

fast ore
#

Yeah, in this situation that is best for me

proper vector
fast ore
#

The suggested package fails to build, with a series of errors like this:

proper vector
#

did you clean the build files after changing?

fast ore
#

oh no, not that used to this process. Will try again 🙂

proper vector
#

it may or may not help but its usually the best place to start

fast ore
#

No, unfortunately it didnt help 😦

proper vector
#

then copying the entire config from the adopted version and replacing everything with it is probably the next thing to try

fast ore
#

OK, thanks for your help!
I have to leave the approriate Wi-Fi and API settings in the config eh?

proper vector
#

you may also want to transfer over your name/friendlyname too

#

oh and encyrption key too i guess

#

basically take the stufff from your config minux the rackage stuff and slot it in on the adopted config where it should go

#

might seem a bit much at the moment but esphome is pretty easy once you have messed with it a bit

#

i am by no means an expert but i am pretty confident messing with stuff by now 🙂

fast ore
#

Unfortunately I get the same errors about the audio_decoder with the adopted yaml copied into my yaml

#

The only config that seems to work is this pkg: github://esphome/wake-word-voice-assistants/m5stack-atom-echo/m5stack-atom-echo.yaml@main

proper vector
#

ok so with the adopted yaml

#
  board: m5stack-atom
  framework:
    type: esp-idf```
#

change this section

#
  board: m5stack-atom
  framework:
    type: esp-idf
    version: 4.4.8
    platform_version: 5.4.0```
#

to this

fast ore
#

I did figure that out - it wouldn't start the compile with out those two extra lines.

proper vector
#

gimme a moment ill see if i can get it to build. i validated it but didnt build it

#

so yeah, it seems that the audio drives just do not work with newer versions of esphome

#

so i guess the options are:
heavily modify the newer functioning version
or
rollback your esphome builder to 2024.11.3 to install an older version

fast ore
#

huh

#

thanks for confirming that, appreciate it!

proper vector
#

another option, all be it not quick. hopefully in 2025.4 there will be some more stuff to be able to start conversations from HA. you could use an automation on button press to start a conversation from the other side

fast ore
#

Do you know if there is a better forum than here to ask for this previous capability to be restored to the modern version of ESPHome + M5 + wake word?

proper vector
#

you could try on the esphome discord server

#

its a real pain isnt it... i got my stack out and am looking at some stuff

fast ore
#

good idea. I hadn't joined that server yet. I'll do that now and raise a new question over there

proper vector
#

ill have a play with it for a bit, if i get anywhere ill ping you

proper vector
#

@fast ore i have a no wake word / button press trigger working

#

1 moment and will stick on github

#

adapt the name/encryptionkey/wifi settings to your settings

#

probably would have been done quicker but had a seperate problem with my voice pipeline i had to fix in the middle of it

fast ore
#

Oh wow! Thanks so much. I’ll test it out after I get some paid work out of the way!!

proper vector
#

no worries, was a fun little side project

#

gunna clean it up a bit, will update the github as i go

#

bit cleaned up now. let me know how it goes

fast ore
#

How did you do that!!!!

#

Thanks - it works as expected.

proper vector
#

started with the working thing, ripped out all the wake word stuff then reprogrammed the button and a few other bits and pieces to make it work

#

esphome is really powerful and not too bad once you get the hang of it

fast ore
#

What in that yaml config defines the UI that shows up for the M5?

proper vector
#

the assistant stuff is added HA side

#

that stuff thats greyed out because i removed it can be deleted in HA if you want. it just remembers this device used to have that entity

fast ore
#

ah, ok

proper vector
#

i removed the factory reset button in the latest version too

#

not sure if it shows its missing thoug

fast ore
#

thanks again for helping someone still learning the intricacies

proper vector
#

no worries, good luck with the learning!

willow stump
#

Hello

#

I think I have the same problem

#

will someone help me?