Improve error reporting in scripts and automations. #2946
Unanswered
wesleyRaposo
asked this question in
Other UI enhancements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the enhancement
Improve error reporting in scripts and automations.
In complex automations, it's common for scripts and automations to "break" when a device goes offline, an entity is removed, or a sensor undergoes an update that changes characteristics (such as the name).
When this happens, Home Assistant issues an error when the trigger or script is executed, giving clues as to where the error might be.
I have an automation that performs a long sequence of operations, and it's only triggered when HA initialization occurs.
It would be much easier if, when looking at the list of automations, I could see which automation broke. Or when looking at a list of scripts, I could see which one is incorrect. Or within a script or trigger, I could see which command failed.
This information is already in Home Assistant.
For example, my trigger failed because an old script was removed.
When clicking on the script call within the trigger, you can see that it has an error. But when looking at the list of trigger calls, it's as if everything is correct.
It would be great if the incorrect command was marked, for example, by turning red or displaying a warning symbol.
Use cases
As I described, complex triggers or complex scripts would be better analyzed if the error blocks were highlighted.
Visual examples
When selecting the block with the error, the situation is reported in the editor, but it is not visible when we only look at the trigger.

Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions