Support backoff integer parameter

The backoff parameter can be specified as either dynamic (using a template) or constant. Previously, constant values had to be provided as strings (for example, "10"). As of this release, constant values may also be provided as integers (for example, 10).

Full Changelog: v4.1.2...v4.1.3

HA 2026.1 compatibility

In Home Assistant 2026.1, the class TargetSelectorData was renamed to TargetSelection (by this PR).
This release of retry adopts the new class name when running on newer Home Assistant versions, while maintaining backward compatibility with older versions.
Without this change, the following deprecation warning is logged:
The deprecated class TargetSelectorData was instantiated from retry. It will be removed in HA Core 2026.12.0. Use TargetSelection instead. Please create a bug report at https://github.com/amitfin/retry/issues

Full Changelog: v4.1.1...v4.1.2

Fix serialization issue for retry.actions[on_error]

Fix for issue 237. Check issue for additional details.

Full Changelog: v4.1.0...v4.1.1

Filter indirect entities based on action's domain

Action's entities can be targeted indirectly by specifying their device, area, floor, or label. Such entities are now filtered based on the action's domain. For example, when the inner action is light.turn_on and the target is an entire floor, only entities belonging to the light domain will be passed to the inner action.

Full Changelog: v4.0.1...v4.1.0

v4.0.1

1. Fixed an issue that produced an incorrect error message when invoking retry.actions and retry.action from Developer tools → Actions.
2. An exception is now raised when a retry loop is canceled due to a duplicate retry_id, ensuring that subsequent steps do not continue when used inside automations or scripts.

Full Changelog: v4.0.0...v4.0.1

4.0.0

Breaking Change: retry.action now executes its retry loop(s) synchronously (blocking) instead of running in the background. This enables:

• Proper error propagation: The exception from the final retry attempt is now raised. When used inside automations or scripts, this will halt execution of subsequent steps unless continuing-on-error is enabled.
• Returning response data on success.

No configuration changes are required.
However, if you previously implemented workarounds to compensate for the old non-blocking behavior, you can safely remove them now.

Synchronous Execution

Breaking Change

retry.action now executes its retry loop(s) synchronously (blocking) instead of running in the background. This enables:

• Proper error propagation: The exception from the final retry attempt is now raised. When used inside automations or scripts, this will halt execution of subsequent steps unless continuing-on-error is enabled.
• Returning response data on success.

No configuration changes are required.
However, if you previously implemented workarounds to compensate for the old non-blocking behavior, you can safely remove them now.

Full Changelog: v3.8.0...v4.0.0

Remove support for legacy names and add variables for template rendering

• The legacy retry.call action is no longer supported. It has been deprecated for over a year now. retry.action should be used instead.
• The legacy parameter service is no longer supported. It has been deprecated for over a year now. action parameter should be used instead.
• The set of variables provided to backoff and validation special templates was extended, and it includes now: entity_id, action, attempt, and any other parameter provided to the inner action.

Full Changelog: v3.7.0...v3.8.0

2025.8 compatibility

HA core 2025.8 includes a code refactor which causes deprecation warnings when using retry actions. See also issues 197 & 198.

The code was changed accordingly to avoid the deprecation warnings.

Note: this release requires HA core 2025.8 (or newer) and can't be used with earlier HA core releases.

Full Changelog: v3.6.1...v3.7.0

Logbook improvement

The automation name is now properly presented in the logbook.

alias: Logbook Test
triggers:
  - trigger: event
    event_type: test_event
actions:
  - action: retry.actions
    data:
      sequence:
        - action: light.turn_on
          target:
            entity_id:
              - light.kitchen_main_light

Full Changelog: v3.6.0...v3.6.1

"ignore_target" parameter

A new parameter to disable target parameters processing which is needed in some rare cases (e.g. this). Full documentation can be found here.

Full Changelog: v3.5.0...v3.6.0