-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
0.73.0 - light.tplink - division by zero #15339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hmm, LB100 does not support temperature changing, so the backend library reports 0 as min & max kelvin. The fix would be to check for that and return whatever is the default return for those methods. |
Probably return |
This was the fix for me. Edit From:
To:
|
Same problem here - LB110 doesn't have colour control, so now they are broken in the GUI. Still seem to work in automations, but it would be good to see this fixed. Is there an ETA? I am using hassio, so hard to fix the source. |
I'm wondering if the |
Its interesting to see this issue reappear. It used to occur way back in the early days of the tplink platform. Strange to see it resurface now. Was working fine for me until 0.73.1. For now I'll go back to altering color.py as I did in the old (lol maybe a year ago) days. |
I had the same issue and the implemented something similar as comment 6 #15339 (comment) |
If you are going for a local change, please test #15484 since that is what we expect will fix this issue. |
seems resolved in 0.74.0 |
It seems that @rytilahti managed to fix it with #15571 👍 |
Home Assistant release with the issue:
0.73.0
Last working Home Assistant release (if known):
0.72.1
Operating environment (Hass.io/Docker/Windows/etc.):
Docker / RPI3B
Component/platform:
light.tplink
Description of problem:
LB100 causes division by zero error with kelvin temperature conversion. seems #15020 could be the culprit
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
The text was updated successfully, but these errors were encountered: