@Misha0926,

Since its two separate models, it is most likely a network setting. But you may still try factory resetting the device, deleting it from your list of Kasa devices, and then setting up the device again. When the device is factory reset and added to your account it will automatically check for, and update its firmware.

If it seems that the device can't communicate with the TP-Link servers, you may try to change the DNS server that you are using on your Home Network. When our Wi-Fi routers are unable to see firmware updates, this is the recommended solution, as it completely changes the way the traffic is routed to and from your home.

What type of router are you using, and who is your ISP?

  @Misha0926,

I have a feeling that there may be a firewall setting on your router that may be interfering with the update process. I am relatively unfamiliar with the interface for Google Mesh networks, but there should be a way to temporarily remove the firewall or prevent the router from blocking connections it THINKS is unsafe. It looks like there may be some settings related to a Nest Wi-Fi service that may be causing the failure. 

We do have a manual update process that our live support can help you complete if you seem not to be able to update at all; however, this is a relatively complex process and is not usually recommended due to the complexity.

On a side note, you may have something else going on with your network, as you should not have needed to change the DNS server for the router to work with your ISP, especially a Google Network, which should have provided you with the normally recommended 8.8.8.8 address. Usually, we recommend changing away from your ISPs DNS to a common service, as the ISP DNS servers can sometimes have routing issues and prevent your ISP from easily identifying your traffic.

You may want to check, while still painful, if your devices can receive the update if you perform a soft reset and only reconnect the device to your network. This way at least you would not need to rename and sort all your devices if it allows the update to proceed.

@Misha0926 

Make sure you try to add the device again after a soft reset. The app should detect that this is a preconfigured device and offer you the option to use the settings that were previously used.

Ill have a check with our team to see if anyone here may be able to come up with a reason that a default DNS server would not work, especially probably the most common DNS service available.

  @Misha0926,

I have had this happen to my devices before when they are set up. Check to see if you can update the firmware through the account page and double-check the firmware of the devices you are using; it is possible that they were either updated in the factory to a newer version, or have already received an update.

If your wireless network has an IoT or guest network, try setting the device up here and seeing if the device will accept the update. It is possible that there is feature on your system that is preventing the cloud connection. and the interfering features are not normally added to the guest network settings.

I am not positive on how the firmware is delivered to the device, so it may be worth seeing if the devices will update when you check from another device's app; if the firmware is delivered through your phone, it could be that the device is losing the connection to your phone due to a local network device access or private addressing setting.