WTH can't trace view on conditions be easier to understand

Step Details of a trace with multiple conditions can be very difficult to find the condition results you wish to check e.g.

Executed: 1 December 2024 at 07:51:52
Result:

result: true

conditions/0

Executed: 1 December 2024 at 07:51:52
Result:

result: true

conditions/0/conditions/0

Executed: 1 December 2024 at 07:51:52
Result:

result: true

conditions/0/conditions/1

Executed: 1 December 2024 at 07:51:52
Result:

result: true

conditions/0/conditions/1/conditions/0

Executed: 1 December 2024 at 07:51:52
Result:

result: false

conditions/0/conditions/1/conditions/0/entity_id/0

Executed: 1 December 2024 at 07:51:52
Result:

result: false state: ‘on’ wanted_state: ‘off’

conditions/0/conditions/2

Executed: 1 December 2024 at 07:51:52
Result:

result: true

conditions/0/conditions/2/entity_id/0

Executed: 1 December 2024 at 07:51:52
Result:

result: true state: ‘on’ wanted_state: ‘on’

Why can’t the elements such as conditions/0/conditions/2/entity_id/0 be changed to what it is in the GUI e.g.

Condition: Confirm light behind sofa is off

or just show the condition line shown with the result after;

  - condition: state
    entity_id: light.light_behind_sofa
    state: 'off'

Mentioned something like this at the feature request section too: Step names and aliasses in trace view of automations and scripts

1 Like

Not sure if it was the 2025.2 release as I can’t immediately find it in all changes, but now it shows the comment or default title! Easier to read now! (I’d personally prefer the text to be the largest and the if/condition/0 in the square brackets to be honest but still much better! :slight_smile:

Looks like it was added here:

Looks like it took a while to hit after the December release at least when I originally posted the WTH :smiley: