It was and is about microwakeword…
It is on topic and a reply, its you who went off topic…
I doubt there will be any simpler training method and as said even if its not much easier OpenWakeWord is too fat for a esp32-S3, we could be making MicroWakeWord more accurate by collating ondevice captures of the common KW…
Thanks for the code but on 14.01.25 I get this error code in esphome for respeaker
src/esphome/components/i2s_audio_xiao/i2s_audio_xiao.cpp: In member function 'virtual void esphome::i2s_audio_xiao::I2SAudioComponent::setup()':
src/esphome/components/i2s_audio_xiao/i2s_audio_xiao.cpp:15:24: error: 'I2S_NUM_MAX' was not declared in this scope; did you mean 'I2S_NUM_1'?
15 | if (next_port_num >= I2S_NUM_MAX) {
| ^~~~~~~~~~~
| I2S_NUM_1
*** [.pioenvs/esp32s3/src/esphome/components/i2s_audio_xiao/i2s_audio_xiao.cpp.o] Error 1
src/esphome/components/i2s_audio_xiao/speaker/i2s_audio_speaker.cpp: In static member function 'static void esphome::i2s_audio_xiao::I2SAudioSpeaker::player_task(void*)':
src/esphome/components/i2s_audio_xiao/speaker/i2s_audio_speaker.cpp:54:24: error: 'I2S_MCLK_MULTIPLE_DEFAULT' was not declared in this scope; did you mean 'I2S_MCLK_MULTIPLE_512'?
54 | .mclk_multiple = I2S_MCLK_MULTIPLE_DEFAULT,
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| I2S_MCLK_MULTIPLE_512
*** [.pioenvs/esp32s3/src/esphome/components/i2s_audio_xiao/speaker/i2s_audio_speaker.cpp.o] Error 1
========================= [FAILED] Took 65.40 seconds =========================
Try cleaning your build files. I remember seeing it. If it doesn’t disappear, open issue on Github. It’s hard to track things like this in different places. 
I accidentally pressed one of the buttons on my respeaker lite while I was moving it and got an factory reset message. The message went on “press button again to confirm”. I didn’t want a factory reset so I didn’t press the button again. However, the respeaker was unresponsive so I powered it off and powered it on again. After restarting, it is now responding normally. However, the blue LED on top is flashing fast, which I think indicates it’s performing some set up or configuration.
I’m running @formatBCE yaml and just wondering what I can do, other than functional testing to ensre it’s working okay?
It has been on for nearly an hour now. The blue LED is flashing fast and the device is responding normally 
Probably something went wrong with internal S3 flash memory. In PE (and Respeaker) there’s no confirming by pressing it again - rather it says “keep pressing button to reset”. So i’d say you did factory-reset the device.
Try deleting the device from HA and re-adding it. If it doesn’t help, re-flash.
Thanks. I tried that, and LED is still flashing fast. Looks like I’ll be re-flashing it then 
Is that a re-flash of XMOS chip and ESP?
EDIT
I did both anyway. Probably best practice.
LED is back to pulsing slowly blue again so all is well.
I’m curious how to raise visibility of Respeaker related information.
Many people struggle to replace their Alexa/Google speakers with Voice PE now. The speaker on PE isn’t good, so there’s only 3.5mm option, or disassembling and using different speaker.
Same stuff happens with FPH SAT1, it’s not ready yet to replace proprietary satellites (although it’s moving there).
On the other hand, Respeaker Lite Satellite and Koala are the closest to PE on the functionality, and have pretty good speaker and look. I try to help people on FB and Discord, but still if I try to search Google for home assistant satellites (or even directly by “Koala satellite home assistant” and "Respeaker Lite home assistant), there’s no good results even on these specific requests.
Any advices guys?
No great ideas but it would not hurt to add more information to the readme file.
Maybe also create a website on GitHub or elseware?
Can also post how-to guides or article for the project on thinkerer websites like example Instructables and Hackaday:
If anyone is looking for ideas for enclosures for your Respeaker Lite voice assistants, I asked our 6 year old what he could come up with.
Off he went, soon returning with a pile of his Duplo blocks. This is what he built:
The speaker is just visible through the arch and the translucent blue block allows us to see the state of the LED as it happily pulses away.
Happy to supply full list if parts and assembly instructions for anyone who wants to replicate this 
Do you think it would be possible to use the “ReSpeaker Lite 2-Mic Array” USB board without ESP32 (or alternativly the FutureProofHomes Satellite1 Dev Kit) in combination a ESP32-S3 development board and one of these 7-inch series of capacitive touchscreen displays from Elecrow in order to make your own variant of a Home Assistant Voice Satellite with a screen? …i.e. something similar in design to Google Nest Hub and Amazon Echo Show 
At least these “CrowPanel Advance” display series features “replaceable wireless modules” meaning that the ESP32 module can be replaced. That is, this article says that they feature an ESP32-S3-WROOM-1-N16R8 module soldered on the back + having a pin header taking ESP32-H2, ESP32-C6 or…
The specificiation does say that it also features a built-in microphone (however I assume that is rubbish) as well as a speaker connector (but no mention of a DAC).
The also have loads of different models with various sizes of screens. With the “Advanced” series all having a pre-soldered ESP32-S3-WROOM-1-N16R8 module:
CrowPanel Advance ESP32 displays are available on Aliexpress from $25.99 up to $54.19 depending on the selected model and whether any of the wireless modules shown above is added as an option. But you can also purchase the displays and wireless modules on Elecrow’s company’s store. Again see:
I’m not sure there’s enough of resources to hold all this functionality on single S3 tho…
You can try on FPH Sat1 - all free GPIO pins are exposed there.
Look again, my point would be to use two ESP32, not just one.
I got confused with your link to Respeaker WIIHOUT ESP32, and mention of dev board.
Multi-chip boards are hard…
The surcharge for the second module is also comparable to the surcharge for a Respeaker Lite WITH its own Xiao, so not sure why you would bother with all the complications…
