Skip to content

Conversation

@wendevlin
Copy link
Member

@wendevlin wendevlin commented Dec 23, 2025

Proposed change

  • Quick bar
    • use ha-picker-combo-box with sections
    • introduce mod/ctrl + K to open global search
    • add areas
    • split up commands and navigation
  • Shortcuts dialog
    • add global search
    • migrate to ha-wa-dialog - to prevent quickbar overlays it when clicked via the ha-tip
  • adaptive dialog: allow to set whole header slot
  • moved area_registry into data/area/area_registry
Screenshots image image image image image

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • 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

Additional information

  • This PR fixes or closes issue: fixes #
  • This PR is related to issue or discussion:
  • Link to documentation pull request:

Checklist

  • The code change is tested and works locally.
  • 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:

@github-actions github-actions bot added Demo Related to frontend demo content Design Related to Home Assistant design gallery labels Dec 23, 2025
@wendevlin wendevlin added the Noteworthy Marks a PR as noteworthy and should be in the release notes (in case it normally would not appear) label Dec 23, 2025
</ha-dialog-header>
<slot name="header" slot="header">
<ha-dialog-header
slot="header"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably no longer needed?

Comment on lines +182 to +199
export const areaComboBoxKeys: FuseWeightedKey[] = [
{
name: "primary",
weight: 10,
},
{
name: "search_labels.aliases",
weight: 8,
},
{
name: "secondary",
weight: 8,
},
{
name: "search_labels.domain",
weight: 4,
},
];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This no longer accepts using area id?

},
{
name: "secondary",
weight: 8,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
weight: 8,
weight: 6,

So aliases are higher, which may be the same as the floorname. This also matches the weight with what it was.

};

showQuickBar(this, {
mode: QuickBarMode.Command,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This quickbar should open in command (or navigate) mode.

@marcinbauer85
Copy link
Member

Nice @wendevlin ! Let's work on this for next release to make it more usable that the standard picker. A quickbar has more use cases than our pickers, so we should design for those. Think Apple spotlight or Raycast.

@marcinbauer85 marcinbauer85 self-assigned this Jan 7, 2026
@marcinbauer85
Copy link
Member

marcinbauer85 commented Jan 7, 2026

Please add the followinig changes:

  1. Filter order: Navigate Commands | Entities Devices Areas (just one separator, also order the results the same
  2. Change height of quick bar to: 620px
  3. Change shortcut description to: "Quick search" - "Search Home Assistant" is too generic, and by naming it "Quick search" we'll give it our "brand" name, it also implies speed and what its intent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Demo Related to frontend demo content Design Related to Home Assistant design gallery Noteworthy Marks a PR as noteworthy and should be in the release notes (in case it normally would not appear)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants