I wish to group functionally related selectors in a blueprint together in a collapsible section.
This improves UX for users, minimise noise and decision fatigue.
Will also be nice to have collapsible selector serve as a section header.
My Example Blueprint
In this example blueprint, there are many options.
Each option can be categorised very nicely.
Eg:
Notification Configuration
Android Options
iOS Options
Users who only use android can easily skip the entire iOS group.
Same request applicable to Script Fields.
Blacky
January 26, 2024, 12:45am
2
I 100% aggree with @samuelthng
The implementation of collapsible sections could not only streamline my workflow but also enhance the overall usability for others. I’ve included a visual representation below for a clearer understanding.
Blueprint inputs
Input 1
Dynamic Lighting
Input 4
Conditions
Input 7
Night Lights
Input 9
Blacky
5 Likes
hazio
February 11, 2024, 11:32am
3
+1, this really needs to be implemented for ease of use. It get’s quite overwhelming when there are too many text and options on a single page. Collapsing will give the ability to minimise options that you might not need, and expandability when required.
karwosts
February 14, 2024, 1:52am
6
I’ve started a proposal for this in HA core, to allow for blueprint input sections.
Feel free to see if the schema suggested there would meet your needs, or if you have any other suggestions I missed.
home-assistant:dev ← karwosts:blueprint-sections
opened 01:51AM - 14 Feb 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
Add an optional section to blueprint definition called `input_sections`, and allow inputs to optionally attach themselves to a particular section.
Authors of large blueprints sometimes claim that the current big flat list of all inputs becomes difficult to organize and can overwhelm users visually with number of options, and would like a way to organize them better. With collapsable sections, various related inputs can be visually grouped and collapsed to improve organization.
## 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:
https://community.home-assistant.io/t/is-there-a-way-to-add-headlines-separators-sections-in-blueprint-ui/674162
https://community.home-assistant.io/t/collapsible-selector-groups/634545
- 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.
-->
- [ ] The code change is tested and works locally.
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
- [ ] There is no commented out code in this PR.
- [ ] I have followed the [development checklist][dev-checklist]
- [ ] I have followed the [perfect PR recommendations][perfect-pr]
- [ ] The code has been formatted using Ruff (`ruff format homeassistant tests`)
- [ ] 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:
- [ ] 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
1 Like
Sir_Goodenough
February 15, 2024, 7:12pm
7
Add your opinion up there. Show your support! Show Nabu Dev team this is something we need.
Agree, this would be great.
pgale
April 12, 2024, 5:40am
9
This would be great. Current complex blueprints can be quite confusing to use if they have many options. Being able to better display them and candidate through the options would help hugely.
SimTechLP
June 9, 2024, 7:40pm
10
+1 ! Very good option.
Not sure about the interface if conditional display would be possible as well, such as:
But I don’t think that is possible though
