v0.4.1

docs/PROJECT_SPEC.md

@@ -66,23 +66,35 @@ Each device stores:
 - fan, swing, quiet, turbo, light,
 - online/last-seen/error state.
 
-## Temperature zones
+## Smart thermostat, zones and schedules
 
-A zone connects an AC to a temperature-control policy. It contains:
+The primary user model is a fast thermostat, not raw device automation. A global **House mode** selects the season (`cool`, `heat`, `off`). Zones follow it by default and can optionally override Heat/Cool. Global Off is authoritative and powers controlled units down.
 
-- target setpoint,
-- heat/cool mode,
-- hysteresis,
-- minimum ON time,
-- minimum OFF time,
-- temperature source,
-- optional Home Assistant sensor entity.
+During normal heating/cooling the controller minimizes unit power cycling. It keeps the indoor unit powered and uses **setpoint modulation**:
 
-Each zone can assign its own Home Assistant room sensor. Combined mode fuses the GREE and room measurements with a configurable weight (40% room sensor by default), while GREE remains the primary input. If HA is unavailable or the two sensors differ beyond the configured limit, control falls back to the GREE sensor.
+- when the zone requires conditioning, use the active target (optionally assisted slightly by outdoor weather),
+- when the zone is satisfied, move the device setpoint to the non-demand side of the room target so the inverter/compressor can stop naturally,
+- use hysteresis and a minimum adjustment interval to avoid command chatter,
+- optionally adjust fan speed based on room error and outdoor extremes.
+
+Each zone has separate seasonal profile temperatures:
+
+- Cooling: Comfort / Sleep / Away,
+- Heating: Comfort / Sleep / Away.
+
+The zone can use the GREE internal sensor, its own Home Assistant room sensor, or a weighted combination. External room sensors are configured per zone; loss/discrepancy falls back safely to the GREE sensor.
+
+Weekly schedules reference profiles instead of duplicating temperatures. Ready-made Family, Child room, Bedroom, Workday and Always-comfort templates create ordinary schedule rows that remain fully editable. A manual **Sleep now**, Comfort, Away or custom-temperature override ends automatically at the next schedule boundary. Whole-house preset actions apply the same temporary policy to every zone.
+
+Automations remain available for advanced exceptions. Daily comfort should be implemented with zones/profiles/schedules so direct-device automation commands do not compete with the thermostat engine.
+
+### Outdoor temperature assist
+
+A configured Home Assistant outdoor-temperature entity is optional auxiliary context. It never replaces the room-control temperature. Under strong heat/cold the engine may slightly bias the active AC target and increase Smart Fan airflow. If HA is unavailable, the smart thermostat continues without outdoor assistance.
 
 ## Scheduler and automations
 
-Schedules are weekly time windows and may cross midnight. Automations currently support time or temperature triggers and send device commands with cooldown protection.
+Schedules are weekly time windows and may cross midnight. Schedules can select Comfort/Sleep/Away or a custom setpoint. Automations support time or temperature triggers and device commands with cooldown protection; they are intended for exceptions rather than the normal daily thermostat cycle.
 
 The automation engine runs in Rust and does not require Home Assistant YAML automation logic.
 
@@ -142,7 +154,8 @@ A development script prepares dependencies/build/runtime configuration, and a se
 - secrets kept outside source control,
 - no direct public Internet exposure,
 - TLS delegated to a trusted reverse proxy/VPN when required,
-- local device keys and HA token protected in environment/database files.
+- local device keys and HA token protected in environment/database files,
+- invalid/self-signed HA HTTPS certificates are rejected by default; bypass is an explicit trusted-LAN opt-in.
 
 
 ## Per-zone room sensors
@@ -160,3 +173,10 @@ The zone controller supports `device`, `combined`, and `home_assistant` temperat
 - `scripts/service.sh` provides common systemd operations.
 - Cargo's `build.rs` stays at the package root because Cargo requires that location.
 - Every SQLite statement and schema definition is centralized in `src/queries.rs`; database/domain code must not embed SQL strings elsewhere.
+
+
+## Web UI design system (v0.4.1)
+
+The embedded UI uses a compact Supabase-inspired dashboard language while retaining GREE Controller branding and information architecture. Light, Dark and System themes are driven by CSS design tokens. The visual system favors neutral layered surfaces, thin borders, 6-8 px radii, compact controls, a restrained green accent, no decorative shadows, a desktop sidebar and mobile bottom navigation.
+
+Tailwind CSS is an optional local build dependency only. `web/styles.css` is committed and embedded into the Rust binary, so production/LXC runtime has no CDN or Node.js dependency. UI source/build files are `web/tailwind.input.css`, `tailwind.config.js`, `package.json`, and `scripts/build-web.sh`.