Filtering missing from Unused Entities data table

SeanPM5 commented 7 months ago

Checklist

[X] I have updated to the latest available Home Assistant version.
[X] I have cleared the cache of my browser.
[X] I have tried a different browser to see if it is related to my browser.
[X] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

All data tables were updated with filtering support, but the "Unused Entities" table from dashboard edit mode appears to have been missed (screenshot below).

The new filtering and organization features would be very useful here, some example use cases:

Show all unused entities belonging to "Office" area when creating your office view
Show all unused entities belonging to "Sun" and "Pirate Weather" integrations when making your weather view
Show all unused entities with "Security" label (motion sensors, alarms, sirens, cameras etc) when creating a security dashboard

Describe the behavior you expected

Filter support like all other tables

Steps to reproduce the issue

Lovelace dashboard → Edit mode → Unused entities

What version of Home Assistant Core has the issue?

core-2024.4.0b3

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Chrome version 116.0.5845.187

Which operating system are you using to run this browser?

macOS Sonoma

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

bramkragten commented 7 months ago

This table is using a different component, as it is not a config page. Filtering can be added in the future, but is probably not in scope for this release.

github-actions[bot] commented 4 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 1 month ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / frontend