v0.12.0

README.md

@@ -2,7 +2,7 @@
 
 Self-hosted controller for GREE-compatible air conditioners with a local Web UI, thermostat zones, schedules, Home Assistant integration, history, notifications and a documented HTTP/WebSocket API.
 
-**Current release: 0.11.6**
+**Current release: 0.12.0**
 
 > [Full API reference](docs/API.md) — authentication, every endpoint, request bodies, response models, WebSocket events and examples.
 
@@ -306,7 +306,7 @@ For Linux/network issues also use:
 
 ## Backup and restore
 
-**Settings → Application → Configuration backup** exports settings, devices, zones, groups, schedules and automations.
+**Settings → Application → Configuration backup** exports settings, devices, zones, groups, schedules, automations and Flows.
 
 The export intentionally does **not** contain metric history, event history or generated API-token records. It **does contain** GREE binding keys and configured integration secrets, so store it like a credential file.
 
@@ -369,7 +369,9 @@ Runtime assets are available at `/lang/index.json` and `/lang/<code>.json`.
 
 ## API
 
-The HTTP API is the same backend used by the Web UI. It includes devices, zones, groups, house control, schedules, automations, history, control plan, events, settings, backup/restore, debug, tokens and integration tests.
+The HTTP API is the same backend used by the Web UI. It includes devices, zones, groups, house control, schedules, automations, history, control plan, events, functional settings resources, configuration backup/restore, tokens and integration tests.
+
+**Breaking in 0.12.0:** the monolithic `/api/settings`, `/api/debug`, `/api/events/retention` and `/api/settings/{export,import}` routes were removed. Settings now live under `/api/settings/application`, `/gree`, `/history`, `/influxdb`, `/notifications`, `/night`, `/home-assistant` and `/debug`; configuration backup uses `/api/configuration/export` and `/api/configuration/import`.
 
 Start here: