Yeah, that didn't seem to do anything. I even changed my password in the phone app, logged out, refreshed credentials in Kasa integration, saw it got a new auth token and ran discovery. Every time I run discovery different devices change to cloud or will show the IP.
Is there a timeout or anything perhaps where if something times out it changes to cloud?
So before dropping back to punt, I decided to try manually putting the IP and Port in one of the devices and saving it. After I did that I was able to turn off use cloud for control. And the device works. I repeated this with all the devices that were showing cloud and they all work now.
I suspect though if I re-run discovery it'll change several back to cloud.
sorry if this has been answered before.. is there any reason to switch over to the built-in integration today? I've got lots of Kasa devices and it'll be a pain to delete them all and re-add. I figure I'll do it eventually but waiting until there's some reason to.
Everything's working today so I think that's my answer but I did notice I can't get the driver name to sync with the Kasa name (below screenshot) so if that's something that's fixed in the built-in version it might be worth it.
Question: how do I do a manual sync? Is it the Refresh or Configure driver command? I don't change plug names often but for example I'll use a plug for our Christmas tree and then change the name in the Kasa app to "Christmas tree".. ideally I'd get the Hubitat devices updated so I can use it in a google home integration (ie: Google, turn on XMas tree)
You can change the name in the Kasa App itself and then change it in Hubitat to match. A big pain, but with sync name no longer working on all devices.....
Dave
PS - if all is working ok, there is no advantage to update to the built-in app. It is frozen in time since Kasa has abandoned the UDP API for new models (and in some cased new HW versions of the same model). They are transitioning to using the Tapo API for these devices.
List of devices (as of several months ago):
SMART_TAPO_REMODEL_KASA_HUB_KH100 (works with Kasa TRV)
I don't know if this is the appropriate place for this but I am seeing many of my devices showing a comms error "true". They are all working though. How do I correct this?
I see some comments about KS200M but no confirmation if it can report motion separate from switch. Does anyone know? I'm wondering if I can use the motion event from that switch to do some other things.
