Been using the Kasa integration to talk to a a bunch of devices. The 3 outlet strip model KP303 stopped working. It works through the Kasa app on my iPhone. And also on the Tapo app on my iPhone. (SO CONFUSING - GET YOUR ACT TOGETHER TP-LINK!) but won't respond. So, I deleted to try to re-add and it doesn't find it. It's got a reserved IP address as before but just won't work and refused to be detected now. Any thoughts?
Tech info:
Model: KP303
Hardware Version 2.0
Firmware Version 1.1.2
My assumption is you are on the current official Hub version or on one of the current "beta" versions.
I have the same KP303 HW and FW Version. Was successful on both of my hubs in finding all three outlets on my KP303. I can only suggest the following:
Have you changed you Router or Router configuration lately? If so, something there may have isolated Hubitat from the wireless SSID the KP303 is installed in.
Check if the plug is still installed in the integration app. Easiest way is to select "Remove Devices" and then seeing if any of the KP103 plugs are in the list.
Check the plug's wifi strength (in the tapo or kasa app, device info page). Click the wifi icon to get the strength. Below -58 may cause issues.
On doing the find, open the Phone Kasa/Tapo app and test the device just prior to doing the find. If first find fails, do the retry immediately.
I have the KP303 on watch daily for switch-over to the tapo protocol. But not yet - so....
TP-Link is trying to make things less confusing. They are going away from the Kasa App in favor of the Tapo app so their smart home products have the same control interface. They have already gone to the Tapo cloud for Kasa devices (deleting the cloud). On the Tapo App me page, they have a link Kasa with Tapo.
Of course, this can cause some problems. Since they have never published their API and do not support third-party developers, they do as they please. Where they can, they are updating Kasa device firmware to be the TAPO firmware. Reduces future maintenance. I am following this to add Kasa devices to the community Tapo integration as the transitions occur.
Please verify your Hubitat Version. The App was updated about one month ago to eliminate cloud access (Kasa cloud abandoned by TP-Link).
Did you try the install as recommended in my message?
Need more detail since I can not duplicate on the same model, hw ver, and sw ver device either on an existing installation nor on a new installation of the Kasa Integration.
Turn on debug logging on the Kasa Integration app and run find devices again. PM me the results along with an image of the Kasa Integration Start page.
Not sure. One possibility is that your hub is on the .4 segment and the device on the .5 segment and the hub is not able to communicate to the .5 segment (security or some other reason). At any case, the error appears to be a hub - device access within your LAN structure. I have seen this before and there is nothing my code can fix.
I practice the KISS property for my LAN to avoid this type of issue (Kiss = Keep It Simple...).
Yeah, the other working Kasa devices are split across the .4 and .5 segments so I know that's not the problem. I have a lot of devices on my Eero network and ran out of the original Class C. Yeah, I know. Anyway, strange that:
it worked for 3 years fine.
Still works on the Tapo and Kasa apps
But won't work anymore on Hubitat on either the Kasa or Tapo integrations.
Many thanks for all your efforts on this integration and trying to help me out. I'll probably give up on this 303 this year and get a Matter compatible one to replace it this Christmas. It's used to control a number of indoor Christmas decorations.
Well, I think I know what's going on. While the strip worked find in the Kasa and Tapo app, I thought I'd try deleting it and resetting the KP303 to rejoin it. Well, it won't rejoin. And it just blinks RED instead of the green/amber that it's supposed to blink. So, seems that the KP303 has lost its mind. Pretty sure that this all started with me taking a firmware update on this thing. I'll need this in about a 6 weeks so I'll have to look for another plug strip that I can connect to HE. Thanks again @djgutheinz. Thought I'd close the loop on this as a hardware failure.