Avoid divide by zero errors in tplink light integration

[superm1]

Proposed change

Some bulbs such as kl125 don't have a definition submitted into
pyHS100. Trying to interact with them will cause a divide by
zero error:

  File "/usr/src/homeassistant/homeassistant/components/tplink/light.py", line 248, in attempt_update
    self._light_features = self._get_light_features()
  File "/usr/src/homeassistant/homeassistant/components/tplink/light.py", line 289, in _get_light_features
    min_mireds = kelvin_to_mired(min_range)
  File "/usr/src/homeassistant/homeassistant/util/color.py", line 515, in color_temperature_kelvin_to_mired
    return math.floor(1000000 / kelvin_temperature)
ZeroDivisionError: division by zero

As the pyHS100 project has been abandoned in favor of python-kasa but there isn't yet
a component in home assistant for using python-kasa add some fallback code into the component.

If the light specifies it supports color temperature but the range isn't available choose a "safe"
range that is the minimum of what is available in bulbs today.

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)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
tplink:
  discovery: false
  light:
    - host: !secret kasa_bulb_1

Additional information

• This PR fixes or closes issue: fixes tplink: Error on device update! (division by zero) #45675
• This PR is related to issue: Add KL125 definition GadgetReactor/pyHS100#201
• Link to documentation pull request: Add newly supported bulbs for tplink home-assistant.io#17125

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.
• 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.

[rytilahti]

A couple of comments. I'm wondering if it would make sense to copy over the definitions from python-kasa to this file, and handle the detection here?

That being said, having the fallback values is still better than crashing when an unknown range is reported by pyhs100.

[superm1]

A couple of comments. I'm wondering if it would make sense to copy over the definitions from python-kasa to this file, and handle the detection here?
That being said, having the fallback values is still better than crashing when an unknown range is reported by pyhs100.

I hadn't actually considered moving the definitions over. That's a great idea. I've brought them over and added the fallback check in case it's another unknown bulb.

[rytilahti]

There used to be this sort of mapping (iirc) which was moved to the backend lib which is the proper place for it. Considering the state of affairs, I think it makes sense rather to reintroduce this mapping inside homeassistant instead of doing a new pyhs100 maintenance release for new devices that were not available when pyhs100 got abandoned.

So 👍 after the changes I mentioned in the comments.

[superm1]

I'm not really sure what is wrong with the new test I added causing CI problems. They seem to work for me locally.. any ideas?

[superm1]

Let me know if you need me to squash them or you will, but it looks like CI and codecov is working now.

[rytilahti]

LGTM, what do you think @TheGardenMonkey?

[superm1]

Let me know if you need me to squash them or you will, but it looks like CI and codecov is working now.

FYI squashed it and force pushed, and also added a linked documentation update for this change.

[TheGardenMonkey]

This makes sense to me as well.

[superm1]

Anything else needed to merge this?

[frenck]

Thanks, @superm1 👍