I have various color model conversions. I think the one I am using matches the HS HSV and comes from the ,NET library with method GetBrightness. I will review again.
In either case the problem of a change in master brightness on WLED UI is reported as only a brightness change without any change in the reported RGB color. Similarly a RGB color command does not affect the WLED master brightness. No matter what RGB value is sent the status feedback for /g (brightness) never changes. Since the LEDs do seem to track the RGB commanded shade of color there should be some deterministic way to achieve an acceptable integration.
From a user’s perspective it is a good thing to have the controls independent so a user can increase brightness without changing hue/saturation or change from red to blue while still keeping the brightness the same. With this operational model it would make sense to use HSB/HSL for the LAN control rather than RGB. I suspect that users interested in integration requested RGB because that is what their automation systems used.
In either case the problem of a change in master brightness on WLED UI is reported as only a brightness change without any change in the reported RGB color. Similarly a RGB color command does not affect the WLED master brightness. No matter what RGB value is sent the status feedback for /g (brightness) never changes. Since the LEDs do seem to track the RGB commanded shade of color there should be some deterministic way to achieve an acceptable integration.
From a user’s perspective it is a good thing to have the controls independent so a user can increase brightness without changing hue/saturation or change from red to blue while still keeping the brightness the same. With this operational model it would make sense to use HSB/HSL for the LAN control rather than RGB. I suspect that users interested in integration requested RGB because that is what their automation systems used.
Comment