ESPHome problème création sensor, binary_sensor,

Mon problème

Bonjour à tous,

J’ai créé un BLE Proxy sous ESP Home avec un petit modul ESP Wroom 32.
En configuration de base, tout se passe bien au niveau du flashage :
yaml de l’esp32 :

substitutions:
  name: esp32-bluetooth-proxy-4cb664
  friendly_name: Bluetooth Proxy 4cb664
packages:
  esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/esp32-generic.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: XXXXXX

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

esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: true
    
bluetooth_proxy:
  active: true

button:
  - platform: safe_mode
    name: Safe Mode Boot
    entity_category: diagnostic

Mais dès que je tente de rajouter des sensor, binary_sensor, ou switch; le flash fail; alors que le yaml est bien validé avec le bouton « validate ».
yaml

substitutions:
  name: esp32-bluetooth-proxy-4cb664
  friendly_name: Bluetooth Proxy 4cb664
packages:
  esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/esp32-generic.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: XXXXXX


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

esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: true
    
bluetooth_proxy:
  active: true

button:
  - platform: safe_mode
    name: Safe Mode Boot
    entity_category: diagnostic

binary_sensor:
  - platform: status
    name: "Statut"

sensor:
  - platform: wifi_signal
    name: "Signal Wifi"
    update_interval: 60s
    
  - platform: uptime
    name: "Allumé depuis (s)"
    id: uptime_sec
       
switch:
  - platform: restart
    name: "Redémarrage"

Le log d’erreur:

INFO Reading configuration /config/esphome/esp32-bluetooth-proxy-4cb664.yaml...
INFO Generating C++ source...
INFO Compiling app...
Processing esp32-bluetooth-proxy-4cb664 (board: esp32dev; framework: espidf; platform: platformio/espressif32@5.3.0)
--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
 - framework-espidf @ 3.40404.0 (4.4.4) 
 - tool-cmake @ 3.16.9 
 - tool-ninja @ 1.10.2 
 - toolchain-esp32ulp @ 2.35.0-20220830 
 - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5
Reading CMake configuration...
Dependency Graph
|-- noise-c @ 0.1.4
|   |-- libsodium @ 1.10018.1
|-- Improv @ 1.2.3
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_frame_helper.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_pb2.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_pb2_service.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_server.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/list_entities.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/proto.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/subscribe_state.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/user_services.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/bluetooth_proxy/bluetooth_connection.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/bluetooth_proxy/bluetooth_proxy.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/button/button.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32/gpio.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32/preferences.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32_ble/ble.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32_ble/ble_advertising.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32_ble/ble_uuid.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32_ble_client/ble_characteristic.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32_ble_client/ble_client_base.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32_ble_client/ble_service.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/esp32_ble_tracker/esp32_ble_tracker.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/improv_base/improv_base.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/improv_serial/improv_serial_component.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/logger/logger.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/md5/md5.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/mdns/mdns_component.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/mdns/mdns_esp32.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/mdns/mdns_esp8266.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/mdns/mdns_host.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/mdns/mdns_rp2040.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/network/util.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/ota/ota_backend_arduino_esp32.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/ota/ota_backend_arduino_esp8266.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/ota/ota_backend_arduino_rp2040.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/ota/ota_backend_esp_idf.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/ota/ota_component.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/safe_mode/button/safe_mode_button.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/socket/bsd_sockets_impl.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/socket/lwip_raw_tcp_impl.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/socket/socket.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/wifi/wifi_component.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/wifi/wifi_component_esp32_arduino.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/wifi/wifi_component_esp8266.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/wifi/wifi_component_esp_idf.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/wifi/wifi_component_pico_w.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/application.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/component.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/component_iterator.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/controller.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/entity_base.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/helpers.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/log.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/scheduler.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/string_ref.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/util.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o
Linking /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/firmware.elf
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o:(.literal._ZN7esphome3api13APIConnection14switch_commandERKNS0_20SwitchCommandRequestE+0x8): undefined reference to `esphome::switch_::Switch::turn_on()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o:(.literal._ZN7esphome3api13APIConnection14switch_commandERKNS0_20SwitchCommandRequestE+0xc): undefined reference to `esphome::switch_::Switch::turn_off()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o:(.literal._ZN7esphome3api13APIConnection17send_sensor_stateEPNS_6sensor6SensorEf+0x8): undefined reference to `esphome::sensor::Sensor::has_state() const'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o:(.literal._ZN7esphome3api13APIConnection16send_sensor_infoEPNS_6sensor6SensorE+0x4): undefined reference to `esphome::sensor::Sensor::get_accuracy_decimals()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o:(.literal._ZN7esphome3api13APIConnection16send_sensor_infoEPNS_6sensor6SensorE+0x8): undefined reference to `esphome::sensor::Sensor::get_state_class()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o: in function `esphome::api::APIConnection::switch_command(esphome::api::SwitchCommandRequest const&)':
/config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.cpp:477: undefined reference to `esphome::switch_::Switch::turn_on()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.cpp:479: undefined reference to `esphome::switch_::Switch::turn_off()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o: in function `esphome::api::APIConnection::send_sensor_state(esphome::sensor::Sensor*, float)':
/config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.cpp:423: undefined reference to `esphome::sensor::Sensor::has_state() const'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.o: in function `esphome::api::APIConnection::send_sensor_info(esphome::sensor::Sensor*)':
/config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.cpp:436: undefined reference to `esphome::sensor::Sensor::get_accuracy_decimals()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/components/api/api_connection.cpp:438: undefined reference to `esphome::sensor::Sensor::get_state_class()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0xb8): undefined reference to `vtable for esphome::status::StatusBinarySensor'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0xbc): undefined reference to `vtable for esphome::status::StatusBinarySensor'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0xd8): undefined reference to `vtable for esphome::wifi_signal::WiFiSignalSensor'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0xdc): undefined reference to `vtable for esphome::wifi_signal::WiFiSignalSensor'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0xfc): undefined reference to `vtable for esphome::uptime::UptimeSensor'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0x100): undefined reference to `vtable for esphome::uptime::UptimeSensor'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0x120): undefined reference to `vtable for esphome::restart::RestartSwitch'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0x124): undefined reference to `vtable for esphome::restart::RestartSwitch'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0x17c): undefined reference to `esphome::binary_sensor::BinarySensor::BinarySensor()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0x180): undefined reference to `esphome::sensor::Sensor::Sensor()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0x184): undefined reference to `esphome::sensor::Sensor::set_state_class(esphome::sensor::StateClass)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0x18c): undefined reference to `esphome::sensor::Sensor::set_accuracy_decimals(signed char)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o:(.literal._Z5setupv+0x190): undefined reference to `esphome::switch_::Switch::Switch()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o: in function `setup()':
/config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/main.cpp:228: undefined reference to `esphome::binary_sensor::BinarySensor::BinarySensor()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/main.cpp:247: undefined reference to `esphome::sensor::Sensor::Sensor()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o: in function `std::vector<esphome::binary_sensor::BinarySensor*, std::allocator<esphome::binary_sensor::BinarySensor*> >::push_back(esphome::binary_sensor::BinarySensor* const&)':
/data/cache/platformio/packages/toolchain-xtensa-esp32/xtensa-esp32-elf/include/c++/8.4.0/bits/stl_vector.h:1076: undefined reference to `esphome::sensor::Sensor::set_state_class(esphome::sensor::StateClass)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/cache/platformio/packages/toolchain-xtensa-esp32/xtensa-esp32-elf/include/c++/8.4.0/bits/stl_vector.h:1081: undefined reference to `esphome::sensor::Sensor::set_accuracy_decimals(signed char)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o: in function `esphome::status::StatusBinarySensor* esphome::Application::register_component<esphome::status::StatusBinarySensor>(esphome::status::StatusBinarySensor*)':
/config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/core/application.h:132: undefined reference to `esphome::sensor::Sensor::Sensor()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o: in function `setup()':
/config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/main.cpp:283: undefined reference to `esphome::sensor::Sensor::set_state_class(esphome::sensor::StateClass)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/main.cpp:285: undefined reference to `esphome::sensor::Sensor::set_accuracy_decimals(signed char)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o: in function `esphome::wifi_signal::WiFiSignalSensor* esphome::Application::register_component<esphome::wifi_signal::WiFiSignalSensor>(esphome::wifi_signal::WiFiSignalSensor*)':
/config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/core/application.h:132: undefined reference to `esphome::switch_::Switch::Switch()'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/controller.o:(.literal._ZN7esphome10Controller16setup_controllerEb+0x18): undefined reference to `esphome::binary_sensor::BinarySensor::add_on_state_callback(std::function<void (bool)>&&)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/controller.o:(.literal._ZN7esphome10Controller16setup_controllerEb+0x1c): undefined reference to `esphome::sensor::Sensor::add_on_state_callback(std::function<void (float)>&&)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/controller.o:(.literal._ZN7esphome10Controller16setup_controllerEb+0x20): undefined reference to `esphome::switch_::Switch::add_on_state_callback(std::function<void (bool)>&&)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/esphome/core/controller.o: in function `esphome::Controller::setup_controller(bool)':
/config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/core/controller.cpp:11: undefined reference to `esphome::binary_sensor::BinarySensor::add_on_state_callback(std::function<void (bool)>&&)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/core/controller.cpp:29: undefined reference to `esphome::sensor::Sensor::add_on_state_callback(std::function<void (float)>&&)'
/data/cache/platformio/packages/toolchain-xtensa-esp32/bin/../lib/gcc/xtensa-esp32-elf/8.4.0/../../../../xtensa-esp32-elf/bin/ld: /config/esphome/.esphome/build/esp32-bluetooth-proxy-4cb664/src/esphome/core/controller.cpp:35: undefined reference to `esphome::switch_::Switch::add_on_state_callback(std::function<void (bool)>&&)'
collect2: error: ld returned 1 exit status
*** [/data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/firmware.elf] Error 1
========================= [FAILED] Took 94.74 seconds =========================
Merci pour votre aide précieuse!

EDIT:
Je m’apercois aussi que meme avec la configuration qui fonctionne, aucun device n’est découvert…

Ma configuration


[center]## System Information

version core-2023.5.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.10.11
os_name Linux
os_version 6.1.25
arch aarch64
timezone Europe/Paris
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
GitHub API Calls Remaining 4818
Installed Version 1.32.1
Stage running
Available Repositories 1354
Downloaded Repositories 28
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 10.1
update_channel stable
supervisor_version supervisor-2023.04.1
agent_version 1.5.1
docker_version 23.0.3
disk_total 27.9 GB
disk_used 10.3 GB
healthy true
supported true
board odroid-n2
supervisor_api ok
version_api ok
installed_addons Terminal & SSH (9.7.0), File editor (5.6.0), TasmoAdmin (0.24.3), Studio Code Server (5.5.7), Mosquitto broker (6.2.1), Node-RED (14.2.0), InfluxDB (4.6.0), ESPHome (2023.5.1), Grafana (8.3.0), Samba Backup (5.2.0), Z-Wave JS (0.1.80), Z-Wave JS UI (1.13.0)
Dashboards
dashboards 3
resources 20
views 7
mode storage
Recorder
oldest_recorder_run 9 mai 2023 à 09:14
current_recorder_run 18 mai 2023 à 15:27
estimated_db_size 398.67 MiB
database_engine sqlite
database_version 3.40.1
Sonoff
version 3.5.1 (122751c)
cloud_online 0 / 2
local_online 2 / 2
[/center]

Bonjour,
j’avais eu des soucis pour reflasher un atom lite et j’ai fais clean build file avant de refaire un flash avec mon config.yaml modifier avec des sensors et binary_sensor.

sensor:
  - platform: wifi_signal
    name: "WiFi Signal dB"
    id: wifi_signal_db
    update_interval: 60s
    entity_category: "diagnostic"

  - platform: copy
    source_id: wifi_signal_db
    name: "WiFi Signal Percent"
    filters:
      - lambda: return min(max(2 * (x + 100.0), 0.0), 100.0);
    unit_of_measurement: "Signal %"
    entity_category: "diagnostic"

  - platform: uptime
    name: "BLE Proxy Uptime"

  - platform: internal_temperature
    name: "Internal Temperature"

switch:
  - platform: restart
    name: "BLE Proxy Restart"

binary_sensor:
  - platform: status
    name: "BLE Proxy Statut"

Pas besoin d’ajouter:

button:
- platform: safe_mode
  name: Safe Mode Boot
  entity_category: diagnostic

c’est déja inclus dans le packages bluetooth-proxies/esp32-generic.yaml at main · esphome/bluetooth-proxies · GitHub

Super merci, on avance un peu.
J’ai reussi a rajouter les boutons

binary_sensor:
  - platform: status
    name: "Statut"

sensor:
  - platform: wifi_signal
    name: "Signal Wifi"
    update_interval: 60s
    
  - platform: uptime
    name: "Allumé depuis (s)"
    id: uptime_sec
       
switch:
  - platform: restart
    name: "Redémarrage"

Mais si je rajoute ca , ca fail :

text_sensor:
   - platform: template
     name: "Allumé depuis (j)"
     lambda: |-
       int seconds = (id(uptime_sec).state);
       int days = seconds / (24 * 3600);
       seconds = seconds % (24 * 3600); 
       int hours = seconds / 3600;
       seconds = seconds % 3600;
       int minutes = seconds /  60;
       seconds = seconds % 60;
       return { (String(days) +"d " + String(hours) +"h " + String(minutes) +"m "+ String(seconds) +"s").c_str() };          
     icon: mdi:clock-start
     update_interval: 60s
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bootloader_support/src/bootloader_efuse.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bootloader_support/src/idf/bootloader_sha.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/controller/esp32/bt.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/controller/esp32/hli_api.o
Archiving /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/esp-idf/bootloader_support/libbootloader_support.a
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/controller/esp32/hli_vectors.o
/config/esphome/esp32-bluetooth-proxy-4cb664.yaml: In lambda function:
/config/esphome/esp32-bluetooth-proxy-4cb664.yaml:55:17: error: 'String' was not declared in this scope
        return { (String(days) +"d " + String(hours) +"h " + String(minutes) +"m "+ String(seconds) +"s").c_str() };
                 ^~~~~~
/config/esphome/esp32-bluetooth-proxy-4cb664.yaml:55:17: note: suggested alternative: 'trunc'
        return { (String(days) +"d " + String(hours) +"h " + String(minutes) +"m "+ String(seconds) +"s").c_str() };
                 ^~~~~~
                 trunc
/config/esphome/esp32-bluetooth-proxy-4cb664.yaml:55:113: error: could not convert '{<expression error>}' from '<brace-enclosed initializer list>' to 'esphome::optional<std::__cxx11::basic_string<char> >'
        return { (String(days) +"d " + String(hours) +"h " + String(minutes) +"m "+ String(seconds) +"s").c_str() };
                                                                                                                 ^
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/btc/core/btc_alarm.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/api/esp_blufi_api.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/btc/core/btc_manage.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/btc/core/btc_task.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/btc/profile/esp/blufi/blufi_prf.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/btc/profile/esp/blufi/blufi_protocol.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/osi/alarm.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/osi/allocator.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/osi/buffer.o
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/osi/config.o
*** [/data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/src/main.o] Error 1
Compiling /data/esp32-bluetooth-proxy-4cb664/.pioenvs/esp32-bluetooth-proxy-4cb664/bt/common/osi/fixed_queue.o
========================= [FAILED] Took 98.94 seconds =========================

De plus, je n’ai strictement aucune remontée de device…
A noter que j’ai un clé bluetooth brancher physiquement en USB sur mon odroïd qui ne remonte rien non plus…
J’ai mis ca dans configuration.yaml

bluetooth:
device_tracker:
  - platform: bluetooth_tracker
    new_device_defaults:
      track_new_devices: true
  - platform: bluetooth_le_tracker
    new_device_defaults:
      track_new_devices: true

J’avais un soucis identique pour le template, n’ayant pas réussi a le faire fonctionner je suis passer par un template sur HA.

template.yaml:

- sensor:
    - name: Bluetooth Proxy Uptime Readable
      state: >-
        {% set uptime = states.sensor.bluetooth_proxy_uptime.state | int(0) %}
        {% set jours = (uptime / 86400) | int(0) %}
        {%- if jours > 0 -%}
          {{ jours }} jours, {{ (uptime - (jours * 86400)) | int(0) | timestamp_custom('%H:%M:%S', false) }}
        {%- else -%}
          {{ uptime | int(0) | timestamp_custom('%H:%M:%S', false) }}
        {%- endif -%}
      unique_id: bluetooth_proxy_uptime_readable

uptime ble

Ok.
Comment fais tu pour inclure ce template dans le .yaml de l’esp?
Des idees sur le fait qu’aucune donnée ne remonte?
Le fait d’avoir une cle usb physique + ble proxy peut poser probleme? Les 2 peuvent cohabiter?

C’est pas par esp mais par HA que j’ai fait le template.

Non, pas de soucis. J’ai une clé ble et 2 ble proxy.

Et concernant le fait de n’avoir aucune remontée? Une idée?

Aucune remonté de quoi ?
il découvre pas t’es appareil BLE ?
Ton BLE Proxy est pas découvert ?

Mes appareils. J’ai rien.
Le proxy est bien decouvert.

Quels sont les appareils et marque ?
Ta clé bluetooth est installer dans HA avec l’intégration Bluetooth ?

Du moment que ta clé bluetooth est installer dans HA et que t’es BLE proxy sont installer dans HA, ca va te découvrir automatiquement les appareils bluetooth. Au pire tu peu les ajouter manuellement.

Salut

Tous les appareils Bluetooth ne sont pas forcement détectés.

quels sont les appareils Bluetooth que tu cherches a détecter.

oui

Des thermomètres Xiaomi ( CGG1 et MJ_HT_V1) ainsi que de Mi Flora

Salut
Effectivement les Miflora et les MJ_HT_V1 ça devrait remonter

juste un truc qui me titille dans ton code

je ne comprends pas pourquoi tu utilises

packages:
  esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/esp32-generic.yaml@main

Normalement tu n’as rien d’autre a rajouter que

esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: true
    
bluetooth_proxy:
  active: true

en utilisant le firmware dédié ça donne quoi ?
ESPHome Bluetooth Proxy

c’est la configuration trouvée dans le lien github donné par @WarC0zes dans sa 1ere réponse.

Je viens de reflasher en rentrant manuellement les paramètres

sensor:
  - platform: xiaomi_lywsdcgq
    mac_address: "4C:65:A8:XX:XX"
    temperature:
      name: "LYWSDCGQ Temperature"
    humidity:
      name: "LYWSDCGQ Humidity"
    battery_level:
      name: "LYWSDCGQ Battery Level"

et la ca remonte bien.
J’ai l’impression que je ne comprends pas bien le fonctionnement de ESPHome… ca n’est pas sensé sniffer automatiquement les trames qui passent à proximité?
Et maintenant les infos du device rentré manuellement remontent toutes les 4 secondes. C’est normal des remontées aussi fréquentes? y’a pas un risque de « surcharge » de HA si j’ai une dizaines de device?

[15:42:32][D][xiaomi_ble:328]: Got Xiaomi LYWSDCGQ (4C:65:A8:XX:XX):
[15:42:32][D][xiaomi_ble:331]:   Temperature: 18.7°C
[15:42:32][D][xiaomi_ble:334]:   Humidity: 54.6%
[15:42:32][D][sensor:094]: 'LYWSDCGQ Temperature': Sending state 18.70000 °C with 1 decimals of accuracy
[15:42:32][D][sensor:094]: 'LYWSDCGQ Humidity': Sending state 54.60000 % with 1 decimals of accuracy
[15:42:36][D][xiaomi_ble:328]: Got Xiaomi LYWSDCGQ (4C:65:A8:XX:XX):
[15:42:36][D][xiaomi_ble:331]:   Temperature: 18.6°C
[15:42:36][D][xiaomi_ble:334]:   Humidity: 54.6%
[15:42:36][D][sensor:094]: 'LYWSDCGQ Temperature': Sending state 18.60000 °C with 1 decimals of accuracy
[15:42:36][D][sensor:094]: 'LYWSDCGQ Humidity': Sending state 54.60000 % with 1 decimals of accuracy
[15:42:42][D][xiaomi_ble:328]: Got Xiaomi LYWSDCGQ (4C:65:A8:XX:XX):
[15:42:42][D][xiaomi_ble:331]:   Temperature: 18.6°C
[15:42:42][D][xiaomi_ble:334]:   Humidity: 54.4%
[15:42:42][D][sensor:094]: 'LYWSDCGQ Temperature': Sending state 18.60000 °C with 1 decimals of accuracy
[15:42:42][D][sensor:094]: 'LYWSDCGQ Humidity': Sending state 54.40000 % with 1 decimals of accuracy
[15:42:46][D][xiaomi_ble:328]: Got Xiaomi LYWSDCGQ (4C:65:A8:XX:XX):
[15:42:46][D][xiaomi_ble:337]:   Battery Level: 72%
[15:42:46][D][sensor:094]: 'LYWSDCGQ Battery Level': Sending state 72.00000 % with 0 decimals of accuracy
[15:42:48][D][xiaomi_ble:328]: Got Xiaomi LYWSDCGQ (4C:65:A8:XX:XX):
[15:42:48][D][xiaomi_ble:331]:   Temperature: 18.6°C
[15:42:48][D][xiaomi_ble:334]:   Humidity: 54.4%
[15:42:48][D][sensor:094]: 'LYWSDCGQ Temperature': Sending state 18.60000 °C with 1 decimals of accuracy
[15:42:48][D][sensor:094]: 'LYWSDCGQ Humidity': Sending state 54.40000 % with 1 decimals of accuracy
[15:42:50][D][xiaomi_ble:328]: Got Xiaomi LYWSDCGQ (4C:65:A8:XX:XX):
[15:42:50][D][xiaomi_ble:334]:   Humidity: 54.3%
[15:42:50][D][sensor:094]: 'LYWSDCGQ Humidity': Sending state 54.30000 % with 1 decimals of accuracy
[15:42:56][D][xiaomi_ble:328]: Got Xiaomi LYWSDCGQ (4C:65:A8:XX:XX):
[15:42:56][D][xiaomi_ble:331]:   Temperature: 18.6°C
[15:42:56][D][xiaomi_ble:334]:   Humidity: 54.3%
[15:42:56][D][sensor:094]: 'LYWSDCGQ Temperature': Sending state 18.60000 °C with 1 decimals of accuracy
[15:42:56][D][sensor:094]: 'LYWSDCGQ Humidity': Sending state 54.30000 % with 1 decimals of accuracy
[15:43:00][D][xiaomi_ble:328]: Got Xiaomi LYWSDCGQ (4C:65:A8:XX:XX):

avant de mettre a genoux ton HA a moins d’être du PI 3, tu devrais avoir quand même pas mal de ressources sous le pied

par contre c’est potentiellement les piles des capteurs qui risque de trinquer

Ok. On peut réduire la fréquence de scan?
Autre question : les infos remontent dans ESPHome comme des entités. Est il possible de regrouper par appareil?
J’ai essyé de mettre un « name » dans le .yaml et ca ne passe pas…

  - platform: xiaomi_lywsdcgq
    mac_address: "4C:65:A8:DC:B6:E2"
    name: capteur SdJ
    temperature:
      name: "Mija SdJ Temperature"
    humidity:
      name: "Mija SdJ Humidity"
    battery_level:
      name: "Mija SdJ Battery Level"

  - platform: xiaomi_cgg1
    mac_address: "58:2D:34:10:52:6B"
    name: capteur SdB
    temperature:
      name: "Cleargrass Gde SdB Temperature"
    humidity:
      name: "Cleargrass Gde SdB  Humidity"
    battery_level:
      name: "Cleargrass Gde SdB  Battery Level"

suis pas sur de ca.
j’ai cru comprendre que le proxy BLE était « sniffeur » et capte les trames qui passent a coté. A priori il n’interroge pas activement les appareils; ce sont eux qui envoient leurs trames?

oui effectivement le principe c’est sniffer les trames
mais de mémoire les mi flora ont tendance a bouffer plus de piles que de raison je ne sais pas si c’est la faute a leur foutu firmware
mais cela a été reporté a plusieurs reprises d’où ma remarque.

pour les miflora il existe une carte native et d’autres customisées

Salut,
c’est la configuration automatique que esphome met pour les bluetooh proxy.

mon config.yaml pour un atom lite:

substitutions:
  name: atom-bluetooth-proxy-854638
  friendly_name: Bluetooth Proxy 854638
packages:
  esphome.bluetooth-proxy: github://esphome/bluetooth-proxies/m5stack-atom-lite.yaml@main
esphome:
  name: ${name}
  name_add_mac_suffix: false
  friendly_name: ${friendly_name}
api:
  encryption:
    key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


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

sensor:
  - platform: wifi_signal
    name: "WiFi Signal dB"
    id: wifi_signal_db
    update_interval: 60s
    entity_category: "diagnostic"

  - platform: copy
    source_id: wifi_signal_db
    name: "WiFi Signal Percent"
    filters:
      - lambda: return min(max(2 * (x + 100.0), 0.0), 100.0);
    unit_of_measurement: "Signal %"
    entity_category: "diagnostic"

  - platform: uptime
    name: "BLE Proxy Uptime"

  - platform: internal_temperature
    name: "Internal Temperature"

switch:
  - platform: restart
    name: "BLE Proxy Restart"

binary_sensor:
  - platform: status
    name: "BLE Proxy Statut"

Comme tu peu le voir , je n’est pas ces lignes, car ca les récupent dans le package ( bluetooth-proxies/m5stack-atom-lite.yaml at main · esphome/bluetooth-proxies · GitHub ).

esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: true
    
bluetooth_proxy:
  active: true

Le interval et window a 1100ms a été changer aussi.

[17:04:48][C][esp32_ble_tracker:591]: BLE Tracker:
[17:04:48][C][esp32_ble_tracker:592]:   Scan Duration: 300 s
[17:04:48][C][esp32_ble_tracker:593]:   Scan Interval: 320.0 ms
[17:04:48][C][esp32_ble_tracker:594]:   Scan Window: 30.0 ms
[17:04:48][C][esp32_ble_tracker:595]:   Scan Type: ACTIVE
[17:04:48][C][esp32_ble_tracker:596]:   Continuous Scanning: True

Merci pour toute ces infos et votre aide