home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.74k stars 30.46k forks source link

TP-Link Tapo L530E switching color is having an issue #128537

Open prgorasiya opened 1 week ago

prgorasiya commented 1 week ago

The problem

Hi there,

Forst of all, thank you very much to this awesome supportive community.

I have some TP-link Tapo L530E bulbs and they are used in some automations. I am using this blueprint for automation. I have 2 separate Automations for day and night time. At night I would like the bulbs to have red color and during the day normal warm color. The issue I am observing recently is whenever switch between colors happen for the first time during a day, bulb first turns on with full brightness with previous color than it should at a given time of the day/night and then immediately adjusts to correct color and brightness level.

Example: Night light automation runs on from 11PM to 8AM for red color with 50% brightness. Day time automation for rest of the time for warm color with 100% brightness. During the day light turns on a few times with warm color and 100% brightness. Between 11PM and 8AM if the light is turning on for the first time, it'll turn on with warm color and full brightness and then immediately switches to red color with 50% brightness. And vice versa, if light is turning on post 8AM for the first time then it'll be red color with 50% brightness and then warm with 100% brightness.

I have changed anything in my automation ever since I set it up and I was not experiencing the issue in the past. I am not sure if it could be due to bulbs themselves, perhaps some new firmware introduced this bug 🤔🤷

Any idea if there's anything wrong?

What version of Home Assistant Core has the issue?

core-2024.10.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

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 6 days 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!

Code owner commands Code owners of `tplink` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tplink` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


tplink documentation tplink source (message by IssueLinks)

krysiswbk commented 5 days ago

your issue is likely not related to home assistant or the integration.

In the tapo app, on the bulbs settings page you likely have it set to "last on state". If so, this would be expected behavior.