Skip to content
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: Entity categorization #12

Open
hockey6611 opened this issue Dec 21, 2021 · 0 comments
Open

Feature request: Entity categorization #12

hockey6611 opened this issue Dec 21, 2021 · 0 comments

Comments

@hockey6611
Copy link

hockey6611 commented Dec 21, 2021

Currently the noonlight switch is treated the same as any old switch in home assistant. It would be great if the integration could implement "Entity categorization" to help limit any accidental triggering. This was released with Home Assistant 2021.11.

Per the developer blog:

Entities which have the entity_category set:

Are not included in a service call targetting a whole device or area.
Are, by default, not exposed to Google Assistant or Alexa.
Are shown on a separate card on the device configuration page.
Do not show up on the automatically generated Lovelace Dashboards.

It seems to me that all of these would be nice to have for the noonlight switch. I have had experience with each of these (excluding not applicable #3). I have also had to manually exclude the noonlight switch from google home integration, and for some reason, home assistant decided my noonlight switch should be the default example for new lovelace cards. I think entity categorization would prevent this.
image

I would think that system would be the appropriate entity_category to set (developer documentation). One thing I'm not sure of, is since this integration is set via YAML only, I am assuming the entity_category can still be set, but I don't know this for sure.

Edit:
"#3" was used to reference the third item in the quoted list, not the issue 3, which was inserted but github. Correcting to not reference issue 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant