You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps subjective, but I find very confusing from a UX POV (and also kinda useless), that the card's main label still shows the current state value when grouping and using an aggregating function, instead of a value relevant to the aggregation. E.g.: when grouping power consumption by date over 7 days, the main label should allow to display the overall consumption over the total period.
In terms of configuration/UX, I think there's a simple and elegant way to achieve that: the aggregate_func config at the entity level should be the only the config for the entity, not an override, defining how the value is calculated for each group. And the aggregate_func config at the root level should define how the value is computed for the entire graph (main label).
The text was updated successfully, but these errors were encountered:
Perhaps subjective, but I find very confusing from a UX POV (and also kinda useless), that the card's main label still shows the current state value when grouping and using an aggregating function, instead of a value relevant to the aggregation. E.g.: when grouping power consumption by date over 7 days, the main label should allow to display the overall consumption over the total period.
In terms of configuration/UX, I think there's a simple and elegant way to achieve that: the
aggregate_func
config at the entity level should be the only the config for the entity, not an override, defining how the value is calculated for each group. And theaggregate_func
config at the root level should define how the value is computed for the entire graph (main label).The text was updated successfully, but these errors were encountered: