v0.14.1

docs/API.md

@@ -1,6 +1,6 @@
 # GREE Controller API reference
 
-HTTP and WebSocket API for GREE Controller **0.14.0**.
+HTTP and WebSocket API for GREE Controller **0.14.1**.
 
 [← Main documentation](../README.md)
 
@@ -232,7 +232,7 @@ Response:
 {
   "status": "ok",
   "name": "gree-controller",
-  "version": "0.14.0",
+  "version": "0.14.1",
   "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.0",
+    "version": "0.14.1",
     "uptime_seconds": 1234,
     "auth_required": false,
     "control_ready": true,
@@ -1653,6 +1653,20 @@ Existing Flow updates require `expected_revision`. A mismatched revision returns
 Additional Flow condition blocks are `house_mode`, `device_state`, `zone_state`, `group_state`, `night_mode`, `ha_attribute`, `ha_available`, `constant` and `shared_input`, alongside weekday/time/date, temperature, Home Assistant state/numeric and AND/OR/NOT blocks. `device_state` can inspect enabled/online/power/mode/fan/swing/quiet/turbo/light/air/xfan/health/sleep state. The editor ships 37 categorized editable templates covering comfort, energy, safety, night, reliability, Home Assistant heat-source coordination and advanced multi-branch logic. The template UI adds search, favorites/recent history, a graph preview and runtime requirement checks; shared inputs expose usage links and HA-backed inputs can be tested against live entity state.
 
 
+
+## Split/multisplit installations and energy comparison — 0.14.1
+
+Installation configuration endpoints:
+
+- `GET|POST /api/device-groups`
+- `GET|PUT|DELETE /api/device-groups/{id}`
+
+A device group represents one physical split or multisplit installation. It contains one or more indoor `device_ids`, an optional shared GREE Cloud energy device or Home Assistant cumulative-energy entity, and an optional member device used as the shared outdoor-temperature source. One device may belong to only one installation.
+
+Energy history accepts either a device ID or `group:<installation-id>` as a target. The Web UI can request several targets in parallel and overlay them on one chart. `compare=previous_day|previous_period|previous_year` shifts the requested range for period comparison; `compare=none` disables comparison. Daily buckets are presented as calendar dates.
+
+When the final registered GREE Cloud device is removed, the controller closes the unused MQTT session. MQTT messages already in flight after removal are ignored while no Cloud devices are registered, preventing repeated stale-device warnings.
+
 ## GREE Cloud and energy — 0.14.0
 
 Devices now expose `connection_type`, `connection_status`, `capabilities`, Cloud synchronization fields and energy-source metadata through the existing device API. Local and Cloud devices use the same command endpoint; dispatch is selected strictly by `connection_type`.