Home Assistant Core 2025.3.0 → 2025.4.0

Automation & script variable scopes

The variables action is no longer restricted to local scopes; it can now update the value of a variable also in outer scopes. If the variable was not previously defined, it will be created in the top-level (script run) scope.

actions:
  - variables:
      x: 1
      y: 1
  - sequence:
    - variables:
        y: 2  # Updates y, which exists in the outer scope
        z: 2  # Since z is not defined yet, it is assigned in the top-level scope
  - action: persistent_notification.create
    data:
      message: "{{ x }}, {{ y }}, {{ z }}" # x=1, y=2, z=2
      # Note: previously, it would be: x=1, y=1, z undefined

If you have automations or scripts that use the same variable name in different (previously isolated) scopes, you will need to update them: simply use distinct variable names to prevent any conflicts.

(@arturpragacz - #141114)

Jewish Calendar

Holiday sensor changes:

• In Israel, "Simchat Torah" is now "Shmini Atzeret, Simchat Torah"
• In Israel, the 30th of Shvat returns "Family Day, Rosh Chodesh"

Additionally, the type_id has been removed from the state attributes, use the type if needed instead.

(@tsvi - #137247) (documentation)

Persistent notifications

Persistent notifications with notification_id config_entry_reconfigure are no longer created when an integration fails to authenticate. Automations triggering on such persistent notifications will thus no longer work.

(@emontnemery - #140932) (documentation)

Reolink

The Reolink password is now limited to 31 characters. The latest versions of the Reolink app and desktop client also have this 31-character limit. If you configured your Reolink password years ago, it is possible it is longer than 31 characters. In that case you will get a reauthentication flow asking you to change the password. Passwords longer than 31 characters can cause issues in the latest Reolink API.

(@starkillerOG - #140789) (documentation)