@Solla-topee 

Where is TP-Link in coming up with a fix for this?

We all seem to be getting blown off by TP-Link, and the solution to create an isolated network is not a solution.

Without the promise of a solution, I am days away from removing my 75+ TP-Link devices and sending them back to you for a refund.

I have now spent the last two nights trying to sleep through the strobe show as whatever is causing this runs through the house flashing the lights on and off every few minutes.

My guest's at Easter thought it was quite comical. Needless to say TP-Link won't be getting their business!

The Beta firmware resolved the issue for me so far. It's been three days and no random on/off. Thanks!

@Solla-topee 

 

I've tried the KP103, HS200, HS220 beta firmware so far and it seems to have fixed the issue. Will try the KP400 soon. When can we expect the solution to be rolled into an official firmware release?

I have 6 KL130 smart bulbs one of them sometimes turns off by itself and stays off, not sure why that is, but it's very infrequent. The lights also sometimes flash off and on (only one at a time, as far as I know) but that may just be unreliable power, not sure. Anyway, I can live with those as it's very infrequent, that's not why I'm making this post but I thought it worth mentioning anyway in case there is a solution.

 

I have been using a HS110 smart plug for a while, without issues.

 

I just added 2 more HS110 smart plugs today and one of them is having this issue.

The one in question is connected to my desktop PC to monitor power usage and every time it power cycles the rapid power cycle causes my PC to lock up during boot with the fans on full blast, which is extremely annoying.

The other one seems to be working correctly, though it hasn't been powered on for extended periods of time, so it's a bit early to tell.

 

All of the smart plugs are on hardware 4.0 and firmware 1.0.5 (the latest)

I don't have a mesh network and my router is an Asus RT-AC68U. Away mode is off.

Power cycles happen roughly every 45 min.

 

I've gone through all the troubleshooting steps, factory reset did not help, I now have the problematic plug on a separate guest network. I didn't touch the working plugs and smart bulbs. Will update on whether the issue persists.

 

Edit: Problem went away with the plug on an isolated network. Moreover, I think I've narrowed down the issue to a custom program I wrote for polling the power usage and toggling power using this library: https://github.com/iqmeta/tplink-smartplug

Now, there is nothing special about the library, or my code. It simply polls the sysinfo and meter states every 500ms and updates the info displayed in the program. Perhaps it's simply polling too often or there is a memory leak issue in the TP-Link firmware.

I have also seen multiple reports the same issue when using the OctoPrint-TPLinkSmartPlug plugin to control their 3D printers. I have been using that without issues for a year now, so I don't know why some others are having issues with that specifically, but it seems to me like the ones having issues are the ones making use of the undocumented interface on port 9999 which may not be entirely stable or bug free as it was probably not meant for people to use. As when I googled the issue several results came up which specifically mentioned the OctoPrint plugin.

I also saw one person mention they looked at the LED when it happened and it started blinking like it was searching for the wifi network, which suggests it actually crashed and rebooted. Makes me think it crashed due to a memory leak or a bug seems pretty likely.

 

Edit2: After some more testing I've come to the conclusion that it has to do with the number of requests done on the undocumented port 9999 interface. Doubling the polling delay only doubles the time it takes before the plug crashes and power cycles. It seems to happen after about 5000 requests (120 requests a minute * ~43 minutes = 5160 requests, when the delay was doubled it took almost exactly double the amount of time, but same amount of requests), anyone that runs any 3rd party software making use of this interface will probably experience crashes/power cycles around every 5000 requests. I have a hunch that every request is being logged in RAM or to a ramdisk but never cleared, and once it runs out of space on the ramdisk or in memory, the entire thing crashes. It's also possible there is a memory leak and it is just not freeing all the resources used for each request properly.

@Solla-topee 

My KL130 are hardware version 1.0, not 2.0 and already running the latest firmware (1.8.11)