codechimp
(Andrew Jackson)
December 1, 2024, 10:51am
1
When you create or edit an automation there is no way to add the categories, labels, icons or description whilst you are creating it, meaning you have to go back to the automations list, find what you’ve just created and add them. Quite easy to miss and doesn’t encourage good organisation.
Currently, there is not an option to assign a category when creating a script or automation or helper. One must complete creation of the item and then assign the category. Let’s integrate category assignment into the creation flow.
AJediIAm
(Jaap)
December 3, 2024, 6:12pm
4
I thought I created an architectural proposal or feature request for something similar when creating helpers, but I can’t find it.
This is the screenshot I created to show what it could look like.
Please also include helpers…
3 Likes
codechimp
(Andrew Jackson)
December 3, 2024, 6:24pm
5
Yes, actually anywhere you can set these, scripts and scenes need it as well.
poebae
December 5, 2024, 12:23am
6
Also why can’t we assign categories to multiple automations at once with checkboxes?
You can… use the “Enter Selection Mode” button…
Select the automations, then use the “Move to Category” dropdown…
1 Like
Yes! Whenever a new device is discovered I’m prompted to give it an area, so whenever a new automation is created why can’t I give it an icon/category without having to go out, 3 dots, settings, then edit it? This would streamline automation creation for me.
1 Like
poebae
December 5, 2024, 5:52am
9
Haha thanks, I did have a feeling it existed and I was missing it
I’ll take the L so other fools like me can find it!
While we’re complaining about this area, the process to rename a category (by clicking on Filters) is far from intuitive.
kippuh
(kippuh)
December 5, 2024, 12:18pm
10
On top of that. I dont see the option to add an automation to a category once you have the automation open for edit.
I have to go to the Automations tab, en hit the 3 dots at the end to add an automation to a category.
Pssst… there might be something cooking
home-assistant:dev
← jpbede:automation-script-add-category-labels
opened 10:59AM - 10 Dec 24 UTC
## Proposed change
Add category and labels to the automation/script save and re… name dialog. This way, a user can set the categories/labels at the time of creation and does not have to return to the list to do so.
Additionally this PR declutters the dialog, hides the optional parameters and make them addable via chips.
This is the first PR. There will be a second PR, when we've the possibility to catch the user when he wants to navigate away.
Worked closely with @matthiasdebaat on Discord on this, the redesign is based on his design.
WTH: https://community.home-assistant.io/t/wth-can-you-not-add-categories-labels-etc-when-creating-an-automation/802562
| ![image](https://github.com/user-attachments/assets/2394db58-bf26-43e1-a758-376d696421c9) | ![image](https://github.com/user-attachments/assets/2eca88c5-c78a-4ca2-aae7-6589f63f8751) |
|:-:|:-:|
| ![image](https://github.com/user-attachments/assets/16d04fca-e729-4799-8283-a7b700bd5efd) | ![image](https://github.com/user-attachments/assets/aaeca0ae-6e67-4eaf-b192-0db72c504387) |
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] Bugfix (non-breaking change which fixes an issue)
- [x] New feature (thank you!)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example configuration
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [x] The code change is tested and works locally.
- [x] There is no commented out code in this PR.
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
7 Likes
etauker
(Tautvydas Kersulis)
December 11, 2024, 1:55am
12
Would love to extend this to include labels as well.
potelux
(Potelux)
December 11, 2024, 1:45pm
13
Dude…you’re a machine. Cranking out PRs for these WTHs left and right.
@codechimp – jan-philipp.benecke’s post should be marked as the solution.
1 Like
codechimp
(Andrew Jackson)
December 26, 2024, 11:19am
14
Thanks @jan-philipp.benecke so much for your work on this WTH, I’ve been playing around with it in beta and it’s working really well. Labels and categories will never be forgotten now.
1 Like