v0.5.0

home-assistant/README.md

@@ -10,6 +10,15 @@ It creates HA `climate` entities but sends every command to the standalone Rust
 
 The climate proxy supports power/turn on/off, HVAC modes, target temperature, fan mode, vertical swing and horizontal swing.
 
+Version 0.5.0 additionally exposes the controller's automation plan:
+
+- `sensor` for the whole-house plan (house mode, upcoming events and active rules),
+- one `sensor` per thermostat zone with current demand, active preset/schedule and upcoming transitions,
+- one writable `number` per zone for the controller target temperature (8-30°C, 0.5°C step),
+- one `switch` per zone for enabling/disabling the thermostat directly from Home Assistant.
+
+The plan entities can be placed on a normal Home Assistant dashboard; their `next_events` attributes contain the same schedule timeline shown as graphical blocks in the controller Web UI. Changing a zone target number calls the restricted controller zone API and creates the same temporary override as the Web UI. The zone switch uses the same API to enable or disable that thermostat.
+
 ## Install the custom integration
 
 Copy the directory into your HA configuration:
@@ -25,7 +34,7 @@ Restart Home Assistant, then open **Settings -> Devices & services -> Add integr
 - controller URL, for example `http://192.168.1.20:8787`,
 - the generated controller access token.
 
-The integration token is required even when the controller Web UI itself is left open on a trusted LAN. It is restricted to reading controller devices and sending climate commands.
+The integration token is required even when the controller Web UI itself is left open on a trusted LAN. It is restricted to reading controller devices/control plans and sending climate, zone target or zone enable/disable commands.
 
 ## Preserve an existing entity ID