v0.14.2

docs/API.md

@@ -1,6 +1,6 @@
 # GREE Controller API reference
 
-HTTP and WebSocket API for GREE Controller **0.14.1**.
+HTTP and WebSocket API for GREE Controller **0.14.2**.
 
 [← Main documentation](../README.md)
 
@@ -232,7 +232,7 @@ Response:
 {
   "status": "ok",
   "name": "gree-controller",
-  "version": "0.14.1",
+  "version": "0.14.2",
   "uptime_seconds": 1234,
   "control_ready": true,
   "time": "2026-08-30T06:54:00Z"
@@ -295,7 +295,7 @@ Returns the initial Web UI snapshot:
   "control_plan": {"generated_at": "2026-09-04T08:00:00Z", "zones": [], "rules": []},
   "control_plan_revision": 42,
   "system": {
-    "version": "0.14.1",
+    "version": "0.14.2",
     "uptime_seconds": 1234,
     "auth_required": false,
     "control_ready": true,
@@ -1654,6 +1654,12 @@ Additional Flow condition blocks are `house_mode`, `device_state`, `zone_state`,
 
 
 
+## Swing control across manual, thermostat and automation surfaces — 0.14.2
+
+Local device control exposes vertical (`swing_vertical`) and horizontal (`swing_horizontal`) swing independently. Thermostat zone UI and the bundled Home Assistant zone climate entity expose the same auxiliary controls when the assigned device reports support; changing swing does not hand thermostat ownership to manual control.
+
+Legacy direct-device automations accept optional `swing_vertical` and `swing_horizontal` action fields. Visual Flow exposes both axes in `device_action` and `zone_thermostat` actions and in device-state conditions. A `zone_thermostat` Flow using swing compiles to an automation rather than a native schedule so the auxiliary command is preserved. Swing remains outside the thermostat's continuously regulated fan/temperature outputs.
+
 ## Split/multisplit installations and energy comparison — 0.14.1
 
 Installation configuration endpoints: