[homeassistant] Native number entity import and control

[landonr]

What does this implement/fix?

• new Home Assistant Number which reads the state, min, max and step from Home Assistant. Syncs updates between ESPHome and Home Assistant.
• new Home Assistant Component which makes reading and writing to Home Assistant easier. I use it for covers, lights, numbers, and switches here https://github.com/landonr/esphome-components/tree/main/components/homeassistant_component

I'm adding the number component which I tested using a graphical display menu config

Home Assistant Component

• next_api_publish_: prevents publishing the next value to the API, used to prevent publishing duplicate values back to the api when the entity changes from the api
• can_update_from_api: updates from the api are ignored for a second after the device publishes to the API, this is used so the updates don't recursively continue
• ignore_api_updates_with_seconds: ignore updates before publishing to update can_update_from_api

all of this is used in combination to keep the device's entity in sync with the API as close as possible. This works for most devices like switches, numbers, covers, but it can be a bit buggy for more complicated entities like Lights.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#3942

Test Environment

• ESP32
• ESP32 IDF
• ESP8266
• RP2040
• BK72xx
• RTL87xx

Example entry for config.yaml:

number:
  - platform: homeassistant
    id: my_number
    name: "My Number"
    entity_id: "number.bedroom_bass"
    on_value:
      then:
        lambda: 'ESP_LOGI("number", "value: %f", x);'

graphical_display_menu:
  id: my_graphical_display_menu
...
  items:
    - type: number
      text: 'My Number'
      format: '%.2f'
      number: my_number

Checklist:

• The code change is tested and works locally.
• Tests have been added to verify that the new code works (under tests/ folder).

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

• Documentation added/updated in esphome-docs.

[probot-esphome]

Hey there @OttoWinter, mind taking a look at this pull request as it has been labeled with an integration (homeassistant) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[probot-esphome]

Hey there @landonr,
Thanks for submitting this pull request! Can you add yourself as a codeowner for this integration? This way we can notify you if a bug report for this integration is reported.
In __init__.py of the integration, please add:

CODEOWNERS = ["@landonr"]

And run script/build_codeowners.py

_{^{(message by NeedsCodeownersLabel)}}

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.94%. Comparing base (4d8b5ed) to head (8b5cda2).
Report is 1122 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #6455      +/-   ##
==========================================
+ Coverage   53.70%   53.94%   +0.23%     
==========================================
  Files          50       50              
  Lines        9408     9655     +247     
  Branches     1654     1705      +51     
==========================================
+ Hits         5053     5208     +155     
- Misses       4056     4124      +68     
- Partials      299      323      +24     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nagyrobi]

I think that the attributes like min_value, max_value and step should be automatically retrieved from HA, and not re-configured here. Someone may configure them differently on the sides which will likely cause malfunctions.

[landonr]

I think that the attributes like min_value, max_value and step should be automatically retrieved from HA, and not re-configured here. Someone may configure them differently on the sides which will likely cause malfunctions.

I think I agree, I'll make the changes and see how it works. thanks!

[landonr]

I think that the attributes like min_value, max_value and step should be automatically retrieved from HA, and not re-configured here. Someone may configure them differently on the sides which will likely cause malfunctions.

works great, nice suggestion thanks

[landonr]

@nagyrobi can you take another look

[jesserockz]

I removed all of the timeout stuff and also added a simple value == state check in the state callback to not do anything if it is the same state.

We can add more protections back in later if needed, but in my basic number testing, it was fine.

[probot-esphome]

Hey there @esphome/core, mind taking a look at this pull request as it has been labeled with an integration (homeassistant) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}