-
Notifications
You must be signed in to change notification settings - Fork 120
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
Bug: Light group lists all supported_color_modes #189
Comments
I'm not sure how to solve this. It does, however, correctly list the available color modes. supported_color_modes: color_temp, hs, rgbw, rgbww, white, xy |
I would expect the group view to show the lowest common denominator of the group, i.e. only the features, that every member of the group supports... in my case it would only be a on/off toggle, if every member supported brightness then show also that bar etc etc.. |
Right, that makes sense. You can't change the color for every light in a group if half of the group doesn't even support color. I just checked what HA does, they do the opposite, they use the greatest common denominator. demo rgbww light, group gets full color functionality of rgbww, hue temperature light in the mix, hue color lights supported_color_modes: color_temp, hs, rgbw, rgbww, white, xy |
Interesting.. (obviously) same for me however it doesn't really make a lot of sense to me when you e.g. increase the brightness of the group from say 50% to 60%, all the on/off lights just come on at 100% (nothing else they can do). I understand wanting to make the behavior consistent with HA but that doesn't mean the HA implementation makes a ton of sense :) |
Yeah, will fix that
I'm just trying to understand why they chose that approach. It's more complicated to check all the children of a group to see what they support and then compare them to each other, rather than simply checking the group's "supported_color_modes." Perhaps that's the reason; it's just simpler. |
Looks like the group header is picking up multiple "Color" options from the members:
Originally posted by @Plawasan in #177 (comment)
The text was updated successfully, but these errors were encountered: