v0.16.1

docs/FLOW.md

@@ -14,6 +14,7 @@ Flow is an authoring/orchestration layer. It does not replace the thermostat, sc
 
 ## Existing control domains remain authoritative
 
+- Optional `zone_thermostat` fields `heat_anticipation_c` (0–2.5 °C) and `standby_offset_c` (0.5–8 °C) persist into the target Zone when the Flow action executes. The regulator enters a hysteretic low-GREE-setpoint *coasting* state when room temperature reaches `target - heat_anticipation_c`, and resumes full setpoint heating once it falls another 0.4 °C. Coasting changes the requested GREE temperature and smart fan/Quiet behavior, **never the indoor unit power**; pre-existing compressor protection and multisplit shared-OFF flow gates remain unchanged. For older Flows the fields are absent and the previous regulator behavior remains.
 - `zone_thermostat` writes the existing persistent Zone intent and wakes the normal thermostat cycle. `power=false` sends an explicit physical OFF to the assigned unit but does **not** change the persistent Zone `enabled` flag; Zone enable/disable remains an administrative control gate. A concrete Flow mode (`heat`/`cool`) is also written with the OFF frame so a stale device `dry`/`fan` mode is not retained; Flow `auto` remains an ownership policy and is never mapped to physical GREE Auto on OFF. While a zone is owned by `automation.flow`, the global outdoor-assist bias is suppressed so the Flow's own room-temperature thresholds remain authoritative. It can also issue one-shot granular vertical/horizontal louver commands to the assigned unit; these auxiliary fields do not take over thermostat ownership.
 - `group_action` calls the existing `control_group` path, including custom group targets.
 - `device_action` uses the existing `DeviceCommand` / automatic-device path.