-
Notifications
You must be signed in to change notification settings - Fork 113
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
Hide some entities by default #256
Comments
This seems like a good idea to me. A blunter instrument would be to disable them (some of the new entities were added disabled by default in this same spirit). A principled stance would be best, i.e. lets take the entities per camera and break them into 3 categories (enabled by default, hidden by default, disabled by default) -- and agree on those 3 categories first, then implement it in 1 go. |
Yeah I am a fan of the principled stance, either way might be good to create a doc explaining the reasoning between the different categories and where the entity goes so future contributors have an idea and we have something to reference as well. |
Enabled by defaultPrincipleAnything required for usecases of the integration or card to provide an excellent "out of the box" experience when that usecase is likely applicable to the majority (>50%) of users of the TAM [Total Addressable Market] for the integration, or the card, individually. Experience the user will have
Hidden by defaultPrincipleAnything required for more niche/expert usecases for either the integration or card when that usecase is likely applicable to at least (25%) of the users of the TAM for the integration, or the card, individually. Experience the user will have
Disabled by defaultPrincipleAnything where the likely usage is < 25% of the TAM for either the integration or card. All disabled entities will also be hidden (so once manually enabled, will fall into the hidden category above). Experience the user will have
Example assignment of entities to categoriesSummary
CaveatsAbove heavily based on my own usecases. Adding some integration/card contributors for feedback on how the above matches their usecases: @NickM-27 , @felipecrs , @blakeblackshear , @peledzius , @drinfernoo |
Wow that's very comprehensive! Overall I agree, seems reasonable to me 👍 |
Impressive summary! I believe I would hide the following entities as well:
|
Personally, I feel like over 25% of users would use most of these. But with all those hidden the only thing not hidden by default is the camera view itself which to me makes less sense / too much the other way compared to what it is now, just my 2c though. |
Agree with Nick, suspect most of these are >25%. Moved |
Going to leave this open, as I temporarily avoided the use of hidden entities pending resolution of a Home Assistant frontend bug. More details in the PR: #273 Leaving this bug open for now. |
Hi, |
@Mincka Background: The |
Thanks for the explanation. I understand your point even it's a choice for the integration based on the card that people may not use at all. Anyway, it's only a matter of a few seconds to disable them. Also, disabling them by default makes them more difficult to discover in HA. |
One may claim the |
I think we'd love to have it hidden, too bad HA frontend behavior / bug means hidden is not an option currently |
Oh yeah, I forgot it. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Can this issue be reopened while we wait for home-assistant/frontend#12887? |
The Home Assistant fix appears to be merged now 😄 |
Is your feature request related to a problem? Please describe.
The Frigate integration provides lots of entities, so that we can automate everything we want. But, I noticed that some entities aren't exactly "user friendly" (not sure if it's the right way to call it or not), but instead only "automation friendly".
Some examples are:
And the problem that arises because of it is:
Describe the solution you'd like
This is exactly what HA 2022.4 tried to solve by bringing the Hidden entities feature:
I believe everything but the main cameras (this is debatable of course) could be hidden by default.
Describe alternatives you've considered
To hide them all myself. It's very hard though (in my installation, Frigate integration provides 339 entities).
Additional context
I would be happy to hear opinions about it.
The text was updated successfully, but these errors were encountered: