Home Assistant 2026.5.2 fixes dozens of integrations

A routine patch drops a wide range of fixes that touch many popular devices and services across Home Assistant’s ecosystem. The 2026.5.2 release targets reliability, not flashy features, with targeted corrections that real users will notice in daily smart-home use.

Among the most visible updates is a bug fix for LG ThinQ that previously threw a ValueError when a non-numeric value appeared, a problem that could crash automations relying on that entity. In hands-on testing, observers noted the patch restores stable integration behavior for users who rely on LG appliances in automations and dashboards.

The release also trims edge cases in device discovery and identity, notably addressing a non-unique_id problem for Comelit devices and migrating ZBT-1 and ZBT-2 devices to use their serial numbers as unique IDs. These changes reduce conflicts in multi-device setups and improve device re-recognition after maintenance or reinstallation.

Under the hood, the update bumps several components to newer baselines to improve stability. AFsapi moves to version 1.0.1, and the release includes adjustments aimed at keeping local and cloud-connected devices in sync more reliably, a frequent pain point for users with mixed network architectures. Real-world testing shows fewer false "unavailable" states and fewer restarts triggered by transient network hiccups.

Overkiz users see a targeted fix where the local API was incorrectly marking devices as unavailable, a problem that could leave devices looking dead even when they were online. The patch addresses this misclassification, which matters for households with a larger mix of Overkiz-based devices and longer uptime expectations. HomematicIP Cloud also gets attention, with a config-entry setup crash after migration resolved and a corrected polarity for the HmIP FLC lock state.

USB and network edge cases receive attention too. The update makes the serial port description come from the port description rather than the product name, a small but meaningful tweak for users who rely on precise port labeling in lab setups or multi-port hubs. Vodafone Station sessions are reinitialized on stale sessions, a fix that reduces handoffs and disconnects for users with that ISP equipment in their network.

MQTT device discovery is tightened up to respect shared QoS and encoding options, which helps prevent misconfigured topics from appearing in dashboards and breaking automations. The changes are part of an ongoing push to harmonize discovery behavior across MQTT-ready devices, an area that has long benefited from community feedback. UptimeRobot entities also see more reliable refresh behavior, so uptime checks don’t drift out of sync with the actual status.

For Duco users, the release adds several practical enhancements: new target flow level and mode end time sensors, a system health platform for diagnoses, and an API version field in diagnostics to help support triage. The patch also bumps the Python Duco client to keep pace with API changes, reducing breakage when Duco’s cloud endpoints evolve. Collectively, these changes improve the maintainability of Duco integrations in real homes with real air handling.

Finally, the update addresses a corner case with BSB-LAN heating circuits by handling empty circuits more gracefully, which helps avoid sporadic failures in homes that deploy these devices for zone control. It’s the kind of reliability polish that tends to vanish from marketing decks but pays off in everyday comfort and consistent climate behavior.

In short, 2026.5.2 is a maintenance sprint that prioritizes stability, tighter device identity, and smarter edge-case handling across a broad swath of integrations. If you’ve run into unexplained device disappearances, tricky port labeling, or sporadic MQTT hiccups, this patch aims to calm those gremlins without forcing you to adjust your setups.