jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-28 11:46:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Tweaks climate cleanup blog post

Browse Source
This commit is contained in:
Franck Nijhof 2019-07-03 09:30:09 +02:00 committed by GitHub
parent f1edc57a3d
commit c54b88b486
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/blog/2019-07-03-climate-cleanup.md
View File

@ -9,15 +9,15 @@ _This post is about the upcoming changes for the Home Assistant climate integrat
Starting with Home Assistant 0.96, we're shipping a big architectural clean up of our climate integrations. This effort is lead by Pascal Vizeli. Starting with Home Assistant 0.96, we're shipping a big architectural clean up of our climate integrations. This effort is lead by Pascal Vizeli.
Over the years, the climate integration has grown from being a simple place for thermostats, to hosting ACs, heatpumps and ventilation systems. During this growth, mistakes have been made which resulted in a confusing and hard to work with design. Work is underway to get this all cleaned up and we're going to ship this in Home Assistant 0.96. Over the years, the climate integration has grown from being a simple place for thermostats to hosting ACs, heat pumps and ventilation systems. During this growth, mistakes have been made which resulted in a confusing and hard to work with design. Work is underway to get this all cleaned up and we're going to ship this in Home Assistant 0.96.
The biggest mistake we made is that we conflated operating and operation mode. Operation mode is what you want your thermostat to do, for example heat the house to 19 °C. Operating mode is what the thermostat is _currently_ doing. Is it heating because the house is too cold? Or did it already reach target temperature and is it currnetly idle. The biggest mistake we made is that we conflated operating and operation mode. Operation mode is what you want your thermostat to do, for example, heat the house to 19 °C. The operating mode is what the thermostat is _currently_ doing. Is it heating because the house is too cold? Or did it already reach the target temperature and is it currently idle?
On top of that, we've noticed that a lot of integrations overload operation mode with a wide range of delightful options like "eco", "comfort", "boost" or "sleep". After carefully analyzing all the different climate systems out there, we have come to the conclusion that these alternative operation modes are variations of the existing operation modes (heat, cool, heat-cool), but might have different target temperature ranges or try to heat/cool at a slower pace to conserve energy. On top of that, we've noticed that a lot of integrations overload operation mode with a wide range of delightful options like "eco", "comfort", "boost" or "sleep". After carefully analyzing all the different climate systems out there, we have come to the conclusion that these alternative operation modes are variations of the existing operation modes (heat, cool, heat-cool), but might have different target temperature ranges or try to heat/cool at a slower pace to conserve energy.
To support as many different thermostats as possible, we have decided to allow climate devices to specify a new "preset" mode that they are operating under. This will cover hold mode, away mode, or any custom operation mode that a thermost wants to include. To support as many different thermostats as possible, we have decided to allow climate devices to specify a new "preset" mode that they are operating under. It covers hold mode, away mode, or any custom operation mode that a thermostat includes.
You might wonder, why go for a preset instead of allowing to overload operation mode? On first glance it might seem fine for an integration to list the possible options and the current chosen option, easy to make a UI. But that's not the only way Home Assistant is used. We are also serving as a single place to control any thermostat for external systems like Google Assistant or Amazon Alexa. And they have a limited set of operation modes they expect. You might wonder, why go for a preset instead of allowing to overload operation mode? On first glance, it might seem fine for an integration to list the possible options and the current chosen option, easy to make a UI for. However, that's not the only way Home Assistant is used. We are also serving as a single place to control any thermostat for external systems like Google Assistant or Amazon Alexa. They have a limited set of operation modes they expect.
A gist of the changes: A gist of the changes:
@ -27,7 +27,7 @@ A gist of the changes:
- `turn_off` and `turn_on` have been removed. Instead, integrations should expose two HVAC modes, one of them being `HVAC_MODE_OFF`. - `turn_off` and `turn_on` have been removed. Instead, integrations should expose two HVAC modes, one of them being `HVAC_MODE_OFF`.
- Property names have been aligned, - Property names have been aligned,
If you are a maintainer of an integration that has a climate platform, or maintain a custom compnoent that has one, make sure you [follow the pull request](https://github.com/home-assistant/home-assistant/pull/23899) and test your integration during the beta to make sure that it works like expected. If you are a maintainer of an integration that has a climate platform or maintain a custom component that has one, make sure you [follow the pull request](https://github.com/home-assistant/home-assistant/pull/23899) and test your integration during the beta to make sure that it works like expected.
<div id='discourse-comments'></div> <div id='discourse-comments'></div>