Home Assistant Voice PE device together with openWakeWord?!

Yes, ESPHome 2025.3 (i think) broke this.

Still trying to find a way around it that is compatible with the updates moving forward.

1 Like

Is there any update so far? Thanks a lot for your efforts!

I downgrade ESPHome to 2025.2. This seems to be the only way until the ESPHome team adds whatever resources are necessary to use custom wake words with MicroWakeWord. Its running smoothly with 2025.2 though.

1 Like

I have to downgrade the ESPHome Addon, right? How about the builder app?

There is no official way to downgrade, unless you created a backup of the add-on at the time when you updated. I hadn’t, so I installed this custom repo into add-ons:

Its an archive of previous ESPHome versions, so I went with 2025.2, as that was the last version I recall it working correctly.

Install this then remove the official release ESPHome add-on. It will automatically find your devices. And no, the add-on is the builder app, same thing.

You can train a custom model for micro wakeword using this:

[GitHub - MasterPhooey/MicroWakeWord-Trainer-Docker](https://MicroWakeWord Trainer)

You will have to play with settings. But with this you can run the latest ESPHome Builder and HAVPE release. No hacks required.

2 Likes

Dangit I had held off buying that EGPU until you posted that! :rofl: RIP wallet.

Yes. Ran this yesterday and it works! Going to do a second run tonight with higher sample count. Will post any settings that make a noticeable difference.

1 Like

I was purposely waiting to do Friday’s wake word until I got through the core build. Yeahhh. Well… It’s time. I was hoping the builder was going to catch up. Looks like a good alternative if it’s CUDA only (the right choice). If someone has an IPEX alternative (falls down laughing) I’m all ears…

(starts spend justification doc for adding TB4-Nvidia EGPU. Ooooh a Blackwell rtx if we’re going there. Burn it down…)

1 Like

How does this help bypass needing a custom build to run custom wake words on HAVPE? I had used the original hosted version of the microwakeword trainer to generate my wake word, which I uploaded to my Voice Assistant in HA, but I still cannot select it in the device with today’s version of the default HAVPE firmware.

(EDIT: To clarify, I had the original workaround up and running until I recently restored factory settings on my HAVAPE and ran into this new ESPHome breaking issue.)

With this you basically take control of a HAVPE load only a diff of the production yaml that says yeah all that except this new microwakeword. (it doesn’t work with openwakeword you will need to compile a new one.) thays how.

Compile wake word. Put it in a git repo, take control of a havpe, drop in the right stuff to make it load the custom wake word and bobs yojr uncle.

And because it’s the diff method. If they ever push a new build you just recompile yours and it pulls new with your custom wake word.

The hardest part is getting a good wake word.

You are pulling the official config and overwriting or adding the necessary lines, as well as pointing to your local directory for the custom files

Two and a half months go by and that repo for training microwakeword, and the user, are gone from github.

Yeah seems like the masterphooey docker has been rugged.

You can use this though, looks the same:

1 Like