climate: standalone zone keeps hvac_mode cool after a DIMENSION 7 cooling-comfort echo although the season frame says heating #811

Requested by A

Environment: MyHOME 2.0.0b16 (v2-phase1-architecture d8bac15, local Home Assistant 2026.10.2), OWNd 2.0.0b11, BTicino F461 2.0.11, Living Now KW4691 standalone thermostat zone 2 (no central unit). Capture: tests/fixtures/traces/f461_live_2026-10-24 run 4 (PR #810) and the 2026-10-24 session on #791.

What happened. After *#4*2*#7*2*3## (DIMENSION 7, context 2 = cooling, state 3 = comfort) the thermostat answered *#4*2*7*2*3##, *#4*2*12*0250*3##, *4*208*2##, *4*0*2## (season conditioning), and a few seconds later *4*1*2## (season heating) with *#4*2*12*0225*3##. The climate entity went to hvac_mode: cool and stayed cool after the *4*1*2## frame, after a manual write *#4*2*#14*0235*3## (answered with *4*1*2##, 12 = 14 = 0235), and after a *#4*2## poll whose reply carried *4*1*2## again; season: heating, hvac_action: idle, temperature: 23.5, state cool.

Where it comes from (as read in climate.py). _apply_zone_state() sets HVACMode.COOL from the DIMENSION 7 cooling context; MESSAGE_TYPE_SEASON (*4*1*2##) intentionally preserves a non-OFF hvac_mode on standalone zones, and the KW4691 never emits *4*110*2## when it returns to heating or on a *#4*2*#14*T*3## write, so nothing ever moves the mode back to heat.

Expected. On a standalone zone, a season frame *4*1*2## (or *4*0*2##) that contradicts the current hvac_mode should update it, or the DIMENSION 7 context should not set the mode when the zone is standalone and the season frame is the authority.

Related frames seen in the same session (not decoded by OWNd 2.0.0b11, mode=None): *4*108*2## with heating comfort, *4*107*2## with heating eco, *4*208*2## with cooling comfort. Reported separately to OWNd.

🤖 Generated with Claude Code