Home Assistant Core Patch: HTTP Config Safeguards, Integration Fixes, and Library Updates

imagem 54

This latest Home Assistant Core patch brings important fixes to the HTTP configuration system, ensuring a smoother experience during upgrades. The migration of YAML-based HTTP settings now correctly avoids using the new default port 80 unless explicitly configured, preventing accidental exposure. Additionally, a safety check has been introduced to block changes to the HTTP configuration while Home Assistant is not fully running, eliminating a potential source of misconfiguration for self-hosted setups.

Several integrations received targeted bug fixes to address user-reported issues. The AirGradient integration now accurately reports CO2 units and corrects the display brightness value. The Music Assistant media browser regains its search functionality, while the Cookidoo migration process no longer creates duplicate unique IDs. The Casper Glow integration now properly rejects non-Casper Glow Bluetooth devices before the configuration handshake, avoiding confusion. SwitchBot standing fan users will notice missing icons have been added and night light options have been renamed for clarity. The Liebherr home appliances integration was also updated with a newer API library (version 0.5.1) to resolve underlying communication issues.

Under the hood, several key dependencies have been updated to bring improvements and new features. The Hue integration’s backend library (aiohue) was bumped to version 4.8.2, the Deebot client for Ecovacs devices was updated to the latest release (18.5.1) and now includes device verification support for more reliable connections. Finally, the intents system received a version bump and additional tests to enhance the accuracy of voice assistant commands.

Leave a Comment

Your email address will not be published. Required fields are marked *