Skip to content

Add issue filtering to maintenance dashboard#51837

Draft
Brookke wants to merge 1 commit intohome-assistant:devfrom
Brookke:maintenance-issues-filtering
Draft

Add issue filtering to maintenance dashboard#51837
Brookke wants to merge 1 commit intohome-assistant:devfrom
Brookke:maintenance-issues-filtering

Conversation

@Brookke
Copy link
Copy Markdown
Contributor

@Brookke Brookke commented May 3, 2026

Breaking change

Proposed change

Introduces a way of filtering the entities down to ones that have problems. When the maintenance screen is accessed from the summary card the filter is applied by default

Screenshots

SCR-20260503-jimq-2

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

Additional information

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

Checklist

  • I understand the code I am submitting and can explain how it works.
  • The code change is tested and works locally.
  • There is no commented out code in this PR.
  • I have followed the perfect PR recommendations
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

To help with the load of incoming pull requests:

Comment on lines +35 to +37
:host([no-leading-icon]) {
--_with-leading-icon-leading-space: var(--_leading-space);
}
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

added this to fix an issue where the left spacing was wrong when the button was selected

Image

Comment on lines +285 to +301
.badge {
position: absolute;
top: -4px;
right: -4px;
inset-inline-end: -4px;
inset-inline-start: initial;
min-width: 16px;
box-sizing: border-box;
border-radius: var(--ha-border-radius-circle);
font-size: var(--ha-font-size-xs);
font-weight: var(--ha-font-weight-normal);
background-color: var(--primary-color);
line-height: var(--ha-line-height-normal);
text-align: center;
padding: 0px 2px;
color: var(--text-primary-color);
}
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

copied from src/layouts/hass-tabs-subpage-data-table.ts

Comment thread src/translations/en.json
"devices": "Devices",
"other_devices": "Other devices"
"other_devices": "Other devices",
"issues_only": "Issues"
Copy link
Copy Markdown
Contributor Author

@Brookke Brookke May 3, 2026

Choose a reason for hiding this comment

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

I, in a previous PR, swapped the maintenance summary card to say:

X low batteries, X unavailable devices

Here I have used issues. I could add two separate filter buttons one for low batteries one for unavailable devices. But longer term I wonder if just a single issues button is better.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant