RGBW Values and custom presets stored and recalled as scenes?

[tgauchat (ActionTiles.com co-founder Terry @ActionTiles; GitHub: @cosmicpuppy)]

Though it’s a rambling discussion, you may have some luck joining the Topic below.

Basically… SmartThings Capability “Color Control” doesn’t support RGBW.

That doesn’t mean a Device Type Handler(s) and SmartApp(s) can’t do what you want, it means that there is currently no published & standard way of doing it. So your customer DTH for your strip and your SmartApp(s) won’t be compatible with anyone else’s unless you agree on doing it all the same way.

Is bulb in 'color' or 'white', i.e. colorTemperature, mode?

Is there a way for my SmartApp to determine if a bulb, I’m using Hue bulbs, is currently displaying white, set via colorTemperature, or a color, set via hue and saturation?

AND

Capability Color Control "color" Attribute & Command ambiguous, incorrectly documented, and/or improperly used in DTHs

Can of worms aside, If values are HSL 0-100, how is the W diode in RGBW getting assigned? It seems to me that we should be able to control RGBW across all four values 0-100 independently… Hue as a color value designator is a poor means of achieving a value that is replicate-able across various brands but I do see how it works well for crude color wheel use for the consumer. Difference between composite and component color values. Component is many times more accurate. Plus, why are they/we working in 100th value increments? shouldnt it be at least 0-255 across each color diode independently? (I dont mean pixel addressable, but more increments per channel.) Working with LED color assignments should be addressed in much more accurate terms than what is currently happening in the SmartThi…