fix(climate): gate unrouted WHO 4 #4#II and actuator status polls

.github/release-notes/2.0.0b16.md

@@ -21,7 +21,7 @@ See the cover docs for the details and the known limits.
 
 - **`myhome.send_message` and `myhome.sync_time` reject unknown keys.** A misspelt key such as `gw_mac` or a missing `message` raises a validation error instead of sending the frame to the default gateway; both services get text selectors in the visual editor (#189).
 - **Climate zones show the setpoint in force (dimension 12).** When the thermostat regulates to another setpoint than the commanded one (dimension 14; 23.5 in force while 21.0 commanded on an F461), the entity and `local_target_temperature` now show the one in force instead of the commanded value plus the knob offset. Known limit: once a zone has reported dimension 12, a dimension 14 that is not the echo of a Home Assistant write does not move the slider until the next dimension 12 report or poll (see Known Limitations).
-- **Startup requests the gateway firmware drops are no longer sent.** `*#4*0##` is left out on F450, F454, F459, F460, F461, H4684, MH200, MH201, MH202 and MyHomeServer1, `*#16*0*5##` on F450, F459, F460, F461, MH202 and MyHomeServer1 (own-firmware-oracle verdicts; the MH201 from a physical sweep trace). On the SCS-only models among them (F450, F454, F459, H4684, MH200, MH201, MH202), each climate zone asks for its temperature with `*#4*<WHERE>*0##` after the sweep instead (a zone behind an F422 interface is left to report by itself on the F450, F454, F459 and MH202, whose firmware drops that request too), and a restored `current_temperature` is flagged `current_temperature_restored` until the zone reports (#185, #257, #674). `myhome.sweep_bus` leaves the same two requests out unless called with `force: true`.
+- **Startup requests the gateway firmware drops are no longer sent.** `*#4*0##` is left out on F450, F454, F459, F460, F461, H4684, MH200, MH201, MH202 and MyHomeServer1, `*#16*0*5##` on F450, F459, F460, F461, MH202 and MyHomeServer1 (own-firmware-oracle verdicts; the MH201 from a physical sweep trace). On the SCS-only models among them (F450, F454, F459, H4684, MH200, MH201, MH202), each local climate zone asks for its temperature with `*#4*<WHERE>*0##` after the sweep instead (zones behind an `#4#II` interface are withheld across all gateways unless `supports_interface_zone_requests = True` on the OWNd profile, since zero of 12 oracle firmwares route WHO 4 across `#4#II`), and a restored `current_temperature` is flagged `current_temperature_restored` until the zone reports (#185, #257, #674). `myhome.sweep_bus` leaves the same two requests out unless called with `force: true`.
 - **`myhome.sync_time` refuses time zones with a half-hour offset** (e.g. `Asia/Kolkata`, UTC+5:30) with a translated error. The WHO 13 time-zone field carries whole hours only; b15 (on OWNd 2.0.0b10) set the gateway clock with a truncated offset without saying so (#764).
 - **Group, area and general bus events only for frames that carry a state.** A relative dim step (`*1*30*#1##` / `*1*31*#1##`, `*1*30#2#100*#1##`) no longer fires `myhome_group_light_event` / `myhome_area_light_event` / `myhome_general_light_event` as `on`, no longer switches an assumed-state light group or a point-to-point light on, and its member re-sync accepts both on and off echoes; a WHO 2 `DIMENSION 10` frame on a group, area or general address (`*#2*#5*10*10*50*001*0##`) no longer fires `myhome_group_automation_event` / `myhome_area_automation_event` / `myhome_general_automation_event` as `stop` (nor the gateway's *Centralized shutter stop* trigger). This is a defensive guard matching WHO 1, not a readback a shutter sends: a physical shutter reports `DIMENSION 10` on its own point-to-point address, and the Dimension 11 level echo a gateway really puts on the event session (`*#2*#5*#11#001#1*50##`) never fired an event. On/off and open/close/stop command frames, including the advanced `WHAT 10` / `11` / `12`, fire as before; the WHO 2 scope events are now documented in the cover docs (#367).
 - **`advanced: true` on a standard F411 shutter now logs a startup warning.** Those actuators have no position reporting, so the position stayed at 50 % and calibration was refused; the error now says to remove `advanced: true` (#761, #762).
@@ -35,7 +35,7 @@ See the cover docs for the details and the known limits.
 - **Expose Home Assistant to the bus**: a declarative `expose` engine projects HA entities and the clock onto free SCS addresses: virtual WHO 1 / WHO 2 actuators that a wall control can drive (mirroring HA state back to its LEDs), WHO 4 virtual temperature probes, WHO 18 virtual energy meters and the WHO 13 bus clock. Custom actions run as Home Assistant scripts (#750).
 - **Covers**: `class:` in `myhome.yaml` now reaches WHO 2 covers (a `curtain` is no longer shown as a shutter; #39); Venetian blind slat tilt as timed slat pulses (`slat_tilt`, `slat_time`) (#508); impulse garage and gate covers on WHO 1 relays with optional safety approval, door-entry strike locks and doorbell events (#667); native broadcast for general covers behind an interface (#679); a cover stop overtakes other queued frames (#694); cover kinematics split into pluggable strategies (#739).
 - **Lighting**: 2-digit Area 0 point addresses `01`–`09` (#713); `where: "0004"` in `myhome.yaml` is resolved to `04`, the spelling the gateways accept and report, with a one-time warning, and registry entries created under the 4-digit spelling are moved to it; the duplicate entity and device that bus discovery had created under `04` are removed, their area, labels, icon and custom name carried over to the configured ones where those have none, and a light that bus discovery had created at the address of a WHO 1 switch or impulse cover goes with its lock / unlock buttons; the `A` / `PL` state attributes of such a light, switch or cover read `0` / `4` instead of `00` / `04`, as on bus-discovered entities (#147; the `0809` of #135 is a point of area 8, not of area 0, and stays as typed); ON dimmers on a fresh install are probed for brightness support (#742); timed turn-on uses the OWNd builders (#659); lights the startup sweep already reported are not polled again (#701); area and group re-syncs only skip once every member has echoed, counting only the members' own echoes in the commanded state (#740, #749).
-- **Thermoregulation (WHO 4)**: each zone asks for its actuators (dimension 20) after the startup sweep and after a reconnect, so `hvac_action` is known at start; the new `actuators` attribute lists them (#25, #44); zone humidity is not polled on F450, F453, F453AV, F454, H4684, MH200, MH200N and MH202, where the emulated firmware did not forward `*#4*<WHERE>*60##` (own-firmware-oracle `findings/thermo-zone-requests.md`, emulated firmware; an OWNd profile flag `supports_heating_humidity_request` overrides the table); season frames, a generic setpoint mode and the central unit's season (#657, #725); holiday and vacation program attributes (#689); zone humidity remembered and queried at startup (#712); F461 zones polled, AUTO on standalone zones, fan coils per season, season kept across restarts (#714, #715); `hvac_action` derived from the season when the actuator carries no heating flag (#721); standalone default follows the plant (#698); 10 s command timeouts on the F455 removed (#675); migrated to the `native_*` temperature API (#665).
+- **Thermoregulation (WHO 4)**: each local zone asks for its actuators (dimension 20) after the startup sweep and after a reconnect, so `hvac_action` is known at start; the new `actuators` attribute lists them (#25, #44); zone humidity is not polled on F450, F453, F453AV, F454, H4684, MH200, MH200N and MH202, where the emulated firmware did not forward `*#4*<WHERE>*60##` (own-firmware-oracle `findings/thermo-zone-requests.md`, emulated firmware; an OWNd profile flag `supports_heating_humidity_request` overrides the table); zones behind an `#4#II` interface withhold WHO 4 status/dimension polls and outbound climate writes, and actuator-shaped `Z#N` / `3#Z#N` addresses are withheld from WHO 4 status and zone-dimension polling across all gateways unless the OWNd profile sets `supports_interface_zone_requests = True` (0 of 12 oracle firmwares route WHO 4 across `#4#II`, preventing main-bus local-zone cross-polling or writes on H4684/MH200/F450/F454/F459/F460/F461/MyHomeServer1, false `unresponsive` repairs on F460/F461/MyHomeServer1, and the `MH202` `1.0.24` `coso` `SIGSEGV` crash on `*#4*Z#4#01##` / `*#4*Z#N##`); season frames, a generic setpoint mode and the central unit's season (#657, #725); holiday and vacation program attributes (#689); zone humidity remembered and queried at startup (#712); F461 zones polled, AUTO on standalone zones, fan coils per season, season kept across restarts (#714, #715); `hvac_action` derived from the season when the actuator carries no heating flag (#721); standalone default follows the plant (#698); 10 s command timeouts on the F455 removed (#675); migrated to the `native_*` temperature API (#665).
 - **Sound system**: tuner frequency, preset and RDS read from WHO 22, with optional per-frequency pictures (#695); sound source commands and wall transport steps (#651); amplifiers no longer woken by volume status reports (#670); one decision engine for the power state (#683); an idle decoder can be claimed from a parked group (#723).
 - **Scenarios**: WHO 25 Scenario Plus commands and events (#671); WHO 17 scene events (#656).
 - **Gateways**: H4684 / LGRH4684 and MH201 identification (#652, #722); kernel and distribution in the diagnostic sweep (#711); user commands go ahead of status polls (#685); one frame scheduler with per-target ordering (#738); the HA web session is used for discovery (#757).