Sorry i ever "took control"

[jherby2k]

This is the third time now i've had trouble updating my Voice after "taking control of the configuration" during the initial install. Currently i'm stuck on version 2025.5.0 - updating now just kinda hangs. Validating just kinda hangs. Cleaning build files just kinda hangs. All with the same pointless messages about strapping pins and nothing helpful in the logs. All my other devices compile/clean/install just fine.

This is my config that was working at least in May:

substitutions:
  name: home-assistant-voice-09451a
  friendly_name: Basement Office Home Assistant Voice
packages:
  remote_package_files:
    url: https://github.com/esphome/home-assistant-voice-pe
    files: [ home-assistant-voice.yaml ]
    refresh: 0s # Had to add this in May to get it to install 2025.5.0
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: !secret basement_office_voice_api_key


wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

Validating, compiling or cleaning build files all give this same output, then just don't progress:

INFO ESPHome 2025.7.2
INFO Reading configuration /config/esphome/home-assistant-voice-09451a.yaml...
INFO Updating https://github.com/esphome/home-assistant-voice-pe@None
INFO Updating https://github.com/esphome/home-assistant-voice-pe@dev
WARNING GPIO0 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO3 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO45 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins

I would go back to the OG "managed" firmware but the browser flashing tool no longer works for me either.

[wmrato]

Compile Error of Home Assistant Voice PE every time, but unable to understand error or get any idea why, when googling it.
I have Cleaned Build Files too.

Same wish too, that I hadn't taken control of Home Assistant Voice PE
But I do like to customise the configs & add substitutions.

Compiling .pioenvs/home-assistant-voice-091586/components/esp-tflite-micro/tensorflow/lite/micro/micro_allocator.cc.o Compiling .pioenvs/home-assistant-voice-091586/components/esp-tflite-micro/tensorflow/lite/micro/micro_context.cc.o xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus compilation terminated. *** [.pioenvs/home-assistant-voice-091586/src/main.cpp.o] Error 1 xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus compilation terminated. *** [.pioenvs/home-assistant-voice-091586/components/esp-tflite-micro/tensorflow/lite/micro/micro_allocation_info.cc.o] Error 1 ========================= [FAILED] Took 220.73 seconds =========================

[lucemans]

As it seems the esphome/components (micro_wake_word, microphone, and voice_assistant) have been replaced with voicekit. (See #f643).

Ran into this myself (with Seeedstudio ReSpeaker) and for now downgrading to the commit before seems to build fine;
Replace this in your config:

  - source:
      type: git
      url: https://github.com/esphome/home-assistant-voice-pe
      ref: dev # <-- this line "use the latest version"

with

      ref: 2ecbe3c54eaed93e4021ecbfc150f0f7077fb3e3

Hope this helps!