Parameter not updated from config - start_sensing_delay keeps staying at default value

[Shogoki]

The problem

I do have a Shell Plus 2PM, which is flashed with ESPHOME.
I wanted to use a current_based cover here. When I first flashed i did not set the start_sensing_delay parameter.
As it was not working with my motor, like this. I wanted to update the start_sensing_delay parameter.

I changed it in the config and flashed the new firmware OTA.

I did try different values for start_sensing_delay and could not see any difference in the behaviour.
Now, when i did connect to the ESP using esphome run I saw in the logs, that the Value does not seem to get updated.
The Log is outputting the config for my cover, but still shows the default value of 0.5s [11:39:44][C][current_based.cover:153]: Start sensing delay: 0.5s

Not sure If I am doing something wrong, or if this is a bug, that the config does not get updated?

Any help would be much appreciated.

Which version of ESPHome has the issue?

2024.4.0

What type of installation are you using?

Docker

Which version of Home Assistant has the issue?

n/a

What platform are you using?

ESP32-IDF

Board

esp32doit-devkit-v1

Component causing the issue

cover current_based

Example YAML snippet

cover:
  - platform: current_based 
    start_sensing_delay: 3.0s
    name: "Wohnzimmer Rolladen links"
    id: rolladen
    open_sensor: current_b 
    open_moving_current_threshold: 0.5
    open_obstacle_current_threshold: 0.8

    open_action:
      - switch.turn_on: relay_2
    open_duration: ${open_duration}

    close_sensor: current_a 
    close_moving_current_threshold: 0.5
    close_obstacle_current_threshold: 0.8

    close_action:
      - switch.turn_on: relay_1
    close_duration: ${close_duration}

    stop_action:
      - switch.turn_off: relay_1
      - switch.turn_off: relay_2

Anything in the logs that might be useful for us?

[11:39:44][C][current_based.cover:136]: Endstop Cover 'Wohnzimmer Rolladen links'
[11:39:44][C][current_based.cover:137]:   Open Sensor 'Output 1 Current'
[11:39:44][C][current_based.cover:137]:     Device Class: 'current'
[11:39:44][C][current_based.cover:137]:     State Class: 'measurement'
[11:39:44][C][current_based.cover:143]:     Device Class: 'current'
[11:39:44][C][current_based.cover:143]:     State Class: 'measurement'
[11:39:44][C][current_based.cover:143]:     Unit of Measurement: 'A'
[11:39:44][C][current_based.cover:143]:     Accuracy Decimals: 2
[11:39:44][C][current_based.cover:144]:   Close moving current threshold: 0.50000000000A
[11:39:44][C][current_based.cover:146]:   Close obstacle current threshold: 0.80000001192A
[11:39:44][C][current_based.cover:148]:   Close Duration: 28.0s
[11:39:44][C][current_based.cover:149]: Obstacle Rollback: 10.0%
[11:39:44][C][current_based.cover:153]: Start sensing delay: 0.5s
[11:39:44][C][current_based.cover:154]: Malfunction detection: YES

Additional information

No response

[Shogoki]

I realized the issue stems from the new firmware not being loaded.
I think it is the same as #5001