@Wayne-TP 

 

I think there might be a misunderstanding.

The electricity in my area typically only flashes or toggles on/off once, and if it happens again, it's usually after several minutes (at least 5-10 minutes). The on/off toggle doesn't occur in quick succession like it would during a soft reset (which involves turning the device on and off within a few seconds).

 

My assumption is that this single on/off toggle, even with the minutes between them, is causing the LED to reset. Now this is only my assumption, I guess I have seen the LED reset without such a sequence of events also.

 

I’m not sure why this is happening, as I use multiple other LED lamps from brands like Wipro and Panasonic, and none of them have this annoying issue.

 

I hope I was able to explain it properly.

I will try this and get back to you.

  @Wayne-TP 

 

I've just tested this product again, and unfortunately, the issue persists. I could not reproduce the issue by following a fixed process. The reset/disconnection happens at random times, even though there is no fluctuation in electricity.

I own several other TP-Link products and have never encountered anything like this. This issue is quite frustrating and disappointing, and I'm now considering this a loss and will move on to another product.

I use "TpLink Smart Switches" which is connected to the same wifi network as the bulb and has same electricity environment as the bulb. The switch never gets disconnected on it's own.

I've checked various online portals and found that I'm not alone. Many others are facing the exact same problem with this device. I'm attaching screenshots and links for your reference.

 

The following is taken from Amazon India page. Just search for "disconnect" under "Looking for specific info section"

 

 

The following is taken from flipkart India page. 2nd review page.

 

Wayne-TP wrote

As I explained, the steps to reset the bulb are relatively complex. Normally, the bulb should not be reset when there is a sudden power outage, and your own tests have confirmed this.

I might have described the issue incorrectly. I assumed that the bulb was being "reset," but I can't be certain that's what's happening.

 

What I do know is that every other day, when I open the Tapo app, I see that the bulb is marked as "offline." This led me to assume it was being reset.

 

At this moment, the bulb is in an "offline" status, and I have to manually reset the bulb and reconnect it to the Wi-Fi network to get it working again. The screenshot of the reviews I posted earlier perfectly describes this situation: the bulb becomes "disconnected" from the app.

 

Below you can see the screenshot of my tapo app.

 

 

 

Power fluctuations don't happen all the time, but what does occur regularly is that the bulb goes "offline" every 2-3 days. The interval isn't consistent.

Moreover, the fact that many other users are experiencing the same issue suggests there's a problem with the Tapo bulb itself. It's unlikely that all those reviewers have unstable electricity.

Additionally, many people either don't bother to leave a review or report the issue, so the actual number of users facing this problem could be much higher than the number of reviews suggests.

Today I faced the same issue again. I'm connected to the local Wifi and The device is offline. On the Wifi List I can see a new network which's name is something like "Tapo_Bulb" I had to connect to that, re-add the bulb like I did on first time. This happens frequently but there is no fixed interval. It just happens randomly.

I also have the same problems. I have fitted 10 of these bulbs along a customers drive. Within external fittings.

When the power was removed and restored due to a power outage the bulbs all reset back to factory default settings. 

I can see the bulbs when I do a scan but they will not connect with the customers app as the IP address and gateway have defaulted.

I presume looking at the other comments and issues experienced I will have to reprogram each of the bulbs again. 

Your advice would be greatly appreciated and will this be addressed in future firmware upgrades