Skip to content
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

Kasa LED Multicolor bulb: Can't update Color or Color Temperature whille light it off #34

Open
nbackous opened this issue Nov 15, 2021 · 1 comment

Comments

@nbackous
Copy link

nbackous commented Nov 15, 2021

I have set up several rules for my TP-Link / Kasa multicolor bulbs (KL130P2).

ex:

Rule 1: turn Bulb A on at sunset

Rule 2: turn Bulb A off at 12:00

Rule 3: turn Bulb A on if Button 1 is pressed

Rule 4: turn Bulb A off if button 1 is long-presssed

Rule 5: At 05:00 Set Bulb A to 2500k

Rule 6: at 23:00 Set Bulb A to Red color

The color change at 23:00 while the light is already on works fine, since the bulb was already on at the time. But it appears the 05:00 color change command isn't broadcast at 05:00 because the light is off.

This is easily reproduced by using the Webthings interface to attempt changing colors or changing between a Color and a Temperature while the light is turned off. The UI will update with the new Color/Temperature momentarily, but will revert to the original color almost immediately. If the light is on at the time of the Color/Temperature change, it works as expected.

I don't have this problem with non TP-Link/Kasa multi color/temperature bulbs.

For clarity, the bulb is receiving power, it's only "off" because its On/Off property is set to Off by Webthings. It is my assumption that the bulb should be able to receive color/temperature/brightness value changes while in this state and would reflect those values the next time it receives a command to turn on.

@benfrancis
Copy link
Member

Thanks for the bug report @nbackous. To set expectations, if this is a bug in the TP-Link adapter add-on then I'm afraid this add-on is currently lacking a module owner so we're looking for contributors to maintain it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants