gru/gree-controller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

v0.7.1

Browse Source
This commit is contained in:
Mateusz Gruszczyński
2026-08-25 19:05:18 +02:00
parent 3ee93b7225
commit dce9ef7270
14 changed files with 132 additions and 93 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/API.md
+2 -2
View File
@@ -111,7 +111,7 @@ A zone stores separate profile temperatures for both seasons:
Quick control does not directly fight the schedule engine:
```bash
# Sleep now until the next schedule boundary (or until cleared if there is no future transition)
# Sleep until the next schedule boundary (or until cleared if there is no future transition)
curl -X POST "$BASE/api/zones/ZONE_ID/control" -H "$AUTH" -H 'Content-Type: application/json' \
-d '{"preset":"sleep"}'
@@ -124,7 +124,7 @@ curl -X POST "$BASE/api/zones/ZONE_ID/control" -H "$AUTH" -H 'Content-Type: appl
-d '{"setpoint":22.5}'
```
`mode` on the quick zone endpoint accepts `house`, `cool`, or `heat`. `house` means **Follow house mode** and should be left unchanged when the zone is meant to inherit the global GREE Controller mode. A fixed `cool`/`heat` is an explicit per-zone override; therefore house mode `off` stops inherited zones but does not disable a zone deliberately fixed to Cooling or Heating. Whole-house master power remains authoritative over all zones.
`mode` on the quick zone endpoint accepts `house`, `cool`, or `heat`. `house` means **Follow global mode** in the UI and should be left unchanged when the zone is meant to inherit the global GREE Controller mode. A fixed `cool`/`heat` is an explicit per-zone override; therefore house mode `off` stops inherited zones but does not disable a zone deliberately fixed to Cooling or Heating. Whole-house master power remains authoritative over all zones.
### Climate groups