Open masonlancaster opened 3 years ago
I have the exact same issue :-(
@rvanbaalen after restarting my gateway, all of my Kasa devices started working again.
Which gateway? You restarted homebridge?
I restarted homebridge, the raspberry pi it's running on and removed and reinstalled this plugin but nothing is working so far. It was all working just fine a couple of hours ago.
My router/modem has an option to restart the gateway. I imagine a router restart would accomplish the same thing. My whole issue was triggered by a power outage and then when everything came back on my kasa devices were undiscoverable by my homebridge. However, before restarting the gateway, i was able to get them to work when specifying the ip address in homebridge settings. If you are able to make your kasa devices static ip's from your router than that is an option that would work long term. But the gateway restart was enough for me.
The same happened to me today after migrating the docker container when upgrading to Synology DSM 7. Tried unpairing the TPLink child bridge, removing TPLink cached accessories, reinstalling the plug-in, none of them worked - cannot discover the accessories.
Finally got here and tried what @Maseman12 mentioned, everything back to normal after a router/AP power cycle. Thanks!
Not sure if this is related to the plug-in, all six of my other plug-ins worked without restarting the network devices.
Expected Behavior
Current Behavior
Steps to Reproduce (for bugs)
Versions
node --version
homebridge --version
Configuration
Homebridge Log / Command Output