Skip to content

Show automation result summary in the picker#51742

Open
karwosts wants to merge 2 commits into
home-assistant:devfrom
karwosts:automation-picker-summary
Open

Show automation result summary in the picker#51742
karwosts wants to merge 2 commits into
home-assistant:devfrom
karwosts:automation-picker-summary

Conversation

@karwosts
Copy link
Copy Markdown
Member

@karwosts karwosts commented Apr 27, 2026

Proposed change

I was thinking I would like a better way to get an at-a-glance overview of my automations to see if any of them are struggling or hitting errors unexpectedly. I thought maybe this could be a good use for a small icon in the picker overview to give some kind of result status of the recent automation runs.

In this proposal:

  • fetch the list of all recent automation traces when opening the automation picker
  • If at least one trace ran to completion (defined as running to the end, or aborting in a controlled way), and no traces have an error: green checkmark
  • If all traces that ran ended with an error: red alert circle
  • If some traces successfully completed, and some traces ended with an error: yellow warning triangle
  • If there is no traces, or no trace passed conditions: show nothing

Screenshots

image

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New feature (thank you!)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue or discussion:
  • Link to documentation pull request:
  • Link to developer documentation pull request:
  • Link to backend pull request:

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • I have followed the perfect PR recommendations
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

To help with the load of incoming pull requests:

@karwosts karwosts added the Needs UX Items requiring a review from the Home Assistant design team label Apr 27, 2026
@karwosts
Copy link
Copy Markdown
Member Author

Another idea is maybe combine this with the robot icon on the left, though that is already conveying entity state, like on/off/missing/unavailable, not sure if that would be overloading too much into a single icon, but I'm open to other ideas.

@nielsrowinbik
Copy link
Copy Markdown
Member

Hey @karwosts, @marcinbauer-ohf and I took a look at this and we like where this is going, and it aligns really well with our upcoming roadmap initiative OpenHomeFoundation/roadmap#32.

We haven't had the time to really start thinking about it, but your PR is a great starting point and we have a few thoughts that we think could improve it:

  • Regardless of what we do in terms of icons, colours, etc, we think the "health status" should be a column of its own, with a heading, and support for sorting, filering, and grouping.
  • We wonder if it would be better to reduce the status to two options: "healthy" and "needs attention". Perhaps it doesn't really matter if an automation fails sometimes or all the times, either way you would probably want to check it out.
  • We think we should set grouping by the health status as the default (unless the user has configured something else) and display the automations that need attention at the top.
  • We wonder if it'd be possible to somehow include a number of failed traces to indicate the severity of the problems (and perhaps that could be used in sorting, too)?

@marcinbauer-ohf will add a comment with some thoughts on the visual aspect of this later.

@BBE-FR
Copy link
Copy Markdown

BBE-FR commented Apr 28, 2026

I like it a lot ! looking forward to this interesting feedback from the picker !

  • We wonder if it'd be possible to somehow include a number of failed traces to indicate the severity of the problems (and perhaps that could be used in sorting, too)?

Or percentage of failed traces (if the user has increased the number of traces for a few automations, just the number could be misleading) :
100% <=> red circle above (even if red is not kept)
0% <=> green check above
any other <=> amber warning above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Needs UX Items requiring a review from the Home Assistant design team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants