TP-Link kasa Trouble

Configuration
1

Ok, so I feel like I’m doing something supremely stupid, hopefully someone can point me in the right direction.

I have a lot of TP-Link Kasa devices (~70). I had been getting the ‘unavailable’ bug on my switches, which I’d mostly resolved by manually configuring the switches I needed in Home Assistant in my configuration.yaml and turning off automatic discovery. I had read that there might be some real progress on the unavailable bug, so I decided to comment out my manual configuration entry, and use the integration through the UI. Strangely only the already configured switches showed up. I didn’t worry too much about it, as those were the ones I needed in Home Assistant anyways.

Yesterday I had an outage on my internet and while trying to work around my router decided it would be a good idea to blank my entire table if static IP assignments. I’d been annoyed with my router in the past so decided to take the opportunity to set up a DHCP server within home assistant so at least I could back up my configuration.

After a few hiccups the new DHCP server seems to be working as it should, and my kasa devices (or at least most of them there are apparently a couple I missed) now have nice sequential static IP addresses (192.168.1.150-192.168.1.206).

Unfortunately none are available in home assistant any more… I’ve tried going back to a manual config, but the integration keeps popping up in home assistant, I’ve tried disabling the integration, but nothing I do seems to make a difference.

Config file excerpt

tplink:
  discovery: false
  light:
    - host: 192.168.1.150
    - host: 192.168.1.151
    - host: 192.168.1.152
    - host: 192.168.1.153
    - host: 192.168.1.155
    - host: 192.168.1.156
    - host: 192.168.1.157
    - host: 192.168.1.158
    - host: 192.168.1.159
    - host: 192.168.1.160
    - host: 192.168.1.162
    - host: 192.168.1.163
    - host: 192.168.1.164
    - host: 192.168.1.165
    - host: 192.168.1.166
    - host: 192.168.1.167
    - host: 192.168.1.168
    - host: 192.168.1.169
    - host: 192.168.1.170
    - host: 192.168.1.171
    - host: 192.168.1.172
    - host: 192.168.1.173
    - host: 192.168.1.174
    - host: 192.168.1.175
    - host: 192.168.1.176
    - host: 192.168.1.177
    - host: 192.168.1.178
    - host: 192.168.1.179
    - host: 192.168.1.181
    - host: 192.168.1.182
    - host: 192.168.1.183
    - host: 192.168.1.185
    - host: 192.168.1.186
    - host: 192.168.1.187
    - host: 192.168.1.188
    - host: 192.168.1.189
    - host: 192.168.1.190
    - host: 192.168.1.191
    - host: 192.168.1.192
    - host: 192.168.1.193
    - host: 192.168.1.194
    - host: 192.168.1.196
    - host: 192.168.1.197
    - host: 192.168.1.198
    - host: 192.168.1.200
    - host: 192.168.1.201
    - host: 192.168.1.202
    - host: 192.168.1.203
    - host: 192.168.1.205
    - host: 192.168.1.206
  strip:
    - host: 192.168.1.154 #Ceiling Plug
  dimmer:
    - host: 192.168.1.199 #Siona's Dimmer
  switch:
    - host: 192.168.1.161
    - host: 192.168.1.180
    - host: 192.168.1.195
    - host: 192.168.1.184
    - host: 192.168.1.204
2

I would try turning discovery on and temporarily comment out all of your specified ips in the yaml… or better yet try totally removing your tplink config from yaml and add it via the UI and see if it finds any. I thought yaml config for tplink was deprecated but I couldn’t find it in the release notes.
(Edit: the deprecation didn’t happen yet… it happens next week)

Not that it’s much help at the moment but the component has had a lot of work done coming in the next release. https://github.com/home-assistant/core/tree/dev/homeassistant/components/tplink

3

I just tried the beta and it was able to discover my devices on my other subnet for the first time. This means I don’t need to configure the device IP addresses in YAML any more. Yay!

4

Anything in the logs?

5

Managed to fix by removing the manual config and deleting and reinstalling the integration…strangely this was where I started. I suspect the problem was ultimately the integration was throwing a hissy fit when the address of every single switch on the network changed…

6

This solved it, which is weird, because its exactly where I started… I suspect the integration was throwing a hissy fit because the address of pretty much every device on the network had changed…