petro
(Petro)
January 3, 2024, 8:42pm
305
FYI Paulus (Balloob) mentioned in the release thread for 2024.1 that they are aware of this feature request. They are looking into the current options and weighing out the pro’s and con’s. All the current methods they’ve discussed don’t check all the boxes and they want to vet out all possibilities before building something in. The team is hopeful that something may be added this year to address this FR. It’s not guaranteed that this FR will be added this year but he seemed very hopeful.
9 Likes
FPro
(Florian)
January 5, 2024, 10:31am
306
It wasn’t in the thread, it was at the release party: https://www.youtube.com/watch?v=dRwzSkKYIDs&t=2280s
1 Like
This has been asked before, but good lord–this should not be that difficult. Can we please be able to put our hundreds of UI automations into FOLDERS? Or at LEAST be able to sort them by: enabled/disabled, date since last updated etc.??
1 Like
Olivier1974
(Olivier Toussaint)
January 6, 2024, 9:55am
309
The Nabu team said that they are working on it, ETA this year.
Listen to the time marked video posted by Florian in post #302
This topic is closed.
3 Likes
grahamj
(Graham J)
January 6, 2024, 2:43pm
310
I should hope they’re aware by now as the OP was from 2019
Very much looking forward to this when it arrives; thanks in advance!
petro
(Petro)
January 6, 2024, 3:01pm
311
It’s been known for many years and actively worked on throughout that duration. I’ve stated this multiple times in this thread but no one reads my responses. They just come in here to say +1 or complain. It would be great if people would just vote, read the marked solution, and move on without drama.
grahamj
(Graham J)
January 6, 2024, 3:58pm
312
It was your response that brought me here. No drama intended.
petro
(Petro)
January 6, 2024, 4:02pm
313
It was a general statement, not directed at you
Protoncek
(Pavel)
January 7, 2024, 7:58am
314
Well, it’s hard to say that it’s been “actively” working… more like “passively”… in 4 years almost half of HA could be made, not just one automations list upgrade… let’s say that all these years it was way down on the priority list…
But, hey, it’s finally confirmed that it will be done, so congrats and thanks for that. Looking forward to it…
1 Like
MrDadShot
(callum)
February 11, 2024, 11:02am
315
Having rudly had my post removed due to “duplicate” I came looking for the duplicate to find this 4 year old thread showing that even now the feature is still wanted and not being addressed. In the space of 4 years a simple sub-folder system could have been implimented, im not sure what they are avoiding this for but i feel like its being actively shut down.
Olivier1974
(Olivier Toussaint)
February 11, 2024, 11:19am
316
You did not read the post closely enough
1 Like
petro
(Petro)
February 18, 2024, 3:35pm
317
There is a very good chance that Floors, Tags/Labels, and Categories (folders for frontend) will come soon. It may be as early as 2024.3 or 2024.4.
13 Likes
jolle
February 25, 2024, 11:51am
318
would be very useful. Voted.
This feature delay is bordering on the ridiculous. Every single HA youtuber complains about this. The devs are overcomplicating this feature apparently. PUT THE AUTOMATIONS IN SIMPLE FOLDERS. Period. HA is getting to be a pain in the rear to use. Why push users to use UI automations if it’s impossible to manage them? And obviously this topic has NOT BEEN SOLVED.
1 Like
petro
(Petro)
March 6, 2024, 6:00pm
320
Calm down. I gave an update 17 days ago stating that it would be in a soon to come release. It missed 2024.3, it will likely be in 2024.4 but may be delayed until 2024.5.
2 Likes
or in .6, or in .7, or… oh, well… we’re used to hear this now…
(btw…it’s 2024 .4, not 2023.4 )
petro
(Petro)
March 6, 2024, 6:09pm
322
Unlikely but possible. There’s a very large developer push for this at the moment. Testing and issues are the only thing that will delay it. Many of the features currently exist in the backend.
3 Likes
potelux
(Potelux)
March 12, 2024, 4:08pm
323
I looked to find the implementation branch or other developer discussion regarding the implementation of this. I could not find it.
Additionally, I have thought through (what I believe to be) a robust solution to this problem that would be flexible and require minimal modification to the existing UI and backend. I would love to be a part of the discussion and share my solution. It would also be an honor to work on this highly requested feature (I have a background in Python, React, and back-end programming).
Could you please assist by providing links to the current development discussions or branches so that I can offer my services?
Thank you in advance for your help.
petro
(Petro)
March 12, 2024, 4:20pm
324
floors (top 6 or so in the list)
https://github.com/home-assistant/core/pulls?q=is%3Apr+floors
labels
There is probably more label PRs that are older. It’s been being implemented for multiple years at this point.
These 2 are the most recent dating only a few days/weeks back.
home-assistant:dev
← home-assistant:frenck-2024-0241
opened 05:08PM - 20 Feb 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Follow up of #110821, originally split out of #69996
This PR adds the `labels`, `label_id`, and `label_name` template methods, that are similar to their area counterparts. Additionally, `label_entities`, `label_devices`, `label_areas` are available.
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
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)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## 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:
- 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] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] 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]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [x] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
home-assistant:dev
← home-assistant:frenck-2024-0230
opened 09:33PM - 17 Feb 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue in the
additional information section.
-->
Split out and iteration of #69996
Adds the concept of labels to Home Assistant.
Labels are basically a "tagging system", however, we avoid the term "Tags", as that is used in Home Assistant for NFC and such already.
Where floors & areas represent your physical home, labels do not. Any area, device or entity can be tagged with one or more labels.
Labels can be defined freely and are not bound to a physical space. You can decide how you use them. Maybe you want to have labels for marking mood lights, energy-inefficient equipment, holiday decorations, and whatever you can think of.
A label consists of:
- Label ID
- Name
- Icon
- Color
- Description
This PR contains:
- The label registry.
- Adjustment for the area registry to support labeling areas.
- Adjustment for the device registry to support labeling devices.
- Adjustment for the entity registry to support labeling entities.
- The WebSocket API for the frontend to manage them.
Follow-up PRs will be made that allow the use of labels in templating and targeting areas in service calls.
Inspiration comes from GitHub Labels:
![image](https://github.com/home-assistant/core/assets/195327/25e1148e-3754-499b-9e97-af61df9b40b7)
## Type of change
<!--
What type of change does your PR introduce to Home Assistant?
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)
- [ ] New integration (thank you!)
- [x] New feature (which adds functionality to an existing integration)
- [ ] Deprecation (breaking change to happen in the future)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## 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:
- 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] Local tests pass. **Your PR cannot be merged unless tests pass**
- [x] There is no commented out code in this PR.
- [x] I have followed the [development checklist][dev-checklist]
- [x] I have followed the [perfect PR recommendations][perfect-pr]
- [x] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [x] 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]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [x] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/development_checklist/
[manifest-docs]: https://developers.home-assistant.io/docs/creating_integration_manifest/
[quality-scale]: https://developers.home-assistant.io/docs/integration_quality_scale_index/
[docs-repository]: https://github.com/home-assistant/home-assistant.io
[perfect-pr]: https://developers.home-assistant.io/docs/review-process/#creating-the-perfect-pr
discussions happen here for the backend. Frontend has it’s own discussion section in the frontend repository.
1 Like