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

Error handling when adding automations to category or label fails #20434

Closed
3 of 4 tasks
klaasnicolaas opened this issue Apr 5, 2024 · 0 comments · Fixed by #20494
Closed
3 of 4 tasks

Error handling when adding automations to category or label fails #20434

klaasnicolaas opened this issue Apr 5, 2024 · 0 comments · Fixed by #20494
Assignees

Comments

@klaasnicolaas
Copy link
Member

klaasnicolaas commented Apr 5, 2024

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

At the moment there doesn't seem to be any form of error handling available when you want to assign labels/category to an automation. But for certain reasons it didn't work out. For example, with automations that are made entirely in YAML and without an ID.

This automation cannot be edited from the UI, because it is not stored in the automations.yaml file, or doesn't have an ID.

Describe the behavior you expected

A pop-up or other form of error handling that makes it clear to users that the chosen automations cannot be added to a category or label

Steps to reproduce the issue

On the automations page:

  1. Click on selection mode
  2. Select automations that are created entirely in YAML and have no ID.
  3. Choose the category you want to assign at the top
  4. Nothing happens...

What version of Home Assistant Core has the issue?

2024.4.0

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

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

The console log in Chrome does show the following message:

image

Additional information

No response

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

Successfully merging a pull request may close this issue.

2 participants