v4.0.0-beta.7 - Humidity source fix, polling interval fix & log cleanup #236

hiall-fyi · 2026-04-18T20:50:16Z

hiall-fyi
Apr 18, 2026
Maintainer

⚠️ If you're coming from v2.x, upgrade to v3.3.1 first, then v3.5.3, then v4.0.

⚠️ v4.x requires Home Assistant 2025.11 or later.

No config changes needed if you're already on any v4.0.0 beta.

Humidity now prefers cloud over HomeKit — The bridge caches humidity values and returns stale readings that can drift 1–4% from the actual sensor. Humidity now uses the cloud API (0.1% precision) by default, with HomeKit as fallback only when cloud is unavailable. Temperature still uses HomeKit first. No change to polling frequency.
Much quieter debug logs — Removed ~130 lines of verbose per-poll logging. HomeKit events only log when values change, data source tracking only logs on transitions, and polling summaries are now single-line.
HomeKit writes visible in normal logs — Temperature and mode changes through HomeKit now appear at info level instead of debug.
Startup and shutdown summaries — A single info line on startup showing zone count, HomeKit status, weather, and polling interval. Shutdown logs when state persistence begins.
Test Mode removed — The simulated 100-call API tier switch is gone. Custom Polling + HomeKit covers everything now. The entity is automatically cleaned up on upgrade.

Fixed custom polling interval stuck after being set (Homekit humidity. New dedicated thread #234) — Once you set a custom day or night polling interval, there was no way to clear it back to automatic. You can now type 0 to go back to auto polling.

This discussion was created from the release Humidity source fix, polling interval fix & log cleanup.