This update to Home Assistant Core delivers a broad set of fixes for popular device integrations, ensuring more accurate readings and smoother operation for self-hosted setups. Growatt V1 users will now see correct total output power, while SmartThings air conditioners get proper temperature range unit conversion. The AirGradient 0-1PS is now correctly identified as an outdoor model, and MJPEG IP Camera action handlers no longer swallow exceptions. ViCare now treats malformed payloads as an update failure rather than crashing, and a sleeping Roborock Q7 job is reported as paused. Peblar owners benefit from a corrected maximum charge limit and only supported smart charging modes are offered, along with a library bump to version 1.0.1. For Midea appliances, missing MAC address and serial number in device info are fixed, switches receive appropriate icons, and airflow and power rate availability are corrected.
Beyond device-specific fixes, several platform-level improvements enhance reliability and usability. The AWS S3 integration now warms up loader caches to eliminate blocking list directory calls. Alexa to-do lists refresh automatically after writing to them. MCP authorization servers are now asked for a refresh token, ensuring longer-lived sessions. Error messages for update installation and skipping are now properly translated. Sleeping printers get extra time to wake up before being marked offline. A deprecation notice now specifies the integration domain for clearer guidance. Mikrotik scans every supported wireless interface instead of only the first one. The Sofar waiting-ends sensor is now gated on an active countdown, preventing misleading states.
Finally, the release includes quality and testing improvements that keep the codebase robust. The peblar and probatio libraries have been bumped to versions 1.0.1 and 0.11.4 respectively. Test coverage has been raised to 100% for the coordinator components in Mikrotik and Shelly, the todo integration in Alexa Devices, and the light and binary_sensor integrations in Midea. These changes may not be visible to end users, but they help maintain a stable and maintainable platform for self-hosted deployments.
