frenck
commented
1 year ago This architecture issue is old, stale, and possibly obsolete. Things changed a lot over the years. Additionally, we have been moving to discussions for these architectural discussions.
For that reason, I'm going to close this issue.
../Frenck
Context
The issue motivating this decision, and any context that influences or constrains the decision. Your motivation cannot include that the frontend is not representing the data correctly, as that is a frontend issue.
issued this in https://github.com/home-assistant/core/issues/32433, but was suggested to first open here in architecture.
Proposal
The change that you're proposing.
light groups made by https://www.home-assistant.io/integrations/light.group/ are not distinguishable from regular light entities, based on the current attributes set in the states machine. This makes it more difficult than desired to create Lovelace cards based on various configurations, and automations have to explicitly exclude these light groups when issuing actions into the light domain. Maybe not a bug essentially but most certainly a missing property/attribute, which when added allows for more fine-grained action and control.
Consequences
What becomes easier or more difficult to do and any risks introduced by the change that will need to be mitigated.
If added, we can easily distinguish lights from light groups, and hence use that, both in backend templating, as in frontend card configs