v0.8.20

src/api/zones.rs

@@ -142,6 +142,7 @@ async fn create_zone(State(state): State<AppState>, Json(input): Json<ZoneInput>
     canonicalize_zone_ha_entity(&mut zone, &settings);
     state.db.save_zone(&zone)?;
     state.broadcast("zone.created", serde_json::to_value(&zone)?);
+    state.wake_zone_control();
     Ok((StatusCode::CREATED, Json(zone)))
 }
 async fn update_zone(State(state): State<AppState>, Path(id): Path<String>, Json(input): Json<ZoneInput>) -> Result<Json<Zone>, AppError> {
@@ -241,10 +242,15 @@ async fn update_zone(State(state): State<AppState>, Path(id): Path<String>, Json
     if power_off_device {
         power_off_zone_device(&state, &zone, "zone.disabled").await;
     }
+    state.wake_zone_control();
     Ok(Json(zone))
 }
 
 async fn apply_zone_control_patch(state: &AppState, id: &str, patch: ZoneControlPatch, source: &str) -> Result<Zone, AppError> {
+    // A quick preset/setpoint derives its resume boundary from schedules. Take the schedule
+    // lock before the per-zone lock so a concurrent schedule edit cannot leave an override
+    // pointing at an obsolete boundary (and so lock order stays schedule -> zone -> device).
+    let _schedule_guard = state.lock_schedule_operation().await;
     // Serialize quick-thermostat changes with the same device lock used by GREE polling and
     // manual-takeover detection. Without this, a poll that started just before a Web/HA
     // thermostat action could save an older zone snapshot afterwards and resurrect a false