Problem with Tapo Light?

Devices
1

Hello, I have a problem with Tapo lamps (GU10, L630).
I need to pair them via the Tapo app and then integrate them into Homey—so far, so good.

But when I try to control them through Homey, there is some latency, and on top of that, they bug out (sometimes half of them turn on/off, sometimes only one, sometimes two, sometimes three, etc.).

However, when I use the Tapo app, there is zero latency and no lighting issues.
Does anyone have a solution?

Thanks!Hello, I have a problem with Tapo lamps (GU10, L630).
I need to pair them via the Tapo app and then integrate them into Homey—so far, so good.

But when I try to control them through Homey, there is some latency, and on top of that, they bug out (sometimes half of them turn on/off, sometimes only one, sometimes two, sometimes three, etc.).

However, when I use the Tapo app, there is zero latency and no lighting issues.
Does anyone have a solution?

Thanks!

1 Like
2

This is probably because you turn more than 2 or 3 devices (using the same protocol) at once.
Homey unfortunately sends the signal to all those devices at once, instead of sequential.
This causes signals getting interfered / lost.

Workaround: group those devices by using the < group > app, or an Advanced virtual device.
Those apps start the group members sequentially.

3

Helo @Peter_Kawa and @Yannick_Neyns

I have similar problem as you describe (specificly with GU10 L630)

anyway from my point of view there are two problems

  • big delay when turning on/off (I could live with that) - in contrast with TAPO app, where it works very swiftly
  • inconsistency (sometimes some of the ligts dont turn on, or also changing colors is often buggy) - this is a big problem for me

I tried the < group > app to solve the inconsistency but it behaves the same (very often at least one of the lighst does not turn ON or when turning OFF one or two stay on)

a janky workaround that sort of works n is following: in a FLOW not turning them all at once, but in a sequence (in my testing I even added 1 second delay inbetween each light turning on), to be safe, I even spammed the sequence multiple times (so that if any of the lights did not turn on in the “first round” it will in the following round)

From user perspective the problem is that in the HOMEY system the light turns OFF but in reality it does not - this sometimes happens even if i try to turn OFF the light via the Homey APP (through the devices overview) - the icon that represents the light shws “TURNED OFF” but in reality it emits light

Similar problem is also with changing colors, sometimes changing colors (either way by input from user in the devices overview in HOMEY app or through a FLOW) - from my experience there are more cases of the color not changing than working properly (also in the HOMEY app it always shows on the icon that the color has been changed but in reality it has not). Curiously to me it seems that when not in RGB mode but in TEMPERATURE mode (different warmths of white) it seems to work with higher succes rate

For the lighst not reacting to color change I did not find work around (unlike with the Turning ON, the color often does not change even with SPAMING the light with order to change color)

Did any of you guys find a solution yet or moved on in any notable way?

Thanks, kind regards
Radim

4

Yes i let it go tapo light … wifi light doesn’t support several command in the same times … i send back all my tapo and bought Wiz working with matter , it works perfectly now ..

5

Hi All,

The app connects to the Tapo API. Unfortunately, this is limited to a number of requests that we can do. Normally this is per user, so you will not experience any problems with this. We are still in contact with Tapo to solve this.