Add tado zone binary sensors

[Noltari]

Breaking change

Tado zone sensors will be replaced by their corresponding binary_sensors. Therefore, users will have to update lovelace panels, scripts and automations referring to the following sensors by their corresponding binary sensor (replace sensor with binary_sensor)

• sensor.%TADO_ZONE%_early_start will be replaced by binary_sensor.%TADO_ZONE%_early_start
• sensor.%TADO_ZONE%_link will be replaced by binary_sensor.%TADO_ZONE%_link
• sensor.%TADO_ZONE%_open_window will be replaced by binary_sensor.%TADO_ZONE%_open_window
• sensor.%TADO_ZONE%_overlay will be replaced by binary_sensor.%TADO_ZONE%_overlay
• sensor.%TADO_ZONE%_power will be replaced by binary_sensor.%TADO_ZONE%_power

The following state attributes have been removed:

• sensor.%TADO_ZONE%_overlay: termination
• sensor.%TADO_ZONE%_open_window: open_window_attr

Proposed change

Use binary sensors where appropriate (for Tado Zones) instead of normal sensors.

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)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
tado:
  username: !secret tado_username
  password: !secret tado_password

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Tado: use proper variable name to avoid confusion #44571 should be merged first and then rebase this PR
• Link to documentation pull request: Add Binary Sensor to Tado integration home-assistant.io#16076

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
• 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[michaelarnauts]

You'll need to rebase since the changes from #44571 are also in this PR.

[Noltari]

You'll need to rebase since the changes from #44571 are also in this PR.

@michaelarnauts done :)

[michaelarnauts]

This looks fine, but I'm not really sure what the policy is regarding the description of the breaking change.

[MartinHjelmare]

Please be explicit when naming the entity types that are breaking in the breaking change paragraph. Also briefly explain what users need to do to cope with the breaking change.

[Noltari]

Please be explicit when naming the entity types that are breaking in the breaking change paragraph. Also briefly explain what users need to do to cope with the breaking change.

Done:

Breaking change

Tado zone sensors will be replaced by their corresponding binary_sensors:

• sensor.%TADO_ZONE%_early_start will be replaced by binary_sensor.%TADO_ZONE%_early_start
• sensor.%TADO_ZONE%_link will be replaced by binary_sensor.%TADO_ZONE%_link
• sensor.%TADO_ZONE%_open_window will be replaced by binary_sensor.%TADO_ZONE%_open_window
• sensor.%TADO_ZONE%_overlay will be replaced by binary_sensor.%TADO_ZONE%_overlay
• sensor.%TADO_ZONE%_power will be replaced by binary_sensor.%TADO_ZONE%_power

[MartinHjelmare]

Please also mention what users should do to cope with this change. Eg update these entity ids in automations and scripts that depend on the ids.

[Noltari]

Please also mention what users should do to cope with this change. Eg update these entity ids in automations and scripts that depend on the ids.

Done:

Breaking change

Tado zone sensors will be replaced by their corresponding binary_sensors. Therefore, users will have to update lovelace panels, scripts and automations referring to the following sensors by their corresponding binary sensor (replace sensor with binary_sensor):

• sensor.%TADO_ZONE%_early_start will be replaced by binary_sensor.%TADO_ZONE%_early_start
• sensor.%TADO_ZONE%_link will be replaced by binary_sensor.%TADO_ZONE%_link
• sensor.%TADO_ZONE%_open_window will be replaced by binary_sensor.%TADO_ZONE%_open_window
• sensor.%TADO_ZONE%_overlay will be replaced by binary_sensor.%TADO_ZONE%_overlay
• sensor.%TADO_ZONE%_power will be replaced by binary_sensor.%TADO_ZONE%_power

[MartinHjelmare]

Please try to avoid squashing commits after review has started, to make it easier for readers to track changes.

[Noltari]

Please try to avoid squashing commits after review has started, to make it easier for readers to track changes.

Ok, I will avoid it in the future.
Excuse me but it's the usual procedure in other projects.

[frenck]

Not in this project. We squash on merge, making the PR clean in the end. Individual commits are trackable/more visible to see what has been changed over time in the PR during a review.

[MartinHjelmare]

Looks good!

[MartinHjelmare]

Please add the Binary Sensor ha_category to the docs page and link the docs PR in this PR description.

https://www.home-assistant.io/integrations/tado/

[Noltari]

Please add the Binary Sensor ha_category to the docs page and link the docs PR in this PR description.

https://www.home-assistant.io/integrations/tado/

Done: home-assistant/home-assistant.io#16076

[MartinHjelmare]

Thanks!