Home Assistant fixes LG ThinQ error in patch release

LG ThinQ error finally fixed in Home Assistant 2026.5.2. The patch bundle fixes a raft of bugs across integrations and devices, proving once again that a maintenance update can matter as much as a feature sprint.

Home Assistant’s 2026.5.2 release tightens stability across the platform with a slate of targeted fixes. Among them, a notable bug in LG ThinQ integrations is resolved, addressing a ValueError that cropped up when non-numeric values appeared in the data stream. That kind of issue could disable automations or cause sensors to misreport, so the fix is a relief for users who rely on ThinQ devices for routine home control. Real-world performance shows a smoother startup and fewer unexpected light or climate events tied to LG appliances after the patch lands.

The update also carries a careful migration touch for ZBT-1 and ZBT-2 devices. Home Assistant now uses serial numbers to define the unique_id for these devices, a change that helps prevent duplication and mismatches as users move between updates and configurations. For anyone who previously managed multiple ZBT devices under similar identifiers, the migration reduces the risk of orphaned entities and brittle automations. It’s the kind of under-the-hood polish that pays off in long-tail reliability.

Other fixes target long-standing quirks in device discovery and local control. For Comelit users, a non-unique_id issue was resolved, while Overkiz users should see the local API reinitialize correctly when sessions go stale. These changes reflect the project’s ongoing emphasis on predictable local control and robust entity identification, two areas that often determine whether a smart home system behaves like a trusted automator or a fragile chain of disconnections.

In addition, the 2026.5.2 patch tackles a mix of smaller, but important, reliability concerns. Homematicip_cloud config entry setup crashes observed after migrations are addressed, HmIP-FLC lock state polarity is corrected, and the serial port description is now taken from the description rather than the product name. For users who juggle multiple ecosystems, these tweaks reduce configuration drift and keep device states aligned with real-world behavior.

On the connectivity front, Vodafone Station sessions that had grown stale now reinitialize more reliably, and MQTT device discovery gains fixes around shared QoS and encoding options. UptimeRobot entity refresh bugs are also addressed, helping keep uptime data current without manual tinkering. For practitioners watching dependability in distributed setups, these adjustments matter because they cut down the time spent chasing flaky feeds and stale statuses.

Industry observers note that releases like 2026.5.2 illustrate a practical truth in home automation, that most value comes from stability, interoperability, and quiet under the hood fixes rather than splashy new features. For users, the takeaway is simple: keep the system updated to reduce rare but painful edge cases, especially if you rely on complex automations spanning LG ThinQ, ZBT devices, and local network integrations. The patch demonstrates that a well targeted maintenance release can meaningfully reduce the friction that makes smart homes feel unreliable in real life.