HomeAssistant Core 2026.4.3 released on 17-04-2026
HomeAssistant Core 2026.4.3 is out now. It fixes a range of integration crashes, prevents spurious sensors and corrects energy and EV units, so setups reliant on those integrations should see more stable and accurate readings.
See the full changelog on the Home Assistant Core GitHub release page for the complete list of fixes, dependency bumps and upgrade guidance.
What’s in this release
- Integration bug fixes: Proxmox VE storage usage crash when used_fraction was missing; template binary sensors keeping their device_class; FRITZ!Box Tools no longer creates a CPU temperature sensor when unsupported; ESPHome cold/warm white colour temperature read-back corrected; SwitchBot Keypad Vision doorbell detection fixed; Wyoming satellite memory leak on disconnect resolved; VOIP blocking call removed from the event loop; Miele steam oven combo cleaning codes added.
- Units and energy/EV sensor corrections: OpenEVSE charging_current and charging_power units fixed; DLQ ADD_ELE energy sensor for Tuya now reports kWh correctly; SPH power sensors in growatt_server use the correct unit; Tibber client handling improved to avoid failures.
- Platform and dependency updates: Z-Wave JS cover moving state now uses current position and cover capabilities; disabled discovered MQTT entities are cleaned up correctly; several dependencies bumped (Pillow 12.2.0, uv 0.11.6, PySwitchbot 2.0.1, satel-integra updates, pyTibber 0.37.1, PyViCare 2.59.0 and others) to pick up upstream fixes.
Upgrade notes
- No breaking changes are listed in the release notes; review the full GitHub changelog before upgrading and follow any integration-specific guidance provided there.
- If you encounter regressions after upgrading, restore from your backups or pin to the previous release until a follow-up fix is available; report issues to the Home Assistant issue tracker with logs and reproduction steps.
Let us know how 2026.4.3 behaves in your setup — share any issues or improvements you spot on the Home Assistant community channels or the GitHub issue tracker.
