Troubleshooting a ESP32-S3-BOX-3 to get it integrated, detects wakeword but doesn't act on it

[boreal lark]

I'm trying to get this esp32-s3-box3 to work and I've got the serial console open, and when I drop the "ok nabu" default wakeword I can see a lot of activity but it never seems to get to a point where it listens for commands, and the image on the screen is the HA default "idle" graphic and never switching to the "listening" graphic. Pastebin of the output from the serial console is here: https://pastebin.com/Ecxi5q5w

The logbook for the device itself shows it turning on, and if i send commands from HA to the device like changing the screen or updating the configuration those go through successfully, it doesnt get beyond internally recognizing the wakeword without exhibiting any external signs of having done so.

HA is running:
Core 2024.9.2
Supervisor 2024.09.1
Operating System 13.1
Frontend 20240909.1

ESPHome Add-On: 2024.9.1
OpenWakeWord: 1.10.0
Whisper: 2.1.2
Piper: 1.5.2

ESP32 firmware: 2024.9.0

Those integrations all seem to be running and Wyoming can see them, the pipeline just seems blocked somehow within the ESP32 device.

I've been running HA for a while, but this is the first attempt at a voice remote.

[barren venture]

Hi there,
this looks like it is an issue with the device streaming audio via the pipeline. Frome the logs it shows that the wakeword is being detected which confirms that the device itself is functioning as it should. The next steps, the screen changes etc are triggered by event from the pipeline.
In HA>>Settings>>Voice assistants>>Assist , your settings should look similar to this screenshot

One thing to do to start , would be to delete the device from the ESPHome integration in HA>>settings>>devices and services>> ESPHome and then to re-add it. You can add the device manually by clicking 'add integration' then 'ESPHome' at this point you will be asked for 'host' for this the easiest way is to use the devices ip address (you should be able to obtain this from your router)
Once re-added , give it a test. if it still fails to respond to a command ,
it looks from the logs that the speech to text is not triggering, can you check the faster-whisper add-on to see if there are any errors in the logs? also check HA >> settings>>system>>logs and see if you can see any relevant messages logged that may help pinpoint the issue.
Another possible cause, can be if the device and the HA instance are on different network subnets/vlans so it is worth looking at that side too.
Let us know how you get on with the above, and if still unresolved we can look deeper to help get you up and running.
Cheers
Rob