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.
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.
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.
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:
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![image](https://user-images.githubusercontent.com/28613898/147007578-b29566df-75e9-447c-98c1-17ce8b2f2059.png)
#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.I would think that
system
would be the appropriateentity_category
to set (developer documentation). One thing I'm not sure of, is since this integration is set via YAML only, I am assuming theentity_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.