Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to show/hide automations/scripts by state #23721

Open
4 tasks done
mrdarrengriffin opened this issue Jan 13, 2025 · 1 comment
Open
4 tasks done

Add option to show/hide automations/scripts by state #23721

mrdarrengriffin opened this issue Jan 13, 2025 · 1 comment

Comments

@mrdarrengriffin
Copy link
Contributor

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

For users who primarily used YAML and want to migrate to the UI, it can get cluttered to see all of the enabled and disabled automations. Most of the time, users are aware of what automations are disabled and only want to see their enabled automations, not just group them

Describe the behavior you expected

It would be nice to have a filter for "state" so users can keep disabled automations from cluttering up their list.

I think that by default, we should hide disabled automations but show a dismissible note to users that disabled automations will be hidden by default to improve UX

Steps to reproduce the issue

  • Go to Settings > Automations
  • No filter is present for showing and hiding disabled entities

What version of Home Assistant Core has the issue?

2025.1.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

@ildar170975
Copy link
Contributor

ildar170975 commented Jan 14, 2025

Agree that "enabled/disabled" should be added as a filter.
But this is not an ISSUE, it should be posted in Discussions (which is already there - #8889).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants