If anyone wants to make a makeshift Color Temperature tile ...
Create a virtual dimmer
Create a new rule with variables (for target CT, and dimmer value):
a. [Trigger: Virtual Dimmer level changes]
b. [Action 1: [Variable Math: 2700+(38 * Dimmer Level)]
c. [Action 2: [Set Color Temperature to result of previous action]
You can replace 2700 with whatever the low-end of your color temperature is, and replace 38 with the range of your color temperature divided by 100. (6500 - 2700 = 3800/100 = 38)
E.G - For Lightify bulbs:
e.g. 7000 - 1800 = 5200 = 52
The variable math would be: 1800 + (52 * Dimmer Level)
I have exactly the same suggestion but would add that the range of color temperature allowed in the existing template is much wider than that supported by the bulb. This causes odd behavior like the slider snapping all the way to the left if you set a value too high, while the bulb is actually set to it's highest possible value. There needs to be a way to inform the dashboard of the available range of the bulb so it can be properly controlled.
On SmartThings the CT was limited to 2700-6500K (I assume d/t something like this) which was horrible and one of the reasons me and my house full of Sylvania RGBWs moved to Hubitat. But anyway, it would be nice to have a CT bulb template, not that I really use the dashboard, but for people that do. It would seem likely that a particular bulb could change the parameters.
That's just the thing: All my bulbs (Osram/Sylvania tunable white) are limited to 2700-6500k. The wider range in the dashboard template does nothing to increase what the bulb is capable of. It just doesn't work properly outside the supported range. I want to reign in the dashboard to match the device. This worked properly on Wink, so I would like to think there is an attribute that can be read from the device. But it may have just been built in to their driver since it was Sylvania branded and such.
They may have just done what SmartThings did and limited the CT range of all bulbs, no matter what was supported by the bulb. Is this behavior with the Generic zigbee ct (dev) driver. You could try the Sengled element plus driver and see if it still has the same behavior. It should work, it just might be no better.
Actually, I just tried this with a Lightify under cabinet CT light and the problem is that the bulb is setting itself higher than the slider value, that is why it snaps to the left. It is reporting 6536, and the slider only goes to 6500. If it was expanded to 7000K you would probably not have this issue. I noticed that setting the slider all the way to the left caused it to return to 2700K, which is correct since that is the limit of the bulb. Maybe @bravenel could expand the slider a little further to 7000K, or 7100K since my bulbs top out around 7042K
My A19s go to 1500K and the strips go to 1600K on the Lightify gateway and HE. The only ones I have that only go to 1800K are the recessed HO RGBWs. This is one of my A19s:
We're clearly using different bulbs. I have 2 of the A19 Tunable White 60s and 1 Smart+ 18" Adjustable White Under Cabinet Light. All are specified as 2700K-6500K. On a side note, why on Earth would you want an 1800K light? It'll just be a disgusting brown. 2700K to me is already far too low. I use a range of about 3200K for warm white to 5000K for daylight. Lower looks too brown, higher looks too blue to my eyes.
All of the Sylvania bulbs (color and tunable white) say 2700-6500k on the box, don’t know why. The lower CT range is great for bedtime and middle of the night lighting. I have 8 modes set up that change the CT of all of the lights throughout the day using color prestaging. Similar to circadian lighting, but a lot easier to change if a brighter light is needed In the evening, due to far fewer CT changes. So, in the morning the lights start out at 2600K, 4000K midmorning, 5000K at noon, then 4200K, 3300K, 2700K, 2400K, and 1500-2000K for late night lighting.
@Ken_Fraleigh and others ... I've quickly tossed an app together that will let you do exactly what I listed above No need for variable math, and it's super lightweight.
In response to your 1800k option ... it's more red on my lights than anything (which is in line with our cinema-grade CT devices). It's really nice for nighttime lighting, I think. But, not much use of that for me—I just assign everything to be 100% red at night.
Just adding information some folks may never have seen - 1800k is supposed to be 'candle flame'
Althought why, without 'flicker' you'd set it... shrugs
No need for variable math, and it's super lightweight.
