-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
New Home Assistant select entities all enabled by default #8083
Comments
The same could be said of the previous behavior of a sensor entity used to expose enums though, and that is still used to expose composite exposes. |
This has been corrected in #7684 and released in 1.20.0. These should be disabled by default, if this PR was on the Home Assistant side, it would not have been accepted in the state it was merged. |
Well, according to that PR, that behavior is not applied to the enum / text / composite expose types though. Personally, I'm not entirely sure if the entire category of enum exposes can be classified as to be disabled by default. In fact, when I authored that PR, I was mostly following existing behavior of those 3 expose types which are epxosed as sensor entities that were enabled by default. |
Actually, you are right! 👍
Maybe just enum isn't specific enough to decide on exposing it with, so instead, we can add them to the lookup table and handle it that way. |
What happened
Extracted this comment into this issue: #7980 (comment)
Introduced in #7980, also related to #8078
These entities are not really "common". As in, they can be useful, but probably most people won't use them in their automation or dashboards in general. Therefore, it is recommended to send a disabled by default in Home Assistant. This allows a user to enable them when needed, but not overwhelm the user with entities they do not need or pollute the (historical) database unneeded.
Can we adjust this for this feature before release it to the public?
What did you expect to happen
To have less common entities disabled by default, keeping setups nice and tidy.
How to reproduce it (minimal and precise)
Debug info
Zigbee2MQTT version: 1.20.0-dev commit: 46e2a77
Adapter hardware: Conbee II
Adapter firmware version: 0x26660700
The text was updated successfully, but these errors were encountered: