A gentle return to an old feature request - Color Temp names for CT bulbs

Back in 2021/22 I spent a great deal of time on the topic of CT bulb color names.

For me, this old topic never died - although I got so much ... um. pushback ... I felt the topic was too unworthy to pursue.
Recently, new tools in my tool chest have highlighted that old issue again for me. I've learned a lot since then and maybe me formulating the Feature Request differently will have a better reception.
HE has a color temp name table, which seems to be based on the same table it did back then.
Pulling CT name values from the public drivers shows me some basic names.
image

Okay. so thats fine. For those who remember numbers its easy to program a bulb to a color temp kelvin value, and the displayed value is whatever name comes with it from HE.

But my smart home is heavily integrated with other vendors. And while it's functional, it's not as easy as it could be to use. If I voice command a bulb to be 'cool white' - the displayed value on my dashboard is a color name I've no idea what it is (and neither does my girlfriend!) - here I've asked Alexa to set my living room 'Cool White' (this is the generic HE driver) and as the image describes it - I got 'Polar':
image

My feature request is this: Allow the CT colorname table to be 4 choices in settings. HE (default), Amazon, Google, and 'custom' (to allow a json file upload mayhaps?)

Internally - when a CT bulb displays the name of a color, it uses the table chosen. In this way, my dashboard which uses english names (not numeric values I can't remember!) becomes more reflective of my whole house, not just Hubitat.
Amazon standard:


Google Standard:
image
My current custom (hybrid) table I use for my CT bulb drivers:
image

I understand the driver provides the names, but it isn't fair to ask me to rewrite every driver - or expect my guests/Girlfriends and family to remember odd names. They are not code people, they barely understand the 3 color temp name choices of the bulbs at Home depot!

Let me be the first to offer some views.. I suspect you'll want to name it "pushback"... (See what I did there?? Two names for one subject?)

This is not dissimilar to Fan Speeds in my mind. "Please set the fan to 66%" and the fan shows as "medium" (if it's a 3 speed fan that has 4 speeds: Off, Low, Medium, Fast. The similarity to color is "Set the fan to 50%" and the driver is forced to decide if 50% is closer to 33% or 66%, and that's the speed of the fan.

I'm curious if you speak the color after translation, does it present the same color?? In other words, if you ask for "Cool White" and are presented with "Polar", if you ask for polar, do you get polar? Because if that's true, then an "overlay layer" of colors feels like an interesting option. Perhaps "alias" is a better word for the concept I'm imagining.

2 Likes

As far as I know, the only thing resembling this is the convertTemperatureToGenericColorName Common Method, which is available as a utility for Device drivers, but not required (as you have noted in your own CT bulb drivers example).

I'm not quite clear how this feature request could be realized without rewriting colorTemperature device drivers (at least any that don't currently use convertTemperatureToGenericColorName()).

Perhaps I am not understanding what you mean by: "Internally - when a CT bulb displays the name of a color ...".
Is "Internally" here referring to something other than the device/driver setting of the colorName attribute?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.