I don’t even remember the last time I was able to update my Voice PE. When attempting to compile within ESPHome Builder there is always this or similar error regarding CC1:
Compiling .pioenvs/home-assistant-voice-09996b/src/esphome/components/api/api_connection.cpp.o
xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
*** [.pioenvs/home-assistant-voice-09996b/src/esphome/components/api/api_connection.cpp.o] Error 1
When compiling from command line within VS Code on my laptop the version of ESPHome is always incorrect but on updating ESPHome, I get this:
PS H:\esphome> esphome version
Version: 2025.7.5
PS H:\esphome> esphome compile home-assistant-voice-09996b.yaml
INFO ESPHome 2025.7.5
INFO Reading configuration home-assistant-voice-09996b.yaml…
Failed config
Failed to load packages. Current ESPHome Version is too old to use this package: 2025.7.5 < 2026.1.0.
Nabu Casa.Home Assistant Voice PE: github://esphome/home-assistant-voice-pe/home-assistant-voice.yaml
Right now, I have loaded the device from the ESPHome web installer with a very old version, which used to work, but now the device has the blue twinkling light as though looking for the network. During the web install, the network is successfully connected and yet the twinkling blue light. The log shows appropriate response to switching the mute switch.
My suggestion would be to use a browser web installer to erase the ESP, and then install the VPE stock firmware (my personal preference is CLI esptool.py --port /dev/ttyUSB0 erase_flash).
Parts of the flash don’t get overwritten when changing firmware - and cause issues. I’ve seen this switching between Tasmota / ESPhome / Shelly, and you seem to be switching from stock to custom ESPhome without an erase.
There is some updated information on this. I have been able to install the latest version from the ESPHome web loader. Previously, I was reluctant to re-add the device to HA following the install because previously this resulted in two devices and required a lot of cleanup. I chose to add it anyway and to my surprise there is now an option to ‘update’ the existing instance which worked correctly.
As far as ‘taking control’, it has been a while since I first installed the device but since that option no longer appears in the ESPHome Builder, I have to assume control has been taken.
Compiling the file locally still gives the same error as before.
I am asking OP how it was installed. Docker, addon or other. I see vscode and makes me think install is borked. Update may fix or reinstall but context helps.
So. If I get this error and clean build files don’t work i effectively reinstall esphome. I use docker so it’s basically a restart but for you if you using HAOS I don’t know a user friendly method to approach this. I know several difficult ways
No. You just clear the existing files that are supplemental to the core files, that are needed to successfully compile the yaml your ESPHome project needs.
If your core files are corrupt, they stay corrupt, until the next release.
To be sure, uninstall ESPHome and reinstall. It should clear cache and download necessary files as part of the process, and fresh copies of any integrations/apps needed. Make certain you have copies of all your ESPHome yaml device files in case they disappear.
As I hinted before, the error logs usually contain meaningful information for troubleshooting, both HomeAssistant system logs and ESPHome compile logs.
) device version to latest.