New 'Duty Time' sensor component

[dudanov]

What does this implement/fix?

The component Duty Time is used to calculate the operating time of something, for example, a light bulb in seconds.

It is configured by one of the logical sources: a binary_sensor or a lambda function.

The main loop checks the source for a change in the input signal. The auxiliary interval loop update() of the PollingComponent class periodically updates the sensor.

If necessary, it is possible to add an auxiliary sensor to record the time of the last switch-on.

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

Related issue or feature (if applicable): fixes

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

Test Environment

• ESP32
• ESP32 IDF
• ESP8266
• RP2040

Example entry for config.yaml:

# Example
# Test "object"
switch:
  - platform: template
    name: Test Object
    id: my_switch
    optimistic: on

# binary_sensor
binary_sensor:
  - platform: template
    id: my_binary_sensor
    name: Object State
    lambda: "return id(my_switch).state;"

# Reset Button
button:
  - platform: template
    name: Reset Duty Time
    on_press:
      sensor.duty_time.reset: id_duty

# duty_time component
sensor:
  - platform: duty_time
    id: id_duty
    name: Duty Time
    restore: on
    last_time:
      name: Last Duty Time
    # binary_sensor as logical source
    sensor: my_binary_sensor
    # .. EOR lambda
    #lambda: "return id(my_switch).state;"

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 @dudanov,
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 = ["@dudanov"]

And run script/build_codeowners.py

_{^{(message by NeedsCodeownersLabel)}}

[SeByDocKy]

Sound an interesting addition. Can be useful for example to build a kind of "historical stats" if you can add a "period" field to compute the ratio. More adding an action to "reset" the sensor would be great too