Unable to set Custom Wake Word on M5Stack ATOM Echo

[static anchor]

Hello! I am trying to follow this guide to setup a custom wake word on my M5Stack ATOM Echo voice assistant. I am able to successfully follow the entire guide basically until the last step. I am able to set the Streaming wake word engine to openwakeword and my wake word to custom uploaded tflite file in my custom assistant.

Where it goes wrong is going into the ESPHome device. I am able to set it to use my custom assistant, but there is now a wake word configuration (not shown in the guide), which is static to the default wake words. I do not see my custom wake word as an option after selecting my custom assistant.

Not sure where to go to get support, but starting here 😄

I have also tried to use the ESPHome add-on to edit the configuration file . I am unable to get it to work with adding a model (as defined here) to my own fork of the esphome repo. I get the error
Not a valid model name, local path, http(s) url, or github shorthand.

[south matrix]

the latest version of the m5 AE voice assistant firmware no longer uses streaming wake words and instead uses MicroWakeWord on the device itself.

OpenWakeWord streaming wake word models are not compatabile with MicroWakeWord which is what is displaying the optons within the device page.

customising MWW models is not yet an easy process. you could try reconfiguring the firmware of the AE to use OWW again but be careful looking at any examples that are older than about 2 months because they will likely be out of date.

[static anchor]

Thanks for the response! I wish the docs were updated to reflect this 😓 I had a feeling this was the case from reading the code changes and bits and peices from other older posts.

Are there any breadcumbs you can point me towards to customizing MWW models? I know a fair amount of knowledge in this space, just not specific to this case. Would be interested to learn how to build a custom wake word for MWW

[south matrix]

the voice setup has changes so much and rapidly over the last year or so that some docs do need to catch up yes.
you can look at the MWW repo here - https://github.com/kahrendt/microWakeWord