Fix state being cleared on disconnect with deep sleep esphome devices

[bdraco]

Proposed change

Fix state being cleared on disconnect with deep sleep esphome devices

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes ESPhome deep sleep sensor values get 'unavailable' as soon as api is not connected #90923
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @OttoWinter, @jesserockz, mind taking a look at this pull request as it has been labeled with an integration (esphome) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of esphome can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign esphome Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[bdraco]

Needs more testing but I'm too tired to build a deep sleep esphome device so will have to do it tomorrow

[bdraco]

Tested with

---
esphome:
  name: deepsleep


deep_sleep:
  run_duration: 10s
  sleep_duration: 1min
  
esp32:
  board: nodemcu-32s

api:
  id: api_server


# WiFi connection, correct these
# with values for your WiFi.
wifi:
  ssid: SNIP
  password: SNIP

logger:
#  level: VERBOSE

# Enable Home Assistant API.

# Enable over-the-air updates.
ota:

# Enable Web server.
#web_server:
#  port: 80

# Sync time with Home Assistant.
time:
  - platform: homeassistant
    id: homeassistant_time

# Text sensors with general information.

# Sensors with general information.
sensor:
  # Uptime sensor.
  - platform: uptime
    name: deepsleep Uptime
  - platform: template
    name: deepsleep free Memory
    lambda: return heap_caps_get_free_size(MALLOC_CAP_INTERNAL);
    unit_of_measurement: 'B'
    state_class: measurement
  - platform: wifi_signal
    name: "WiFi Signal Sensor"
    update_interval: 2s

[Kimotu]

Thanks for the fast fix. Just installed 2023.4.1 and dashboard shows last value again till next sensor update. 🙂