Humidifier/heater ineffective alerts use the wrong band: they read RH/temperature targets from compose helpers the hub never writes, so they always fall back to

Found while fixing the dehumidifier alert gap. The hub’s RH/temperature setpoints live in its controls (number.dsc_hub_rh_target_min/max, number.dsc_hub_target_temp), but the ineffective-suspect checks and the humidify/dehumidify flow proxies look them up in the compose helper store (helpers.get(…)), where nothing writes them — so they silently use hard defaults RH min 45, max 70, target 25 °C whatever the grow is set to (the simulated flower tent runs max 55 %). Separately, binary_sensor.dsc_humidifier_ineffective_suspect is raised when the humidifier is on and tent RH >= rh_max − 0.5: that describes a humidifier over-shooting the ceiling, not one failing to raise RH (which would be RH staying below rh_min). The new climate-failure alerts (dehumidifier ineffective, relay mismatch, RH/VPD out of band) read the hub’s own controls and do not share this problem; the older checks were deliberately left unchanged pending review. Fix: read setpoints via _control_state(view, ‘number.dsc_hub_…’) like the new checks, and flip the humidifier condition to RH <= rh_min − margin held.