@InterHmai,
From what it sounds like, your devices are disconnecting from the cloud, but still maintaining their connection to the home network.

If Smart Actions(read cloud control) are not Working Properly there are a few steps that you can take to try and fix your issues.

If the Smart Action was working previously, it likely means that the device has gone offline and is not communicating with the Kasa Cloud Systems. Check to see if your smart devices are connected to your phone locally or via the cloud on your phone.

While you are having issues with the Smart Plug connecting to the cloud:

1. Please change your phone over to mobile data or LTE by disabling Wi-Fi on your phone.
2. Can you control and access the device?
   • If not, the device is not using the internet to control your device, this is a requirement for Smart Actions to work.
   • If the device can only be controlled on the home network, this means that the device isn't connected to the cloud and is operating locally on your network.
   • If the device cannot be controlled on the home network or via the Cloud, this means that the device is no longer connected and you should proceed with a soft reset, and then a hard reset if the device does not stay connected to the network.
3. Please Reboot any Smart Devices that are controlled by Smart Action. Even if your devices are connected to the cloud, I would still recommend rebooting any devices

Please ensure that the time settings are correct for your smart device in the Kasa Application, as this is a common source of failure for cloud connections. The time in the device settings needs to match the physical location for cloud control to work properly.

• Syncing Device Time Through the Kasa App

If none of the above helps to fix the disconnecting, I would recommend completing a factory reset of the device and configuring the device from scratch. 

As this is a HomeKit Compatible Device, I am also curious if the device has the same reconnects when set up using the Kasa App first.

Lastly, you mentioned that the setup was awkward because of the placement of the QR Code. This can be avoided by either configuring the device on a power strip or extender where the code is visible from behind; there is also a card in the box that has a QR Code for the HomeKit Setup which can be scanned instead of the code on the back of the plug.

I was a little confused at what you said that you had to wait to plug it back in; does this mean that after you scanned the code while the plug was disconnected, you had to reconnect the plug to proceed to the next screen, or else the setup would fail?
If so how do you think we should relate this to future users?

  @moiety   @RickCJ7,

The EP25 and KP125 offer the exact same feature set and experience for the end-user. Model differences such as this can vary for a few reasons such as sellers, selling in sets, or even simply different manufacturing facilities. In this case, I believe that there is no difference between the models, but I cannot confirm this for sure. I believe that in this case, however, they are different as a result of online retail vs retail; and packaged sets vs singular.

  @InterHmai,

Sorry to hear that they disconnected again. I think that you are on the right path with your troubleshooting when it comes to the IGMP Snooping Settings. I have been talking with our QA team and we have been trying to discover if this is the potential cause for homekit devices going offline. This issue can be seen across the board when it comes to both homekit devices and hubs. One thing that we noticed is that some manufacturers have included an IGMP Proxy Option. This can be found in our routers as a default option or will require a more detailed setup for other brands routers.
The Proxy seems to allow these devices to function albeit flawlessly as it passes the control of the devices from the Hub to the Router. This allows the router to be the device sending and organizing the network traffic, instead of following whatever instructions are sent to it by the HomeKit Hub.