Add a warning that honeywell/EU is to be deprecated #23469
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
The honeywell component actually contains two mutually-exclusive integrations, based upon either the
somecomfort
(US) orevohome-client
(EU) client libraries. Theevohome
functionality is better provided in the evohome component, which uses the same client library.This PR will add a warning to users of the
honeywell
component that support for EU-based systems is deprecated in favour of theevohome
component.This warning does not apply to / will not be seen by users of US-based systems.
Related issue (if applicable): None
Pull request in home-assistant.io with documentation (if applicable): None
Checklist:
tox
. Your PR cannot be merged unless tests passIf user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
requirements
in the manifest (example).requirements_all.txt
by runningscript/gen_requirements_all.py
..coveragerc
.If the code does not interact with devices: N/A