Deprecate Daikin yaml-support

[fredrike]

Breaking change

Configuration via YAML for the daikin integration is deprecated and will become invalid in release 0.113.0. All configuration should be done via the Integrations tab in the GUI. Users should remove the daikin configuration YAML section before 0.113.0 is released.

Proposed change

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:

DEPRICATED (YAY)

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Add config options to Daikin and add support for Daikin zeroconf discovery #35507
• 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
• 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

[MartinHjelmare]

Thanks!

For the future, please don't squash commits after review has started to make it easier for readers to track changes.

[MartinHjelmare]

Please update the breaking change paragraph with that the user should do to cope with the breaking change.

[MartinHjelmare]

I updated the breaking change paragraph to better explain the breaking change.

[charlietomo]

As an end user it would be very helpful if a breaking change such as this had instructions and implications for a user. "All configuration should be done via the Integrations tab in the GUI." is very generic - and not that helpful for someone who has always configured via YAML.

• Before or after upgrading to 113?
• What happens to automations using the old Daikin setup?
• What happens to homekit integrations that use Daikin?
• What is the process to ensure a bunch of reconfiguration isn't needed?

It may be obvious for those that are always working with Home Assistant, but for those of us that have used it for years but don't fiddly daily, a little more instruction on breaking changes would be really useful.

[frenck]

@charlietomo That is more a fitting comment on the release notes PR.

Nevertheless, the answer is almost always the same, unless stated otherwise. YAML configuration is imported and can be safely removed. This import was already the case in previous releases, nothing changes.

[charlietomo]

@charlietomo That is more a fitting comment on the release notes PR.

Nevertheless, the answer is almost always the same, unless stated otherwise. YAML configuration is imported and can be safely removed. This import was already the case in previous releases, nothing changes.

Noted - where would I find that PR?

[frenck]

@charlietomo Nowhere, as there is no release being prepared at this time.

[jamesgoodhouse]

Is there a reason this was deprecated and removed? Seems like it's a step backwards to force people to configure manually through the UI versus being able to codify their configuration.

[frenck]

@jamesgoodhouse https://www.home-assistant.io/blog/2020/04/14/the-future-of-yaml/