Open flyinghier opened 1 month ago
Hey there @rytilahti, @bdraco, @sdb9696, mind taking a look at this issue as it has been labeled with an integration (tplink
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
tplink documentation tplink source (message by IssueLinks)
Alas, only kasa-branded devices support defining a transition for individual commands, so we should remove the transition from supported features for tapo bulbs like yours.
For tapo devices, you can either toggle smooth transitions on and off, or adjust the transition time for both on & off separately. You could use a script to adjust those values prior adjusting the light settings to simulate different transition periods.
I'm having the same issues with L530 bulbs 2 off. But I've working with Tapo as well over them dropping off the network with 2 issues I have 1 when powering off and back on they come on as 100% white 2 sometimes they lose there programs in the Tapo app on at sunset and off at set times. Tapo is causing issues in HA on timeouts. It did do an update 2 days ago but no different. Update - 2 bulbs above are hardware 1 - a 3rd L530 I have is hardware 2 and don't seem to have the issue.
The problem
When I call the light.turn_on service on by TP link Tapo L530 bulbs, they ignore any transition instructions. I am able to successfully transition another light using the same integration which is a Kasa KL135 bulb, however the L530's are not transitioning as expected.
What version of Home Assistant Core has the issue?
core-2024.7.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
TP-Link Smart Home
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tplink
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response