-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request show helpers not used in any automation or lovelace #118
Comments
Why not using an already availably possibility of filtering entities by entity_id? |
Sorry, I didn't understand what means " filtering entities by entity_id" in this context. Tks |
https://github.com/dummylabs/thewatchman?tab=readme-ov-file#ignored-entities-and-services-option-example |
You did not understand my request. But that's ok, I coded the solution and solved the problem. |
@fcortijos - I understand what you were asking for. The exact opposite of what watchman does - entities that exist but aren't referenced anywhere rather entities that are referenced that don't exist (which is what watchman does). For the UI "Unused entities" on the dashboard menu is supposed to fill that need but it isn't very useful because you can't filter it by domain or anything else (maybe a good core FR?). That wouldn't help you with helpers or template entities) you have created that aren't referenced in automations or scripts though. It's a good idea. I'm curious how you solved the problem? |
@jazzyisj - I'm glad that you understood my proposal. My solution was quick and dirty, not for general use. A simple python program that reads the automations.yaml e lovelace files looking for my helpers and templates entities. I print how many times each entity was found in these files, if none, that is an "issue". |
Please consider including this feature:
show the helpers (input_boolean, input_button, input_datetime, input_number, input_select, input_text, sensor, timer, etc.) that are not used in any automation or lovelace.
tks
The text was updated successfully, but these errors were encountered: