Why are the traces of an automation so complicated to read

Month of "What the heck?!"
1

When trying to understand why an automation did not work as expected the traces are the place to go. Nevertheless i find it unnecesary complicated to read them.

When there are multiple conditions it uses the term conditions/0, conditions/1 etc. instead of showing the condition itself.

Or instead of saying choice 1 (see screenshot) just list the name of the choice e.g.
Choice “Reinigung am Morgen”.

debug
debug1862×998 95 KB

Some additional example are shown in this thread:

Best regards and thank you for this great piece of software!

I think making these more readable would improve the user experience a lot.

5

Don’t forget to vote for your own WTH.

1 Like
6

I’d like them to be more useful.

I think traces only shows last 3 triggers. Whenever I’ve tried to find issue it seems the incident I’m looking for is no longer available or gets overridden while I’m testing

And yes, the ui navigation seems weird and non obvious.

7

Last 5, you can alter (yaml only) as well.

1 Like
8

I’ve mentioned regarding this in particular to the conditions WTH can’t trace view on conditions be easier to understand - Month of “What the heck?!” - Home Assistant Community

9

One super annoying thing with trying to read traces is that the tree on the left does not scroll independently from the code/results view on the right. WTH?

The tree rendering also tends to be broken/misaligbed more often than not, at least in Safari/WebKit powered views on my Mac.

1 Like
10

Same here, this is probably a bug in the UI.