FA-92834 / HVAC thermostat control / Member archive

Zoned system idles for a minute after a mode is satisfied · case 04

Zones waiting for the opposite mode lose a minute every time the current mode finishes.

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

Zoned single-unit system arbitration per minute; each sample maps zone -> heat, cool or None. When idle the system picks the mode with more calling zones (ties go to heat). A mode ends when no zone calls for it, and a new mode may be chosen in the same minute. If zones call for the opposite mode, the system switches once the current mode has run max_run minutes, restarting the run timer. Dampers open only for zones calling the active mode. Return [mode, sorted open zones] per minute.

Why this case matters

Residential and light-commercial thermostats make these decisions sample by sample; each defect changes equipment calls in a way that shows up as short cycling, comfort complaints or equipment stress.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
regression: scenario 2	`[["heat", ["z3"]], [null, []], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z3"]]]`	`[["heat", ["z3"]], ["cool", ["z1", "z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z2", "z3"]], ["cool", ["z3"]]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.