Home Assistant Core 2025.2.0 → 2025.3.0

Automations & scripts

The wait variable and variables defined by a response_variable set in an inner scope of a script or automation now propagate to outer scopes also if a variables action is present in the inner scope.

Furthermore, variables defined by a response_variable now also propagate out from parallel sequences. Scripts and automations which relied on the older (buggy) behavior might need to be adjusted.

(@arturpragacz - #138883)

GPSD

All state attributes of the main sensor were replaced with a dedicated sensor Home Assistant in 2024.9. The deprecated attributes have now been removed.

(@jrieger - #137600) (documentation)

Home Connect

Some programs and program switches (which are being deprecated) and program select entities may not be exposed anymore by the integration as they are missing an aiohomeconnect program key enumeration (file). You can get the diagnostics from the configuration entry or the device and open an issue or submit a PR with the generated diagnostics file on the aiohomeconnect repository to suggest the missing program(s).

(@Diegorro98 - #136116) (documentation)

---

Using program and option keys that aren't in the API documentation in Home Connect actions will no longer work. To be able to use undocumented program or option keys, open an issue or submit a pull request with the required keys at MartinHjelmare/aiohomeconnect.

(@Diegorro98 - #137027) (documentation)

---

Multiple Home Connect config entries will not be allowed to be configured. For regular users where all appliances in the home are connected to the same Home Connect account, there should not be any reason to have more than one config entry since all appliances in the home will be connected to the same account and config entry.

(@Diegorro98 - #137088) (documentation)

MQTT

Legacy color_mode support for MQTT JSON lights has been removed. The support was deprecated in HA Core 2024.4.

Users with a YAML setup have been instructed to update their configuration in configuration.yaml via repair issue flow. Deprecation issues with MQTT JSON lights set up through discovery were communicated via warnings in the logs. Using the removed parameters in discovery will not break the configuration but will still log a warning.

(@jbouwh - #136996) (documentation)

Proximity

The distance is now measured to the edge of the monitored zones (it takes the radius into account), instead of to the center of the zone as before. This leads to slightly different expected distance values, which you may have to adjust accordingly in your existing automations.

(@Spcemarine - #138819) (documentation)

SmartThings

The energy and power sensors have been removed for every device that has a switch. They rarely worked because there were no energy or power capabilities available to get data from. If you do have the capabilities, it will still work for you.

(@joostlek - #138313) (documentation)

---

There are a lot of states that have been renamed; this might need an update in your automations or other configurations.

• Set options for dishwasher job state sensor in SmartThings (#139349)
• Add translatable states to SmartThings media source input (#139353)
• Add translatable states to SmartThings media playback (#139354)
• Add translatable states to oven mode in SmartThings (#139356)
• Add translatable states to oven job state in SmartThings (#139361)
• Add translatable states to robot cleaner movement in SmartThings (#139363)
• Add translatable states to robot cleaner turbo mode in SmartThings (#139364)
• Add translatable states to washer job state in SmartThings (#139368)
• Add translatable states to dryer job state in SmartThings (#139370)

Synology DSM

The scan interval option has been removed, and the default of 15 minutes is used. If needed, there is an integration-independent and common way to set a custom polling interval.

(@mib1185 - #138490) (documentation)

TechnoVE

The status sensor state high_charge_period was renamed to high_tariff_period.

(@Moustachauve - #139314) (documentation)