v0.14.0
This commit is contained in:
+25
-3
@@ -1,6 +1,6 @@
|
||||
# GREE Controller API reference
|
||||
|
||||
HTTP and WebSocket API for GREE Controller **0.13.10**.
|
||||
HTTP and WebSocket API for GREE Controller **0.14.0**.
|
||||
|
||||
[← Main documentation](../README.md)
|
||||
|
||||
@@ -232,7 +232,7 @@ Response:
|
||||
{
|
||||
"status": "ok",
|
||||
"name": "gree-controller",
|
||||
"version": "0.13.10",
|
||||
"version": "0.14.0",
|
||||
"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.13.10",
|
||||
"version": "0.14.0",
|
||||
"uptime_seconds": 1234,
|
||||
"auth_required": false,
|
||||
"control_ready": true,
|
||||
@@ -1651,3 +1651,25 @@ Cancellation suppresses the same pending intent until a new explicit thermostat/
|
||||
Existing Flow updates require `expected_revision`. A mismatched revision returns HTTP 409 to prevent stale editor tabs from overwriting newer graphs. Source Flow plus generated outputs are replaced atomically in one database transaction while configuration/automation/schedule/thermostat-cycle operations are serialized.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
## 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`.
|
||||
|
||||
Cloud account/discovery/diagnostic endpoints:
|
||||
|
||||
- `GET|PUT /api/settings/gree-cloud`
|
||||
- `POST /api/integrations/gree-cloud/test`
|
||||
- `GET /api/integrations/gree-cloud/devices`
|
||||
- `POST /api/integrations/gree-cloud/devices/{cloud_id}/add`
|
||||
- `GET /api/integrations/gree-cloud/status`
|
||||
- `POST /api/integrations/gree-cloud/reconnect`
|
||||
- `GET /api/devices/{id}/cloud-diagnostics`
|
||||
|
||||
Energy endpoints:
|
||||
|
||||
- `GET /api/integrations/home-assistant/energy-sensors` lists compatible cumulative HA energy sensors.
|
||||
- `GET /api/history/energy?device_id=...&interval=hourly|daily|weekly|monthly&source=auto|gree_cloud|home_assistant` returns consumption buckets and period summaries in kWh.
|
||||
|
||||
Cloud settings and diagnostics are redacted: passwords, REST/MQTT tokens, Authorization values and device cipher keys are not returned.
|
||||
|
||||
+1090
-12
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user