TP-Link (KL420L5 LED strip) set to unsupported color mode brightness

[esand]

The problem

LED light strip was set using the Kasa mobile app to a custom effect light setting that I had just created. Everything worked fine, however Home Assistant apparently logged an error when it happened:

Logger: homeassistant.components.light
Source: components/light/__init__.py:1114
integration: Light (documentation, issues)
First occurred: January 1, 2025 at 12:11:30 AM (1 occurrences)
Last logged: January 1, 2025 at 12:11:30 AM

light.master_bed_lighting (<class 'homeassistant.components.tplink.light.TPLinkLightEffectEntity'>) set to unsupported color mode brightness, expected one of {<ColorMode.HS: 'hs'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+tplink%22

What version of Home Assistant Core has the issue?

core-2024.12.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

TP-Link

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink/

Diagnostics information

config_entry-tplink-aa7b0b0986169d556f9c5f97a3c19056.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

I have a tile card configured for this device and it's set to display brightness. I am uncertain if perhaps the tile card caused the error to log due to not knowing how to display the special effect brightness. The special effect has a flicker/strobe/pulse effect and is likely done via brightness control.

[home-assistant]

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)}}

[sdb9696]

Hi, could you please trigger the same issue and then upload the diagnostics information while the custom effect is still active?

[esand]

config_entry-tplink-aa7b0b0986169d556f9c5f97a3c19056.json

@sdb9696 Hopefully this has what you need - if not, let me know. Seems the steps to reproduce the issue don't work every time.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[sdb9696]

Bot keep issue open. I have a fix.

[sdb9696]

This should be fixed with library PR 1491. The current plan is for this to make the HA 2025.2 release.