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

v0.7.2

Browse Source
This commit is contained in:
Mateusz Gruszczyński
2026-08-25 19:44:12 +02:00
parent 62d071c972
commit 0d65a6a946
15 changed files with 464 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files
BUILD_REPORT.md
+23 -1
View File
@@ -1,4 +1,4 @@
# GREE Controller v0.7.2 - build and validation report
# GREE Controller v0.7.3 - build and validation report
## Scope
@@ -260,3 +260,25 @@ Validation for the 0.7.1 package:
- Restored `tokio-util = 0.7.19`, which satisfies `tower-http 0.6.11` (`^0.7`) and is present in the crates.io index used by the target LXC.
- No application source, database schema, scheduler, automation, device-control or Web UI logic changed in this hotfix.
## 0.7.3 Home Assistant climate-group support
- Added restricted HA group discovery and group-control endpoints.
- Added one Home Assistant device per configured climate group.
- Added group Power switch, Thermostat mode select, Work profile select and Control plan sensor.
- Group reporting derives common mode/profile from member-zone configuration and reports mixed states without coercing them.
- Group plan attributes include members, online unit count, average current temperature, demand count and upcoming zone schedule events.
- Existing group-control engine remains the single command path, including global-master-power and overlapping-disabled-group protections.
### 0.7.3 validation
- `python3 -m py_compile home-assistant/custom_components/gree_controller/*.py` passed.
- Home Assistant manifest and PL/EN translation JSON parsed successfully.
- `Cargo.toml` parses successfully and both Cargo package metadata and HA manifest report `0.7.3`.
- `Cargo.lock` keeps the packaging hotfix at `tokio-util = 0.7.19`.
- Static assertions confirm the restricted HA router exposes group discovery/control, the API client polls groups, and select/switch/sensor group entities are registered.
- `node --check web/app.js` and `node --check web/sw.js` passed.
- `bash -n scripts/*.sh` passed.
- HTML parsing and CSS brace-balance checks passed.
- The validation environment does not provide `cargo`/`rustc`, so the Rust test/build step must run on the target host/LXC (the normal `scripts/update.sh` performs `cargo test --all-targets` before installation).