ESPHOME

[cme424]

Hello I am running it in ESPHOME with HA and everytime that I tried to download it in mi ESP32, HA lost conection.

Do you think that its for your configuration?

This is my .yaml

substitutions:
name: esphome-web-2f305c

esphome:
name: ${name}
min_version: 2024.6.0
name_add_mac_suffix: false
project:
name: esphome.web
version: dev

esp32:
board: esp32dev
framework:
type: arduino

logger:
api:
ota:

• platform: esphome
  improv_serial:
  wifi:
  ap: {}
  captive_portal:

dashboard_import:
package_import_url: github://esphome/example-configs/esphome-web/esp32.yaml@main
import_full_config: true

esp32_improv:
authorizer: none
web_server:

external_components:

• source: github://aronsky/esphome-components@main
  components: [ ble_adv_controller ]

ble_adv_controller:

• id: my_controller
  encoding: fanlamp_pro

light:

• platform: ble_adv_controller
  ble_adv_controller_id: my_controller
  name: Luz Principal

fan:

• platform: ble_adv_controller
  ble_adv_controller_id: my_controller
  name: Ventilador

button:

• platform: ble_adv_controller
  ble_adv_controller_id: my_controller
  name: Pair
  cmd: pair

[NicoIIT]

Hello @cme424,

I am also facing the same kind of issues, this seem to occur on some ESP32 base devices, when using the BLE stack while the OTA update is on-going. I faced it with this component, but also with other components so I can for sure say this is not directly due to this component but more to the interaction in between OTA and ESP32_BLE core components.

I tried a basic workaround to disable the BLE stack on OTA and it seems to work:

ota:
  - platform: esphome
    password: !secret ota_password
    on_begin:
      then:
        - ble.disable

In order to have this working you will need to first upload the new firmware with this new part of the config, which is the more complex part if your OTA updates are failing... I would advise to insist, as for me it worked in 20% of the cases before I implemented the change, or use the USB update if possible for your device.

EDIT: I also updated my esphome to latest version, so maybe this change is useless and a bug was corrected in esphome directly...