TP-Link Tapo L930 does not turn on depending on service call payload.

[WillT93]

The problem

When calling light.turn_on with the L930 LED strips, the lights will not physically turn on in certain circumstances as described below. This has the secondary impact of breaking scenes for these devices.

When performing alternating basic calls between light.turn_off and light.turn_on service calls, the light turns on and off as expected provided there is no additional state data in the turn_on call.

As soon as state data such as color or brightness values are included, the light will not physically return to its on state when those values are the same as the previous on call, instead they will stay in the off state. Home Assistant will incorrectly report the state of the light as being on when it is not. If different values are provided for each on call, the light will turn on with each call as expected.

Some examples below, as I know this is a bit nuanced:

Example 1 - Basic on/off with no state payload. Works fine.

light is off

• light.turn_on called. - Light turns on.
• light.turn_off called. - Light turns off.
• light.turn_on called. - Light turns on.
• etc.

Example 2 - On/off with differing on payloads. Works fine.

light is off

• light.turn_on with state data payload requesting brightness of 5% called. Light turns on to 5%.
• light.turn_off called. Light turns off.
• light.turn_on with state data payload requesting brightness of 90% called. Light turns on to 90%.
• etc.

Example 3 - On/off with same on payloads. BROKEN CASE

light is off

• light.turn_on with state data payload requesting brightness of 50% called. Light turns on to 50%.
• light.turn_off called. Light turns off.
• light.turn_on with identical state data payload requesting brightness of 50% called. LIGHT FAILS TO TURN ON. Home Assistant reports the light as being on, when it reality it is not.
• light.turn_off called. Light remains off.
• Subsequent calls of light.turn_on will only physically activate the light if the payload includes some other information that "brightness to 50%".

This presents an issue as it causes these lights to fail when used in a Scene. From what I can tell, scenes operate by sending their state payloads with the light.turn_on call. When alternating between scenes where the light is on and the light is off, the light will fail to turn on in any of the "on" scenes.

What version of Home Assistant Core has the issue?

core-2024.6.3

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_tapo/

Diagnostics information

home-assistant_tplink_2024-08-18T04-15-37.174Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

tplink_tapo documentation tplink_tapo source

[H220r]

getting the same problem.