Can't re-configure accidentally deleted device

Configuration
1

Hi,

I have a TP-Link HS110 connected to my HA platform using the TP-Link Kasa integration.
I accidentally deleted this device from the integration and now whenever I try to re-add it, I got a pop-up saying:

image

Any ideas on how to overcome this ?
Thanks in advance.

2

I don’t use that integration but have you restarted HA as that might help?

If so then search for the entity in Developer Tools - States and see if you can delete it there.

Other than that I don’t know but hope this helps.

3

Sadly enough I tried both and they didn’t work, thanks though.

4

If I recall correct then I had to reset the device to factory settings and delete it from the Kasa app on the phone, then reconnect it.

5

Already done :frowning: didn’t do the trick…

6

Would really love some input from smarter people than me on this same issue.

7

Solved. I’ll do my best to document this here, anyone finding this feel free to reach out!
I deleted a KASA 100 series bulb from my HA server whilst troubleshooting something. It then failed to show up, even when I factory reset it and added it to the TP Link Kasa app with a new name.

Upon targeting the IP of the bulb in question (With the Kasa integration setup), I recieved the “Device already configured” message. I assumed (correctly) this meant orphaned registry entries that were no longer accessible from the UI.

So, I installed the community SSH Add-On, stopped my HA server core while leaving the HA OS itself running, and accessed the filesystem of my server with WinSCP. I then searched for the MAC address of the orphaned bulb in the core.config_entries, core.device_registry, and core.enities_registry JSON files. I deleted the entry blocks for these carefully, making sure the syntax before and after was left intact.

You mileage may vary, but this worked for me and I was able to add and use the device again!

1 Like
8

Worked great! Well, took me two tries. Thanks really appreciate it!

And to save somebody a google search:

  1. The core can be shutdown with ha core stop and ha core start to boot up
    • WARNING: don’t run in browser!! You must be able to connect to the server directly (ssh remotely or from the VM host) as the browser will be shut off!!
  2. The files can be found with cd /config/.storage/… then use vim :smiling_face_with_three_hearts: or nano
    :face_vomiting: to edit.

Side note: If using static IPs, just clear any associated reservations. In my
case my nightstand was flickering, so: basement->nightstand, new->basement,
keeping IPs consistent. Kasa must depend on a successful lease from the DHCP
server to finish the registration, as pre-changing the reservation’s MAC didn’t
work