Voice Preview Error: Writing mute modes failed

My Voice Preview Edition changed to all red LED all the time regardless of the state of the physical mute button.

I have followed all the steps in the debug guide and reinstalled firmware both normally and in boot loader mode.

When added to Home Assistant everything else works as expected (ie. events for button presses, etc.) but of course since it is permanently in mute mode the actual voice portion does not work.

Has anyone seen this error before and have a way to get out of it?

It was running fine for about a day. Then I disconnected it and moved it to a different location where it also worked fine. Then during the night everything turned red and it was permantly stuck in the mute state.

Here are some relevant snippets from the device logs:

[21:03:15][D][esp-idf:000]: E (5113) i2c.master: I2C transaction timeout detected
[21:03:15][D][esp-idf:000]: E (5113) i2c.master: s_i2c_synchronous_transaction(945): I2C transaction failed
[21:03:15][D][esp-idf:000]: E (5114) i2c.master: i2c_master_execute_defined_operations(1366): I2C transaction failed
[21:03:15][E][aic3204:147]: Writing mute modes failed

[21:03:30][E][component:144]: voice_kit is marked FAILED: unspecified

[21:03:30][E][aic3204:114]: Communication failed
[21:03:30][E][component:144]: aic3204.audio_dac is marked FAILED: unspecified

I’m not sure, but probably a few minutes ago. Is it the same issue?

What is firmware version on HAVPE?

What version esphome are you using?

For the firmware I have tried both 25.10.0 and 25.9.0. Installed using this url [Text](Home Assistant Voice PE)

I am not sure what you mean by esphome version. I have the integration installed in Home Assistant, but I can’t find the version number in there anywhere, but there are no updates, so I am assuming I am on the latest version.

I’m on Home Assistant Core 2025.11.2.

(Moving my reply here to keep the threading in place)

I am unable to find the post you seem to be referring to?

Physical mute switch is off correct

You can invert logic in yaml to test if physical mute has issue

And where would I do that? Which yaml file do I change and then how do I flash it again?

I wonder what changed for this to become an issue. I have played around with it some more and with 25.10.0 it boots directly into the red ring and based on the logs it appears to have problems initializing parts of the hardware.

Downgrading to 25.5.2 allows it to correctly boot and initialize everything and then I get a blue ring and everything appears to work.

However, I am unable to actually set it up in Home Assistant because the setup wizard forces a firmware update and then I am right back to the problems.

as a final attempt i would delete device from HA
reflash
repair device with HA

Have you been able to do what @tmjpugh suggested?

I’m in the same situation as you. Suddenly, the device got stuck with the 4 red LEDs.

Looking at the device YAML, I found this: home-assistant-voice-pe/home-assistant-voice.yaml at a163e7b980c572df9d3811ff98094350f5aae541 · esphome/home-assistant-voice-pe · GitHub

So it seems normal that the ring appears blue in older versions; that option was probably not implemented back then. However, the device is still failing.

I also see the following in my logs:

[11:38:14][W][voice_kit:312]: Request version failed
[11:38:14][E][voice_kit:026]: Communication with Voice Kit failed
[11:38:14][E][component:246]: voice_kit was marked as failed
[11:38:14][E][component:362]: voice_kit set Error flag: unspecified

From what I’ve seen, this clearly points to a hardware issue. I’ve tried requesting a hardware replacement, but the device is already over one year old, so I’m not sure if it will be accepted.

Regards,
t3rr0rz0n3