Migrate the LIFX integration to use kelvin for color temp

[Djelibeybi]

Proposed change

Switch the LIFX integration to use kelvin for color temperature values.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: Use Kelvin as the preferred color temperature unit #79591
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[homeassistant]

Hey there @bdraco, mind taking a look at this pull request as it has been labeled with an integration (lifx) you are listed as a code owner for? Thanks!

[bdraco]

Nice. That was quick.

I'll give this a spin this weekend

[Djelibeybi]

I've been wanting this for longer than I've been a contributor to Home Assistant. 😂

[bdraco]

I tried it on a beam, and I'm not sure if its a problem with the min/max but after I turn it back on/off it jumps back down

[Djelibeybi]

This may be further weirdness with how the light.turn_on stuff was changed. It seems to bounce the conversion to mireds and back for kelvin, even if kelvin is explicitly stated. I thought it was specific to the LIFX integration because it was the only one that directly called preprocess_turn_on_alternatives but maybe there is a larger problem.

Either way, I have plenty of Beams lying around, so I'll test it now and work it out.

[Djelibeybi]

I can't reproduce this on my Beams: they remain the same temperature through on/off cycles.

[Djelibeybi]

I forgot to move the check for color temp changes back to after hue/saturation changes while I was working out an issue with getting the wrong kelvin value. Not sure if it's related to your issue though. And I'm now trying to work out how to extend the UI so that it covers the entire kelvin range available to LIFX devices (1500-9000) instead of being stuck with the more limited 2000-6535 provided now.

[bdraco]

I dug into this a bit more. In the app the color temp is limited to 2500-9000 but in HA its showing as 1500-9000 so thats why its jumping back.

[Djelibeybi]

I dug into this a bit more. In the app the color temp is limited to 2500-9000 but in HA its showing as 1500-9000 so thats why its jumping back.

Interesting. There are two Beams on the product list, one that goes to 1500K, the other only to 2500K. I'll double-check to make sure that the aiolifx product list is up-to-date and that we're correctly identifying each Beam.

[bdraco]

The above issue is unrelated to this PR.

So this LGTM 👍