From 37a44a8a6f6ac20d559e040043cebe35acb9991d Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Sun, 3 May 2026 17:39:39 -0500 Subject: [PATCH] [tests] Fix flaky host_mode_climate_basic_state by ignoring prior MEMORY state The fixture shares the `host-climate-test` build dir with host_mode_climate_control.yaml. When the control test runs first and leaves the thermostat in HEAT mode, MEMORY restore on the next basic_state boot picked up HEAT and the initial-state assertion failed (`assert ClimateMode.HEAT == ClimateMode.OFF`). --- tests/integration/fixtures/host_mode_climate_basic_state.yaml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/tests/integration/fixtures/host_mode_climate_basic_state.yaml b/tests/integration/fixtures/host_mode_climate_basic_state.yaml index f79d684fc6..744b418d0f 100644 --- a/tests/integration/fixtures/host_mode_climate_basic_state.yaml +++ b/tests/integration/fixtures/host_mode_climate_basic_state.yaml @@ -28,6 +28,10 @@ climate: min_temperature: 15.0 max_temperature: 32.0 temperature_step: 0.1 + # Don't restore previous state from flash — this fixture shares the + # `host-climate-test` build dir with host_mode_climate_control.yaml, so a + # prior run of that test could leave the thermostat in HEAT/COOL. + on_boot_restore_from: default_preset default_preset: home preset: - name: "away"