Voice preview edition esphome update

ESPHome
1

Hi, I am trying to update home assistant preview edition to ESPHome 2025.12.1 and receive an error.

I have ‘taken control’ of this device because I have added a bme680 sensor to the Gove Port. All was well until ESPHome 2025.12.0.

Can anyone point me in the right direction for a resolution please?

This is the sensor entry:

sensor:
  - platform: bme680
    i2c_id: grove_i2c
    temperature:
      name: "Bedroom Temperature"
    pressure:
      name: "Bedroom Air Pressure"
    humidity:
      id: "humidity"
      name: "Bedroom Humidity"
    gas_resistance:
      id: "gas_resistance"
      name: "Bedroom Gas Resistance"
    update_interval: 60s

  - platform: template
    name: "Bedroom Air Quality"
    id: iaq
    icon: "mdi:gauge"
    # calculation: comp_gas = log(R_gas[ohm]) + 0.04 log(Ohm)/%rh * hum[%rh]
    lambda: |-
      return log(id(gas_resistance).state) + 0.04 *  id(humidity).state;
    state_class: "measurement"

and this is the error.

INFO ESPHome 2025.12.1
INFO Reading configuration /config/esphome/home-assistant-voice-bedroom.yaml...
INFO Updating https://github.com/esphome/home-assistant-voice-pe@dev
INFO Updating https://github.com/esphome/esphome@72499eaed2ed54316aca90d368053aa2e1a54f5f
WARNING GPIO46 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/#why-am-i-getting-a-warning-about-strapping-pins
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/#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/#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/#why-am-i-getting-a-warning-about-strapping-pins
Failed config

media_source.http_request: [source /data/packages/dc43710d/home-assistant-voice.yaml:1558]
  
  Component media_source.http_request requires component http_request.
  platform: http_request
  id: http_source
  buffer_size: 500000
2
3

This has been raised here and on GitHub
25.12.0 errors in ESP Home with "Component media_source.http_request requires component http_request." · Issue #494 · esphome/home-assistant-voice-pe · GitHub which kahrendt closed with the comment:

The http_request component is included in the .factor.yaml file. If you are just using the base yaml file, you’ll have to manually add the http_request component in your adjusted ymal. The new http_request media_source component now requires it.

I’m not even sure what that means. Looks to me (a non-developer) like Voice PE team have added a new feature, sendspin, and hadn’t finished testing before the ESPHome 2025.12.0 release caused a sudden rush of people recompiling the default code from github.

Another issue was raised in github

I checked back, and cannot find any official notification in the ESPHome release notes, or even an announcement in the ESPhome or Voice Assist community forums. :frowning_face:

1 Like
4

unrelated to sendspin

looks more like undocumented breaking change; must add http_request:
annoying yes but error message literally says what to do and if you look at the default HAVPE yaml on github it is updated with this change.

1 Like
5

just add this to the end of your yaml

http_request:

I had a similar issue when hacking the VPE semdspin yaml.

1 Like
6

Thanks, that fixed it. As others pointed out, the solution was actually in the error message. I didn’t make the connection. Thanks for taking the time to respond.

7

Actually the entire sendspin hasn’t been merged and the entire audio pipeline is a work in progress and subject to change

It works well but it may change

It should be an issue since the many yaml is kept up to date.