Home Assistant Core 2025.1.0 → 2025.2.0
5 versions, 7 breaking changes in 1 version, 0 required stops
Version by version, oldest first
2025.1.1 – 2025.1.4: no action items (4 versions)
2025.2.0 2025-02-05
Quoted from www.home-assistant.io/blog/2025/02/05/release-20252/#backward-incompatible-changes
Breaking
Ecovacs
The attributes on the vacuum entity for the lifespan of the main brush, side brush, and filter have been deprecated and are now removed. These attributes are superseded by dedicated sensor entities.
Breaking
Home Connect
Some appliances might lose their power entity as the API does not report the power setting.
(@Diegorro98 - #135930) (documentation)
Breaking
IMGW-PIB
Some hydrology data is no longer available to Home Assistant users via IMGW-PIB API and for this reason, the following entities are removed:
flood alarmbinary sensorflood alarm levelsensorflood warningbinary sensorflood warning levelsensor
(@bieniu - #134668) (documentation)
Breaking
KNX
The "State Updater" option in the integration settings now works as intended. Previously, the option wasn’t applied correctly.
- When disabled: KNX will only read a
state_addressonce when the connection is established. - When enabled: KNX will also read any
state_addressif no value has been received for one hour.
Please review your integration settings to ensure this option is configured according to your preferences.
(@farmio - #135611) (documentation)
Breaking
Litter-Robot
Remove extra_state_attributes from Litter-Robot vacuum entities. These were previously migrated to sensors.
Breaking
MQTT
To change the MQTT broker settings, you need to start a reconfiguration. When CONFIGURE is selected, MQTT shows a "MQTT settings" page with subscribe and publish tools. The Re-configure MQTT button will be replaced with an MQTT options page.
The reconfiguration option will only be available from the MQTT integration entry context menu.
(@jbouwh - #133342) (documentation)
The MQTT publish action no longer supports the topic_template and payload_template attributes. Instead, only topic and payload should be used. In automation and scripts, users can use templates by default. Users were instructed to update their automations and scripts with a repair flow when the use of the deprecated action options was detected.
(@jbouwh - #134056) (documentation)
Breaking
Pentair ScreenLogic
Raw states derived from ScreenLogic enums are now lowercase instead of Title Case. This change impacts:
- pH/ORP dosing state sensor entities:
Dosing->dosingMixing->mixingMonitoring->monitoring- The
preset_modestate attribute for ScreenLogic climate entities, where raw states have also been underscored-spaced and had any punctuation removed. Solar->solarSolar Preferred->solar_preferredHeater->heaterDon't Change->dont_change
These changes support the addition of translation keys for text-based entity states. You should update any references to the above states/preset_modes to the new, lowercase versions.
Release notes from github.com/home-assistant/core/releases, and the official release blog, checked 17 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).