Esphome - bluetoothproxy- message after update to 2025.3.0

Hi everyone,

After updating to the latest version of Home Assistant (2025.3.0), I noticed a message that I’m unsure how to handle or what actions to take.

Since the Bluetooth proxies installed via the Bluetooth Proxy website still don’t appear in the ESPHome dashboard, I’m not sure what’s going on.

Any ideas?

Thanks,
Cheers, Flo

Me too.

Can you update them via the web server on the device?

The Bluetooth-Proxy do not have webserver component activated (reference → bluetooth-proxies/esp32-generic/esp32-generic-c3.yaml at f4d2525217bcb0431203141f975c26c8355dfe80 · esphome/bluetooth-proxies · GitHub)

I’ll try if I can use this configuration to manually add it via ESPHome dashboard - I’ll report if this helps something.

Cheers mate

Hey everyone! :blush:

I just reflashed my proxy with a new config based on the original one from webflasher. It might not be the “officially recommended” version - I’m not entirely sure - but hey, it works for me! :smile:

For reference, here’s the config I used to flash the bluetooth-proxy (side note: I’ve it now in my ESPHome dashboard too😉).

Hope this helps someone! :blush:

substitutions:
  devicename: "ble-proxy-schlafzimmer-1"

esphome:
  name: $devicename
  comment: "ESP32 C3 - Bluetooth-Proxy"

esp32:
  board: esp32-c3-devkitm-1
  framework:
    type: esp-idf
    sdkconfig_options:
      CONFIG_BT_BLE_42_FEATURES_SUPPORTED: y
      CONFIG_BT_BLE_50_FEATURES_SUPPORTED: n

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: !secret encryption_key

ota:
 - platform: esphome
   id: my_ota
   password: !secret ota_password

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

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: $devicename

captive_portal:

time:
  - platform: homeassistant
    id: homeassistant_time

esp32_ble_tracker:
  scan_parameters:
    # We currently use the defaults to ensure Bluetooth
    # can co-exist with WiFi In the future we may be able to
    # enable the built-in coexistence logic in ESP-IDF
    active: true

bluetooth_proxy:
  active: true

button:
  - platform: safe_mode
    id: button_safe_mode
    name: Safe Mode Boot

  - platform: factory_reset
    id: factory_reset_btn
    name: Factory reset

PS: Sorry, I forgot to mention – this also caused the messages I mentioned above to disappear.

Hallo,
ich verzweifle daran diese Meldung weg zu bekommen.
Alle Versuche in HA mit “take control” über den Bluetooth Proxy in ESP Device Builder führen zum Verlust der Verbindung und Nichts geht mehr,

Einzig per Webflasher Webseite kpl. neu aufsetzen funktioniert, aber dann natürlich wieder die Meldung, es sollte Upgedated werden.
Was für eine Quälerei… wo und wie update ich den Atom-Lite Bluetooth Proxy, damit diese Meldung in HA verschwindet?

Bitte um Hilfe.

Hier noch der Screen des nicht zu Verfügung stehenden Updates:

Let’s stick to English, as this is an international forum. Otherwise, I think 90% of the people here won’t be able to understand you! :slight_smile:

Cheers, mate!

Sorry, now in English :upside_down_face:

Hello,
I’m desperate to get rid of this message.
All attempts in HA with “take control” via the Bluetooth proxy in ESP Device Builder lead to the loss of the connection and nothing works anymore.

Only reinstalling the website completely using Webflasher works, but then of course the message appears again that it needs to be updated.
What torture… where and how do I update the Atom-Lite Bluetooth proxy so that this message disappears in HA?

Using ESP Home Builder always destroyed the firmware and resuts in ofline and so on.

Here an other screen showing no Update available/possible, as 2025.2.2 = stated as newest… but warning about update ESPHome to 2025.2.2 shows up always.
Any solution ?