Open Abba- opened 3 months ago
I’ve run into this too. It causes problems when the failure is minor and non fatal, and the automation then fails to run the next step in a sequence that may be a very critical important step. So, I’m agreeing this is an important improvement.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Voting for this to be kept open...
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.
Can we unstale ?
I’ll reopen, it would be a nice improvement. Can’t say anyone will get to it anytime soon but it’s worth keeping as a a feature request/enhancement IMHO.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
unstale
Describe the bug
Without being able to dive into the code, I'm making a bit of an assumption here. I'm assuming that this plugin throws a generic error (vs a HomeAssistant specific error) when something isnt as expected.
HomeAssistant continue_on_error only handles HomeAsssistant specific errors. Sample discussion and 2.
So if any error happens (which can be a separate report, I seem to sometime get an error even though an action was successful), currently the whole script stops instead of being able to be 'caught' by HomeAssistant and continuing.
Sample error:
### (There is currently workaround by calling things script.turn_on)