Home Assistant Core 2025.7.0 → 2025.8.0
5 versions, 19 breaking changes in 1 version, 0 required stops
Version by version, oldest first
2025.7.1 – 2025.7.4: no action items (4 versions)
2025.8.0 2025-08-06
Quoted from www.home-assistant.io/blog/2025/08/06/release-20258/#backward-incompatible-changes
Breaking
Android Debug Bridge (ADB)
Android Debug Bridge media players entities now report to be off where they previously reported to be in standby state.
If you have automations or scripts that rely on the Android Debug Bridge media player reporting standby state, you will need to update them to use the new off state.
(@emontnemery - #148130) (documentation)
Breaking
Apple TV
Apple TV media players entities now report to be off where they previously reported to be in standby state.
If you have automations or scripts that rely on the Apple TV media player reporting standby state, you will need to update them to use the new off state.
(@emontnemery - #148132) (documentation)
Breaking
Cambridge Audio
Cambridge Audio media players entities now report to be off where they previously reported to be in standby state.
If you have automations or scripts that rely on the Cambridge Audio media player reporting standby state, you will need to update them to use the new off state.
(@emontnemery - #148133) (documentation)
Breaking
Ecovacs
The battery property on vacuum entities is being removed in Home Assistant. Therefore, this property is now removed from this integration and is replaced by a battery level sensor.
Please review your automations, scripts or cards using the battery property and update the code to use the battery sensor instead.
(@mib1185 - #149084) (@edenhaus - #149581) (documentation)
Breaking
Husqvarna Automower
The summary field of calendar events provided by the Husqvarna Automower calendar platform has been updated to include the device name as a prefix. This change improves clarity when multiple mowers are used, but may affect automations relying on the previous summary format.
(@Thomas55555 - #147405) (documentation)
Breaking
LOOKin
LOOKin media players entities now report to be off where they previously reported to be in standby state.
If you have automations or scripts that rely on the LOOKin media player reporting standby state, you will need to update them to use the new off state.
(@emontnemery - #148134) (documentation)
Breaking
Matter
The battery property on vacuum entities is being removed in Home Assistant. Therefore, this property is now removed from this integration and is replaced by a battery level sensor.
Please review your automations, scripts or cards using the battery property and update the code to use the battery sensor instead.
Breaking
Mediaroom
Mediaroom media players entities now report to be off where they previously reported to be in standby state.
If you have automations or scripts that rely on the Mediaroom media player reporting standby state, you will need to update them to use the new off state.
(@emontnemery - #148135) (documentation)
Breaking
Miele
The battery property on vacuum entities is being removed in Home Assistant. Therefore, this property is now removed from this integration and is replaced by a battery level sensor.
Please review your automations, scripts or cards using the battery property and update the code to use the battery sensor instead.
(@astrandb - #148765) (documentation)
Breaking
Reolink
The Reolink Wi-Fi signal strength sensor has changed from an indicator value between 0 and 4 (amount of bars) to a value in dBm between -85 dBm and -30 dBm.
Note that all values in this range are possible, but roughly the old values can be converted like this:
- 0 > -85 dBm
- 1 > -75 dBm
- 2 > -65 dBm
- 3 > -55 dBm
- 4 > -45 dBm
Breaking
Roborock
The battery property on vacuum entities is being removed in Home Assistant. Therefore, this property is now removed from this integration and is replaced by a battery level sensor.
Please review your automations, scripts or cards using the battery property and update the code to use the battery sensor instead.
(@luca-angemi - #150126) (documentation)
Breaking
Roku
Roku media players entities now report to be off where they previously reported to be in standby state.
If you have automations or scripts that rely on the Roku media player reporting standby state, you will need to update them to use the new off state.
(@emontnemery - #148137) (documentation)
Breaking
Snapcast
Snapcast media players entities now report to be off where they previously reported to be in standby state.
If you have automations or scripts that rely on the Snapcast media player reporting standby state, you will need to update them to use the new off state.
(@emontnemery - #148138) (documentation)
Breaking
Sony PlayStation 4
Sony PlayStation 4 media players entities now report to be off where they previously reported to be in standby state.
If you have automations or scripts that rely on the Sony PlayStation 4 media player reporting standby state, you will need to update them to use the new off state.
(@emontnemery - #148136) (documentation)
Breaking
Templates
Returning None from a template binary sensor's state template is now interpreted as unknown state instead of as off state.
If this behavior is not desired, you need to adjust your templates to return False explicitly.
(@epenet - #128861) (documentation)
Breaking
Tuya
The battery property on vacuum entities is being removed in Home Assistant. Therefore, this property is now removed from this integration and is replaced by a battery level sensor.
Please review your automations, scripts or cards using the battery property and update the code to use the battery sensor instead.
(@epenet - #150086) (documentation)
Breaking
UniFi Protect
Support for UniFi Protect installations running on versions below 6.0.0 has been removed.
This change is necessary as we are migrating the Home Assistant integration to use the new UniFi Protect Public API, which is only available in current versions.
If you are running an older version of UniFi Protect, you will need to upgrade to at least version 6.0.0 in order to continue using this integration.
You can read more about the 6.0 release in Ubiquiti’s official blog post: 🔗 Introducing Protect 6.0
Note on future updates: The Public API is still under active development and may change over time. As we continue to migrate more features of the integration to use the Public API, it is likely that the minimum required version of UniFi Protect will increase further in upcoming Home Assistant releases. We will make these changes step by step as the API evolves and new capabilities become available.
What do I need to do?
Upgrade your UniFi Protect installation to version 6.0.0 or later.
Be prepared for possible further minimum version increases in the future.
If you are already using version 6.0.0 or newer, and the user in use has sufficient permissions, the integration will attempt to automatically create a new API key. If this succeeds, no further action is required. If it fails, a reauthentication will be triggered, requiring you to re-enter your password and provide your API key manually.
(@RaHehl - #149126) (documentation)
Breaking
Whirlpool Appliances
The door state for washer/dryer machines is now reported as a binary sensor instead of being part of the main machine state sensor, which now reports only the cycle states. Users relying on this state in automations or scripts will need to update their configurations to use the new binary sensor.
(@abmantis - #144078) (documentation)
Breaking
Z-Wave
With this release, you will need to update your zwave-js-server instance. You must use zwave-js-server 3.2.1 or greater (schema 44).
- If you use the Z-Wave JS add-on, you need at least version 0.20.0.
- If you use the Z-Wave JS UI add-on, you need at least version 4.8.0.
- If you use the Z-Wave JS UI Docker container, you need at least version 10.11.0.
- If you run your own Docker container or some other installation method, you will need to update your zwave-js-server instance to at least 3.2.1.
Release notes from github.com/home-assistant/core/releases, and the official release blog, checked 18 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. Home Assistant lists its breaking changes in the “Backward-incompatible changes” section of each monthly release post on home-assistant.io (2020.12 onward). Each entry of that section is quoted as “Breaking” on the x.y.0 release, under the integration name the post gives it. The post’s “Farewell to the following” section (integrations removed in that release, 2020.12–2024.5) is quoted whole as “Note”. The post's separate section for custom integration developers is not quoted. Patch releases are listed but their notes (lists of fixes) are not quoted. Versions come from PyPI (package homeassistant).