Automation not running on state attribute change - what am I doing wrong?

Actually, without a to or from, it will trigger for any change in the attribute’s value.

The purpose of the experiment was simply to confirm that the value true is being misinterpreted.

Put this back in and see if it still works. Note that there are no quotes wrapping true. If the Automation Editor automatically adds them then the experiment will prove nothing. You may need to edit it in YAML mode to ensure true has no quotes.

    to: true
    for: '00:00:10'

The theory here is that the attribute’s value is a boolean true but the trigger’s to: 'true' is looking for a string true. We want the trigger to look for a boolean true.

1 Like