TP Kasa HS200 not discoverable

Third party integrations
1

Recently I had one of the TP-Link hs200 switches in my home disappear from HA.

I have about a dozen. All except one are fine.

Things I have tried.

  • factory reset switch and re-add with app
  • static assigned IP address
  • remove all tp-link devices and restart HA. All but the one was auto discovered
  • add the switch directly in configeration.yaml
  • removed the switch from the app and re-add.

I would be inclined to suggest bad wifi signal maybe, but it is in a two gang box with another HS200 that is perfectly stable.

I am at a loss as to what has happened or how to get it back. Really a bit miffed since I would have to replace two switches to get this functionality back – I want them to look the same.

Any ideas what I could do next? Like is there some sort of malformed cached entry somewhere that I could clean out?

2

Ugh. Stopped HA, carefully pruned the entries from the core.* files in .storage and restarted.

It is now discovered and available.

I feel like I probably voided my warranty here.

\me ducks the flamethrower

3

I have this same problem but have no idea what this solution entails. I have HA on a Raspberry Pi 4. Does this fix apply?

4

yeah. there is a ‘hidden’ directory in your file system where HA stores its configs called .storage. In there I edited the core.* files and pruned out references to the device. I did this with HA stopped. Then restarted it.

It shouldn’t matter that you are on a Pi