Clarify auto mode

balloob · balloob · commit d3b515593fa4 · 2019-07-16T23:48:01.000-07:00
diff --git a/source/_posts/2019-07-17-release-96.markdown b/source/_posts/2019-07-17-release-96.markdown
@@ -37,10 +37,11 @@ For a breakdown of what was driving the change, [check our blog post on the dev
 The following things have been changed:
 
  - `operation_mode` has been renamed to `hvac_mode` to emphasize what the mode is for.
- - The state of a climate entity is now always equal to the hvac mode.
+ - We split HVAC mode `auto` into `auto` and `heat_cool`. If it's `heat_cool`, the user has set a temperature range the device has to use heating and cooling to stay within. Auto mode is now limited to devices that are running on a schedule or AI.
+ - The state of a climate entity is now always equal to the HVAC mode.
  - `hvac_action` is introduced for integrations that know the current action: heating, cooling, idle.
  - `set_away_mode` and `set_hold_mode` have been merged into `set_preset_mode`. So instead of `turn_away_mode_on()`, we will now call `set_preset_mode("away")`.
- - The `is_on` property has been removed. If a device is able to turn off, it should include the hvac mode `HVAC_MODE_OFF`.
+ - The `is_on` property has been removed. If a device is able to turn off, it should include the HVAC mode `HVAC_MODE_OFF`.
  - Property names have been aligned, anything ending with "_list" is now named "_modes".
  - Integrations are only allowed to represent functionality that is present in the API. It is not allowed to add your own fake away mode.
 
