# LIFX binding - temperature dimmer doesn't cover full colour temperature range

**URL:** <https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330>\
**Category:** Bindings\
**Tags:** lifx, openhab3\
**Created:** [January 24, 2021, 8:57pm UTC](https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330 "2021-01-24T20:57:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![S13\_Mills](https://community.openhab.org/user_avatar/community.openhab.org/s13_mills/32/50052_2.png) [@S13\_Mills](https://community.openhab.org/u/S13_Mills)\
**Post date:** [January 24, 2021, 8:57pm UTC](https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330/1 "2021-01-24T20:57:38Z")

</div>

Hi Everyone,

I’m using OH3.0.0, and have a few LIFX lights in my setup.

The lights work as expected for the most part, except that the colour temperature (color for those in the US) doesn’t cover the full range supported by the lights - it maxes out at 2500K (temperature = 1.0 (number)/ 100 (on the dimmer slider)), when the lights can go down to 1500K. The other end of the scale is fine - temperature = 0 corresponds to 9000K, which is the coldest the lights support.

Steps to reproduce:

1. Set temperature to max in OH - LIFX app shows 2500K (expected 1500K)
2. Set temperature to min in OH - LIFX app shows 9000K (as expected)
3. Set temperature to 1500K in LIFX app, OH shows max (1.0 / 100)
4. Set temperature to max in OH - LIFX app returns to 2500K
5. Create a new item (number) for colortemperature channel, set to \>1, no change in LIFX or light

I use 1500K for dim light at night time and first thing in the morning, and would like to be able to automate this from OH, so I don’t have to use the LIFX app at all.

I can’t see any other mentions of this elsewhere - I don’t _recall_ this being an issue in OH2.5.x, but I can’t be sure about that… it seems more like a binding issue than an OH3 issue.

I am happy to submit a bug request if that’s needed - just wanted to check I’m not doing anything stupid first…

---

<div class="post-metadata">

**Author:** ![wborn](https://community.openhab.org/user_avatar/community.openhab.org/wborn/32/55946_2.png) [@wborn](https://community.openhab.org/u/wborn)\
**Post date:** [January 24, 2021, 9:05pm UTC](https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330/2 "2021-01-24T21:05:52Z")

</div>

The available temperature ranges depend on what kind of LIFX light you have and if it is properly detected by the binding.

The binding uses the temperature ranges as specified by LIFX, see:

> <https://github.com/LIFX/products/blob/master/products.json>

What light (pid) do you have and is it properly detected?

---

<div class="post-metadata">

**Author:** ![S13\_Mills](https://community.openhab.org/user_avatar/community.openhab.org/s13_mills/32/50052_2.png) [@S13\_Mills](https://community.openhab.org/u/S13_Mills)\
**Post date:** [January 24, 2021, 9:26pm UTC](https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330/3 "2021-01-24T21:26:12Z")

</div>

Hi @wborn , thank you for the fast response!

In the current setup, I have 3 x BR30 (PID: 63) and 2 x Mini Color (PID: 49). My LIFX app gives me the option to go down to 1500K with both of these types. Both are properly detected in OH:

 ![LIFX_Entrance_Info](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/c/4/c437948ca007239a6e04a56678e9893a7e6602ec.png)

I can confirm that for the LIFX original and LIFX +, that 2500K is the floor (I have some of these in another setup).

It’s super odd that LIFX themselves have this set to 2500K - I wonder if they maybe forgot to update it after a firmware update?

What’s the right thing for me to do next? Create a PR for the LIFX products? Does the binding refer directly to the products.json? Or just use the values from it?

---

<div class="post-metadata">

**Author:** ![wborn](https://community.openhab.org/user_avatar/community.openhab.org/wborn/32/55946_2.png) [@wborn](https://community.openhab.org/u/wborn)\
**Post date:** [January 24, 2021, 9:45pm UTC](https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330/4 "2021-01-24T21:45:53Z")

</div>

I’ve created this issue for it:

> <https://github.com/LIFX/products/issues/12>
>
> Hi @delfick!
> 
> In our openHAB community a user \[reports\](https://community.open…hab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330?u=wborn) that the temperature ranges of the \[Mini Color (pid 49)\](https://github.com/LIFX/products/blob/2adf13f024ad0ff663a3c10f2a0704cc9e472f33/products.json#L376-L390) and \[BR30 (pid 63)\](https://github.com/LIFX/products/blob/2adf13f024ad0ff663a3c10f2a0704cc9e472f33/products.json#L541-L555) are 1500K-9000K in the LIFX App whereas the products.json lists these as 2500K-9000K.
> 
> Can you check if this is an issue in the products.json? Maybe there are similar issues?

> [@S13\_Mills](#):
>
> Does the binding refer directly to the products.json? Or just use the values from it?

It doesn’t directly use it but the values are based on that file. I will then update the file used by the binding based on the updated `products.json` file. Maybe there is more to update besides these 2 lights. 🙂

---

<div class="post-metadata">

**Author:** ![S13\_Mills](https://community.openhab.org/user_avatar/community.openhab.org/s13_mills/32/50052_2.png) [@S13\_Mills](https://community.openhab.org/u/S13_Mills)\
**Post date:** [January 24, 2021, 11:00pm UTC](https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330/5 "2021-01-24T23:00:25Z")

</div>

Fantastic! Thank you very much for this, amazing support 😃

Have a great weekend! I’ll wait for the fix, and mark solved when it’s in.

---

<div class="post-metadata">

**Author:** ![wborn](https://community.openhab.org/user_avatar/community.openhab.org/wborn/32/55946_2.png) [@wborn](https://community.openhab.org/u/wborn)\
**Post date:** [March 24, 2021, 11:17am UTC](https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330/6 "2021-03-24T11:17:15Z")

</div>

I’ve created a PR for supporting features based on firmware versions in the binding as defined by LIFX in the `products.json`:

> <https://github.com/openhab/openhab-addons/pull/10384>
>
> When the firmware of a light is upgraded the supported features can change.
> Wit…h these changes the binding uses the features based on the light firmware version.
> Also corrects some of the temperature ranges based on the LIFX products description.
> 
> See: https://github.com/LIFX/products/issues/12

---

<div class="post-metadata">

**Author:** ![S13\_Mills](https://community.openhab.org/user_avatar/community.openhab.org/s13_mills/32/50052_2.png) [@S13\_Mills](https://community.openhab.org/u/S13_Mills)\
**Post date:** [March 24, 2021, 6:55pm UTC](https://community.openhab.org/t/lifx-binding-temperature-dimmer-doesnt-cover-full-colour-temperature-range/115330/7 "2021-03-24T18:55:27Z")

</div>

Amazing, thank you very much!!!
