Release 2026.1.0 withdrawn, new version 2026.1.A

[PedroKTFC]

I've reset the default base to the last known working version. This means the buffer overflow issue some people were seeing will be there. I intend to update over the next few days in the following order:

• Missing IDs & language files
• Tyre pressure sensors
• Fixes for the overflow buffer (this is where I think the new issue comes from)
  The .A (.B, .C etc) numbering scheme reflects the fact these versions will be catch ups to 2026.1.0.

I will only make a new release when I've had confirmation from more than one user that the last release is working as expected. That includes this release. Although it is set to the last working release, it's always possible my GitHub skills mean I have not quite got it right.

Thanks for bearing with me.

[patfelst]

thanks Pedro, I'm happy to help test, although I've not seen the crash during charging. FWIW in my years experience coding in C++ for microcontrollers, the most common cause of crashes is manipulating character strings and arrays so it sounds like you're on the right track.

Can you pls confirm the syntax to include the correct packages?

substitutions:
  ...
  tesla_ble_component: "github://PedroKTFC/esphome-tesla-ble@main"
  BLE_library: "https://github.com/PedroKTFC/tesla-ble.git#main" # ????

packages:
  remote_package_files:
    url: https://github.com/PedroKTFC/esphome-tesla-ble/
    path: packages
    files: [base.yml, common.yml, project.yml, client.yml]
    ref: main # ???

[top-gun]

Just to clarify for me, when I open the logs of the device on esphome while the car is awake, the ESP still crashes. Is this something that you know about? Or do I have the wrong version caused by GitHub caching?

Interesting, this has never happened to me. We both use an M5Stack Atom S3 lite, right?

[lukej0]

I am using the M5Stack Atom S3 with a Display. The Atom S3 Lite does not have the display if I recall right.

[top-gun]

I am using the M5Stack Atom S3 with a Display. The Atom S3 Lite does not have the display if I recall right.

Yepp, the S3 Lite is just the SBC in a convenient case. Less hassle with insulation. :)

The display is imho a ressource hog. It might cause issues to have that on the ESP together with the relatively heavy-weight BLE stack.

[lukej0]

I also tried without code for the display, but the behaviour was the same. I have a spare Atom S3 Lite. I will try, if something changes when using it.

[lukej0]

Same behavior with the Lite. But as I am still having the TPMS, I might try building again tomorrow

[patfelst]

ok thanks, its working for me ok, although I haven't put it on charge.

I'm seeing it check for TPMS in the logs, even though I have those entities disabled.

plus another error, seems related to reading the charge state

[nagyrobi]

It would probably make sense to use GitHub's release functionality, instead of always using a branch directly.

[top-gun]

Update: I didn't want to wait until tomorrow, so I deleted the entire .esphome folder and recompiled. I don't see the getTyreState error messages anymore, and the entities are gone, too. That caching mechanism is a bit frustrating for the speed of iterations that we have in this project.

No big deal, but sometimes any good news is good for morale: I recompiled yesterday in the evening, and this uptime graph looks pretty good. All these decreases were caused by fresh builds.

[patfelst]

Can you try cleaning the whole build - hit the "CLEAN ALL" link at the top of the ESPHome add-on page and rebuild (go for a coffee, maybe 2 or 3) while you wait for it to complete. Hopefully that'll pull through the right version.

thanks, that did the trick - no more TPMS!

[top-gun]

It would probably make sense to use GitHub's release functionality, instead of always using a branch directly.

Github is a combination of a complex command line tool with poor documentation and custom extensions from the platform. Maybe it would help to offer some guidance for the functionality you describe.

[PedroKTFC]

It would probably make sense to use GitHub's release functionality, instead of always using a branch directly.

I did come across this yesterday and made a mental note to look into it when I've got a bit of time. As @top-gun said, GitHub isn't the easiest to understand how to do things and there doesn't seem to be a lot of help online (or maybe there's too much and you can't see the wood for the trees).

[patfelst]

Now that I have the proper roll back version, are these log errors known already? This happens when I wake the vehicle

and another one shortly after

after these errors the logs are clean, just green text.

[top-gun]

That's normal, this happens when the dongle was rebooted or the last authentication has expired.

This is the stuff that is part of the baseline and we don't get to see it because we don't watch the log when everything is fine :)

[PedroKTFC]

I've created a new project branch repair where I intend to incrementally make changes to the code and have tested more widely before releasing it into main (I will look at the release mechanism, honest!). This now contains a couple of convenience updates which I am fairly confident won't break anything but I'd like them tested by some users before releasing them more widely. The changes add language files and IDs to all the sensors. To use this branch you need the following in your yaml:

This substitution:

  tesla_ble_component: "github://PedroKTFC/esphome-tesla-ble@repair"

This packages settings (this is a simplified version of the original packages multi line files specification you might have, just replace that):

packages:
  remote_package_files:
    url: https://github.com/PedroKTFC/esphome-tesla-ble/
    path: packages
    files: [base.yml, common.yml, project.yml, client.yml]
    ref: repair

Please let me know how it works for you. Many thanks for testing.

[lukej0]

It is working for me.
Version: 2026.1.B-repair
Uptime: >8.000s with a short charging test.

[nagyrobi]

No reboots here either.

[patfelst]

You seem to have dropped ble presence from the repair branch in common.yml, can you add it back in - with an ID - please?

esphome-tesla-ble/packages/common.yml

Line 15 in d2c9696

- platform: ble_presence

[patfelst]

thanks @top-gun same thing happened and I was just trying to figure what the issue was, you saved me some time. Compiled and flashed ok, is working ok so far. Will check charging soon.

[PedroKTFC]

Thanks for spotting that @top-gun . I've added that back in to the base.yml where it should have been. I've also taken the opportunity to reset the default value to a more reasonable 30s (it was 5s).

(I had a substitution in my yaml to change its value hence not spotting it myself.)

[top-gun]

Fwiw, just to wrap it up: Uptime seems fine - I installed two hours ago, and had no reboots. I even started a charge as that gave some people issues, no crash, no reboot. Atm life is pretty good on the Tesla side - if only we could say the same about our weather.

[patfelst]

holy crap, that's very mono chromatic, and a tad cold! Where are you @top-gun ?

[top-gun]

Ok, the test-charge was fine. I let Octopus control the process over night to fill the battery. As usual, they started at 1AM with a limited slot, then started again at 2:02AM with a longer cycle that extended up to 100% battery (LFP). There was one reboot at 2:10. That's 8 minutes after the charging process started so I don't think it was directly connected. That level of reliability is fine for me.

@patfelst I'm in northern germany. My kids are 9 - so far we had three winters where they actually saw real snow. This year is "different" ;) It was also taxing on the heatpump. -9°C was the worst I saw this weekend.

[capof1000]

HI Pedro, thank you so much for your work. I try to built a littel display base on guition .

i try your repair branch , and this is the output 👍

[21:32:05.403][I][tesla_ble_vehicle:1004]: Reading INFOTAINMENT, previous_asleep_state_=1, car_just_woken_=0, car_is_charging_=0, Unlocked=0, User=0, fast_poll_if_unlocked_=0
[21:32:05.409][I][tesla_ble_vehicle:116]: [wake vehicle] Preparing command.. action value 0
[21:32:05.416][I][tesla_ble_vehicle:372]: [wake vehicle] Executing command.. | attempt 1/5
[21:32:05.426][I][tesla_ble_vehicle:378]: [wake vehicle] Command executed, waiting for response..
[21:32:05.903][W][tesla_ble_vehicle:1734]: [wake vehicle] VCSEC session invalid, requesting new session info..
[21:32:06.106][I][tesla_ble_vehicle:601]: [44df598d437bbe9016899d7e77c62f26] Updated session info for DOMAIN_VEHICLE_SECURITY
[21:32:06.109][E][tesla_ble_vehicle:121]:   MessageStatus:
[21:32:06.111][E][tesla_ble_vehicle:122]:     operation_status: ERROR
[21:32:06.113][E][tesla_ble_vehicle:123]:     signed_message_fault: ERROR_TIME_EXPIRED
[21:32:06.115][E][tesla_ble_vehicle:610]: Received error message from domain DOMAIN_VEHICLE_SECURITY
[21:32:06.118][W][component:490]: tesla_ble_vehicle took a long time for an operation (209 ms)
[21:32:06.121][W][component:493]: Components should block for at most 30 ms
[21:32:09.420][I][tesla_ble_vehicle:372]: [wake vehicle] Executing command.. | attempt 2/5
[21:32:09.470][I][tesla_ble_vehicle:378]: [wake vehicle] Command executed, waiting for response..
[21:32:21.450][I][tesla_ble_vehicle:116]: [data update] Preparing command.. action value 0
[21:32:21.455][I][tesla_ble_vehicle:372]: [data update] Executing command.. | attempt 1/5
[21:32:21.458][I][tesla_ble_vehicle:378]: [data update] Command executed, waiting for response..
[21:32:21.675][I][tesla_ble_vehicle:666]: [data update] Received vehicle status, command completed
[21:32:35.388][I][tesla_ble_vehicle:1004]: Reading INFOTAINMENT, previous_asleep_state_=0, car_just_woken_=1, car_is_charging_=0, Unlocked=0, User=0, fast_poll_if_unlocked_=0
[21:32:35.394][I][tesla_ble_vehicle:1630]: [getChargeState] Adding command to queue (param=0)
[21:32:35.401][I][tesla_ble_vehicle:1630]: [getDriveState] Adding command to queue (param=0)
[21:32:35.405][I][tesla_ble_vehicle:1630]: [getClimateState] Adding command to queue (param=0)
[21:32:35.411][I][tesla_ble_vehicle:1630]: [getClosuresState] Adding command to queue (param=0)
[21:32:35.417][I][tesla_ble_vehicle:116]: [data update] Preparing command.. action value 0
[21:32:35.425][I][tesla_ble_vehicle:372]: [data update] Executing command.. | attempt 1/5
[21:32:35.477][I][tesla_ble_vehicle:378]: [data update] Command executed, waiting for response..
[21:32:35.479][I][ble_rssi_sensor:052]: ESP_GAP_BLE_READ_RSSI_COMPLETE_EVT RSSI: -83
[21:32:35.897][I][tesla_ble_vehicle:666]: [data update] Received vehicle status, command completed
[21:32:35.899][I][tesla_ble_vehicle:116]: [getChargeState] Preparing command.. action value 1
[21:32:35.900][I][tesla_ble_vehicle:372]: [getChargeState] Executing command.. | attempt 1/5
[21:32:35.902][I][tesla_ble_vehicle:1590]: [getChargeState] Building message..
[21:32:35.904][I][tesla_ble_vehicle:378]: [getChargeState] Command executed, waiting for response..
[21:32:36.332][W][tesla_ble_vehicle:1741]: [getChargeState] INFOTAINMENT session invalid, requesting new session info..
[21:32:36.524][I][tesla_ble_vehicle:601]: [067a337097d75212f57ed29495660623] Updated session info for DOMAIN_INFOTAINMENT
[21:32:36.531][E][tesla_ble_vehicle:121]:   MessageStatus:
[21:32:36.536][E][tesla_ble_vehicle:122]:     operation_status: ERROR
[21:32:36.540][E][tesla_ble_vehicle:123]:     signed_message_fault: ERROR_TIME_EXPIRED
[21:32:36.546][E][tesla_ble_vehicle:610]: Received error message from domain DOMAIN_INFOTAINMENT
[21:32:36.551][W][component:490]: ble_client took a long time for an operation (220 ms)
[21:32:36.556][W][component:493]: Components should block for at most 30 ms
[21:32:39.883][I][tesla_ble_vehicle:372]: [getChargeState] Executing command.. | attempt 2/5
[21:32:39.893][I][tesla_ble_vehicle:1590]: [getChargeState] Building message..
[21:32:39.895][I][tesla_ble_vehicle:378]: [getChargeState] Command executed, waiting for response..
[21:32:40.514][I][tesla_ble_vehicle:837]: [getChargeState] Received CarServer OK message, command completed
[21:32:40.520][I][tesla_ble_vehicle:116]: [getDriveState] Preparing command.. action value 3
[21:32:40.525][I][tesla_ble_vehicle:372]: [getDriveState] Executing command.. | attempt 1/5
[21:32:40.531][I][tesla_ble_vehicle:1590]: [getDriveState] Building message..
[21:32:40.544][I][tesla_ble_vehicle:378]: [getDriveState] Command executed, waiting for response..

[PedroKTFC]

I think that looks ok. Do you have all the sensors with values you'd expect?

[patfelst]

Charging works ok with no crashes, and all charging related data is being displayed ok. Uptime 53 mins and counting 🎉

[capof1000]

I dont really know what to thing about.... before finding this discussion, I did spend lot of time to stabilize my code... I was thinking the problem was on my side, I use lvgl which also need ressources.
Yesterday evening I recompile with the repair branch. I remote check now and it has been up all night long and more : +/-46000 seconds uptime. The car has start to charge around 11:50 and now it does sound as stable....esp keep crashing.

Im not sure if the problem is on my code( also good chance) or on your, so to be correlated with other tester...

Im definitely not developper expert, but I did check different ia, and all of then point me to the fact that reducing the Bluetooth traffic would help to stabilize.

[PedroKTFC]

Can you post your yaml and your logs please.

[capof1000]

I m really not sure the problem is on your code pedro, so until other tester repport the same behavior dont spend time on this .... my project is totally"under developemment.... and i did lot of change to fight for stabilization. probably my best version was this one : https://github.com/capof1000/guition-tesla-ble/blob/newteslalib/guition7.yaml.

As fact today i notice that the esp is stable when the car dont charge, but as soon as it is charging.... it keep crashing regulary.

substitutions:
  friendly_name: Capof Gateway HA
  device_name: "guition-esp32-s3-4848s040"
  ble_presence_timeout: "1min"
  tesla_vin: !secret tesla_vin

# --- CONFIGURATION DES SCRIPTS ---
script:
  - id: update_vehicle_image
    then:
      - lvgl.image.update:
          id: vehicle_image_widget
          src: !lambda |-
            if (id(charging_state).state == "Charging") return img_charging;
            if (id(is_charge_flap_open).state) return img_plugged;
            return img_unplugged;

  - id: screen_timeout_timer
    mode: restart
    then:
      - light.turn_on: 
          id: display_backlight
          brightness: !lambda "return id(screen_brightness_config).state / 100.0;"
          transition_length: 0s
      - delay: !lambda "return id(screen_timeout_config).state * 1000;"
      - light.turn_off: 
          id: display_backlight
          transition_length: 1s
      # Suppression de lvgl.pause pour garder le driver graphique actif en tâche de fond

# --- CONFIGURATION CORE ---
esphome:
  name: ${device_name}
  friendly_name: ${friendly_name}
  platformio_options:
    build_flags:
      - -DCONFIG_ARDUINO_LOOP_STACK_SIZE=32768
      - -DCONFIG_BT_BLE_DYNAMIC_ENV_MEMORY=1
  on_boot:
    priority: -100
    then:
      - script.execute: screen_timeout_timer
      - lambda: |-
          auto level = id(logger_level_config).current_option();
          if (level == "NONE") esp_log_level_set("*", ESP_LOG_NONE);
          else if (level == "ERROR") esp_log_level_set("*", ESP_LOG_ERROR);
          else if (level == "WARN") esp_log_level_set("*", ESP_LOG_WARN);
          else if (level == "INFO") esp_log_level_set("*", ESP_LOG_INFO);
          else if (level == "DEBUG") esp_log_level_set("*", ESP_LOG_DEBUG);
          else if (level == "VERBOSE") esp_log_level_set("*", ESP_LOG_VERBOSE);

esp32:
  board: esp32-s3-devkitc-1
  variant: esp32s3
  flash_size: 8MB
  framework:
    type: esp-idf
    sdkconfig_options:
      CONFIG_ESP_TASK_WDT_TIMEOUT_S: "120"
      CONFIG_ESP_MAIN_TASK_STACK_SIZE: "32768"
      CONFIG_BT_BTC_TASK_STACK_SIZE: "16384"
      CONFIG_BT_NIMBLE_MAX_CONNECTIONS: "1"
      CONFIG_BT_NIMBLE_MEM_ALLOC_MODE_EXTERNAL: "y"

psram:
  mode: octal
  speed: 80MHz

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  reboot_timeout: 0s 
  power_save_mode: NONE

api:
  encryption:
    key: !secret api_encryption_key

logger:
  level: INFO

external_components:
  - source: 
      type: git
      url: https://github.com/PedroKTFC/esphome-tesla-ble
      ref: repair

packages:
  base: github://PedroKTFC/esphome-tesla-ble/packages/base.yml@repair
  common: github://PedroKTFC/esphome-tesla-ble/packages/common.yml@repair
  project: github://PedroKTFC/esphome-tesla-ble/packages/project.yml@repair
  client: github://PedroKTFC/esphome-tesla-ble/packages/client.yml@repair

# --- ENTITÉS DE CONFIGURATION ---
number:
  - platform: template
    name: "Poll Drive Period"
    id: poll_drive_period
    entity_category: config
    min_value: 0
    max_value: 600
    step: 10
    initial_value: 60
    unit_of_measurement: "s"
    optimistic: true
    restore_value: true
    on_value:
      then:
        - lambda: "id(tesla_ble_vehicle_id).poll_data_period_ = x;"

  - platform: template
    name: "Screen GTW backlight"
    id: screen_brightness_config
    entity_category: config
    min_value: 55
    max_value: 100
    step: 1
    initial_value: 80
    optimistic: true
    restore_value: true
    on_value:
      then:
        - light.control:
            id: display_backlight
            brightness: !lambda "return x / 100.0;"

  - platform: template
    name: "Screen GTW delay"
    id: screen_timeout_config
    entity_category: config
    min_value: 15
    max_value: 3600
    step: 1
    initial_value: 60
    optimistic: true
    restore_value: true
    on_value:
      then:
        - lvgl.label.update:
            id: delay_value_label
            text: !lambda 'static char buf[20]; sprintf(buf, "%.0f s", x); return buf;'
        - script.execute: screen_timeout_timer

select:
  - platform: template
    name: "Logger Level"
    id: logger_level_config
    entity_category: config
    optimistic: true
    restore_value: true
    options: [NONE, ERROR, WARN, INFO, DEBUG, VERBOSE]
    initial_option: INFO
    on_value:
      then:
        - lambda: |-
            if (x == "NONE") esp_log_level_set("*", ESP_LOG_NONE);
            else if (x == "ERROR") esp_log_level_set("*", ESP_LOG_ERROR);
            else if (x == "WARN") esp_log_level_set("*", ESP_LOG_WARN);
            else if (x == "INFO") esp_log_level_set("*", ESP_LOG_INFO);
            else if (x == "DEBUG") esp_log_level_set("*", ESP_LOG_DEBUG);
            else if (x == "VERBOSE") esp_log_level_set("*", ESP_LOG_VERBOSE);

# --- CONFIGURATION VÉHICULE ---
tesla_ble_vehicle:
  id: tesla_ble_vehicle_id
  vin: ${tesla_vin}
  update_interval: 30s
  poll_charging_period: 30
  poll_data_period: 60
  poll_asleep_period: 0
  post_wake_poll_time: 300
  wake_on_boot: false
  charge_state: { id: tesla_soc }
  charge_current: { id: tesla_amps_raw }
  charging_state:
    id: charging_state
    on_value:
      then:
        - script.execute: update_vehicle_image
  max_soc:
    id: max_soc
    on_value:
      then:
        - if:
            condition: { lambda: return !isnan(x); }
            then:
              - lvgl.arc.update: { id: charge_limit_arc, value: !lambda "return x;" }
              - lvgl.label.update:
                  id: charge_limit_label
                  text: !lambda |-
                    static char buf[10]; sprintf(buf, "%.0f%%", x); return buf;

# --- SENSORS & HARDWARE ---
sensor:
  - platform: wifi_signal
    id: wifi_rssi
    update_interval: 60s
    on_value:
      then:
        - lvgl.image.update:
            id: wifi_icon_widget
            src: !lambda "return (isnan(x) || x < -90) ? img_wifi_none : img_wifi_full;"

  - platform: template
    id: ui_soc_monitor
    update_interval: 10s
    lambda: "return id(tesla_soc).state;"
    on_value:
      then:
        - lvgl.label.update: { id: charge_level_label, text: !lambda 'static char buf[10]; if(isnan(x)) return "-- %"; sprintf(buf, "%.0f %%", x); return buf;' }
        - lvgl.arc.update: { id: charge_level_arc, value: !lambda "return x;" }

  - platform: template
    id: ui_amps_monitor
    update_interval: 10s
    lambda: "return id(tesla_amps_raw).state;"
    on_value:
      then:
        - lvgl.label.update: { id: amps_value_label, text: !lambda 'static char buf[10]; if(isnan(x)) return "-- A"; sprintf(buf, "%.0f A", x); return buf;' }
        - lvgl.slider.update: { id: amps_slider, value: !lambda "return x;" }

output:
  - platform: ledc
    id: backlight_output
    pin: GPIO38

light:
  - platform: monochromatic
    id: display_backlight
    output: backlight_output

spi:
  - id: lcd_spi
    clk_pin: GPIO48
    mosi_pin: GPIO47

i2c:
  id: touchscreen_bus
  sda: GPIO19
  scl: { number: 45, ignore_strapping_warning: true }

display:
  - platform: st7701s
    id: tft_display
    dimensions: { width: 480, height: 480 }
    color_order: RGB
    cs_pin: 39
    de_pin: 18
    hsync_pin: 16
    vsync_pin: 17
    pclk_pin: 21
    pclk_frequency: 10MHz 
    update_interval: 50ms
    init_sequence:
      - 1
      - [0xFF, 0x77, 0x01, 0x00, 0x00, 0x10]
      - [0xCD, 0x00]
    data_pins:
      red: [11, 12, 13, 14, 0]
      green: [8, 20, 3, 46, 9, 10]
      blue: [4, 5, 6, 7, 15]

touchscreen:
  - platform: gt911
    id: tft_touch
    display: tft_display
    on_touch:
      - then:
          - script.execute: screen_timeout_timer
          - logger.log: "DEBUG: Tactile detecte - Relance du timer"

font:
  - file: { type: gfonts, family: Roboto }
    id: font_main
    size: 24

image:
  - { file: "images/charger_unplugged.jpg", id: img_unplugged, type: RGB565 }
  - { file: "images/charger_plugged.jpg", id: img_plugged, type: RGB565 }
  - { file: "images/charger_charging.jpg", id: img_charging, type: RGB565 }
  - { file: "images/parametres.jpg", id: img_params, type: RGB565 }
  - { file: "images/wifi/pas-de-wifi.jpg", id: img_wifi_none, type: RGB565 }
  - { file: "images/wifi/signal-wi-fi-75-100.jpg", id: img_wifi_full, type: RGB565 }

# --- LVGL ---
lvgl:
  displays: tft_display
  buffer_size: 5% 
  pages:
    - id: main_page
      widgets:
        - image: { id: vehicle_image_widget, src: img_unplugged, align: CENTER, zoom: 0.75 }
        - arc:
            id: charge_limit_arc
            align: CENTER
            width: 320
            height: 320
            start_angle: 150
            end_angle: 30
            arc_width: 12
            adjustable: true
            on_value:
              then:
                - homeassistant.service:
                    service: number.set_value
                    data:
                      entity_id: number.${device_name}_charge_limit
                      value: !lambda "return to_string((int)x);"
        - arc:
            id: charge_level_arc
            align: CENTER
            width: 320
            height: 320
            start_angle: 150
            end_angle: 30
            arc_width: 12
            arc_opa: 0%
            indicator: { arc_color: 0x2ECC71 }
        - label: { id: charge_limit_label, align: BOTTOM_LEFT, x: 40, y: -25, text_font: font_main, text_color: 0x00AEEF }
        - label: { id: charge_level_label, align: BOTTOM_MID, y: -25, text_font: font_main, text_color: 0x2ECC71 }
        - label: { id: amps_value_label, align: BOTTOM_RIGHT, x: -40, y: -25, text_font: font_main, text_color: 0xF1C40F }
        - slider:
            id: amps_slider
            width: 20
            height: 250
            align: RIGHT_MID
            x: -20
            min_value: 5
            max_value: 32
            on_value:
              then:
                - homeassistant.service:
                    service: number.set_value
                    data:
                      entity_id: number.${device_name}_current_limit
                      value: !lambda "return to_string((int)x);"
        - obj:
            height: 60
            width: 100%
            align: TOP_MID
            bg_opa: 0%
            widgets:
              - button:
                  width: 60
                  height: 50
                  align: LEFT_MID
                  on_click:
                    then:
                      - lvgl.page.show: settings_page
                  widgets: [ image: { src: img_params, align: CENTER } ]
              - image: { id: wifi_icon_widget, src: img_wifi_none, align: RIGHT_MID, x: -15 }

    - id: settings_page
      widgets:
        - obj:
            width: 100%
            height: 100%
            bg_color: 0x1A1A1A
            widgets:
              - button:
                  align: TOP_RIGHT
                  on_click:
                    then:
                      - lvgl.page.show: main_page
                  widgets: [ label: { text: "X", text_font: font_main, align: CENTER } ]

              - label: { text: "Drive Poll:", align: TOP_MID, y: 20, text_color: 0xFFFFFF }
              - slider:
                  align: TOP_MID
                  y: 45
                  width: 60%
                  max_value: 600
                  on_value: 
                    then: 
                      - number.set: { id: poll_drive_period, value: !lambda "return x;" }
                      - lvgl.label.update: { id: dr_v, text: !lambda 'static char buf[10]; if(x==0) return "OFF"; sprintf(buf, "%.0f s", x); return buf;' }
              - label: { id: dr_v, text: "60 s", align: TOP_RIGHT, x: -20, y: 45, text_color: 0x00FFFF }

              # Screen
              - label: { text: "Brightness:", align: TOP_MID, y: 100, text_color: 0xFFFFFF }
              - slider:
                  align: TOP_MID
                  y: 125
                  width: 80%
                  on_value:
                    then:
                      - number.set: { id: screen_brightness_config, value: !lambda "return x;" }

              - label: { text: "Timeout:", align: TOP_MID, y: 170, text_color: 0xFFFFFF }
              - slider:
                  align: TOP_MID
                  y: 195
                  width: 80%
                  on_value:
                    then:
                      - number.set: { id: screen_timeout_config, value: !lambda "return x;" }
              - label: { id: delay_value_label, text: "60 s", align: TOP_MID, y: 220, text_color: 0xFFFFFF }

              - dropdown:
                  align: BOTTOM_MID
                  y: -10
                  width: 200
                  options: [NONE, ERROR, WARN, INFO, DEBUG, VERBOSE]
                  on_value:
                    then:
                      - select.set:
                          id: logger_level_config
                          option: !lambda |-
                            static const char* opts[] = {"NONE", "ERROR", "WARN", "INFO", "DEBUG", "VERBOSE"};
                            return opts[x];

[top-gun]

You do most certainly run out of ram. Your display needs a lot pf ram, lgvl needs a lot of ram, and ble is a huge ram consumer, too. You run this on a simple esp32s3 without param, though.

the solution is simple: Either distribute the display and the ble control to seperate esps, or get another esp32s3 with psram, then tine your applications to put as much usage on the psram as possible. 340kb is 60% of the 640kb that Bill Gates made history with.

[capof1000]

Actually, the hardware I use (Guition ESP32-S3-4848S040) is equipped with 8MB of Octal PSRAM, so I’m not limited to the internal 512KB SRAM.

However, you are right about the RAM pressure. Even with PSRAM, ESPHome and BLE stacks are very demanding. To handle this, I have already implemented several optimizations in my configuration:

External Memory Allocation: I've enabled CONFIG_BT_NIMBLE_MEM_ALLOC_MODE_EXTERNAL to force the Bluetooth stack to use the PSRAM.

Stack Size Tuning: I've try to increased the Arduino loop and Bluetooth task stack sizes to prevent overflows.

LVGL Buffering: I'm using a small 5-10% display buffer to keep some internal SRAM free for critical real-time tasks.

[PedroKTFC]

If I were you, I would start with the basic configuration and confirm that works and then incrementally add your elements each time confirming they're working.

[top-gun]

What the man says, plus: You set special options for Nimble, but ESP IDF uses Bluedroid with the ESP32-S3. I don‘t think they have any effect.

[nagyrobi]

Yes, ESPHome doesn't use NimBLE.
Using PSRAM instead of RAM is not just a matter of preference. Components must support it and handle it accordingly, because it's slower than RAM, so not everything can be just shelved over.

[patfelst]

guys is this crashing problem as simple as you must have an ESP32-S3 with a minimum amount of PSRAM? Atom S3 lite has no PSRAM. My board never crashes and has 8MB PSRAM (QSPI). Uptime is over 25 hrs for me now!

[PedroKTFC]

It might be. I have a draft change that fixes the buffer overflow by expanding the protobuf buffer by only 7 bytes. I hope that the almost trivial extra use will not cause any crashes but we'll have to see.

[nagyrobi]

An interesting fix in the new beta: esphome/esphome#12696 (comment)

[PedroKTFC]

I've now updated main to 2026.1.B so closing this discusssion.