-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Move climate intent to homeassistant integration #139371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
45a3305
to
6b6e788
Compare
If the intent is going to be used for non-climate entities, should it e renamed to |
Technically yes, but then we will have breaking changes in a lot of places. |
* Move climate intent to homeassistant integration * Move get temperature intent to intent integration * Clean up old test
Breaking change
Proposed change
In preparation for #139221 this PR moves the
HassClimateGetTemperature
intent to theintent
integration.This is needed because the intent will straddle both the
climate
andsensor
integrations (when #139221 is updated and merged) since the current temperature of an area can come from a sensor or a thermostat.Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
.To help with the load of incoming pull requests: