The latest Home Assistant release experienced an unexpected delay—it was originally slated to ship last Friday, but technical difficulties threw a wrench in the works. The team sincerely apologizes for the slower pace and thanks everyone for their patience.
Roborock vacuum owners will appreciate a series of updates aimed at ironing out kinks. The underlying python-roborock library has been bumped through versions 5.26.0, 5.29.0, 5.30.0, and finally 5.31.1, each bringing incremental refinements. On top of that, the integration now filters A01 query protocols based on supported schemas, updates dynamic dock support, and resolves a tricky issue with segment mapping repairs that was triggering unnecessary alerts.
Overkiz users get two important fixes: Hitachi Yutaki units no longer have the second heating zone incorrectly mirroring zone 1 states, and RTSGeneric covers now open and close as expected. The pyoverkiz dependency moves to version 2.1.0 to support these changes.
Several other device integrations received targeted stability improvements. The UniFi integration no longer crashes during setup when dealing with cellular or 5G WAN connections that lack monitors. Hikvision binary sensors adopt properly unique IDs to avoid conflicts. Lunatone sensors now refresh their data before each update for more accurate readings, and Vizio configuration entries automatically update their host on Zeroconf rediscovery. Over in the kitchen, the La Marzocco integration filters out grinders during certain operations to prevent confusion, and Plugwise Select receives a handful of stability tweaks.
Rounding out the release, the Guntamatic library jumps from v1.9.1 to v1.9.2, the Swisscom Internet Box integration gets a new python-swisscom-internet-box version 0.2.0, and the FRITZ!Box Tools integration ensures repairs are no longer persistent. The Nederlandse Spoorwegen (NS) integration switches its device representation to a service. The GIOS air quality integration updates its backend library to 7.1.1. On the Zigbee front, ZHA moves to version 2.0.1. The frontend is refreshed to 20260624.6, and add-on update entities now properly reflect changes after the add-on store is reloaded via the Supervisor API proxy.
Finally, a notable under-the-hood change exempts certain protocol integrations from the entity limit, helping larger installations avoid hitting caps.
