SOLVED: I HAD TO MANUALLY RE-ADD EACH STATIC IP IN THE TP-LINK SMART HOME APP. SOMEHOW, THIS FIXED THE CONNECTION AND ALLOWED HA TO SUCCESSFULLY SEE THE DEVICE!
Over the weekend, I upgraded my Unifi network (swapped from a USG Pro-4 to a Dream Machine Pro). The new Unifi network was directly imported from the old network configuration (so, theoretically, all of the networks and configuration were exactly the same - just a new piece of hardware acting as the “router”). For reference, I keep all of my IoT devices on a separate VLAN. I have ~50 Kasa switches configured for use in Home Assistant - they are no longer working in Home Assistant.
My Kasa switches have static IPs (assigned by me in the Unifi controller). 192.168.20.xxx
My configurations.yaml file lists all of the
In the Kasa integration, all of the Kasa devices state “Failed setup, will retry” with the following error message:
You can see from the error message that HA is looking for a very different IP (192.168.1.xx). My normal gateway is 192.168.1.xxx. All of the Kasa switches are supposed to be managed on the 192.168.20.xxx VLAN.
I also find error messages like this in the log:
I don’t understand why HA is looking for 192.168.1.xxx IPs for these devices when they are hard-coded to 192.168.20.xxx and have worked previously. HA should not be looking for 192.168.1.xxx static IPs for these Kasa devices…
I tried restarting / resetting / re-adding a Kasa switch, but nothing shows up.
Sorry for the technical details - hoping somebody has run into this issue before or knows how I can fix it. I’m certain that this is related to the network controller change - but hoping that I can fix this in HA since it worked before.
Notes:
My Kasa IOS app can control the switches just fine - so I know that the network sees the switches and they can be controlled. They just aren’t accessible in Home Assistant.
