Same here it found it when I narrowed the range down. However when I select the device (ticked) and click next, then done, I don't see the device created on hubitat device page.. I assume I don't have to manually add the device.. I haven't waited for long to see if it's delayed in the creation as a child device..
Version 1.1 is released to correct errors to date. See top post for link to installation.
Issue for Tapo Hub device. After updating, run command "play Alarm Configuration". Otherwise it goes into a loop (some data issue). If you encounter the loop, do the same. I will investigate a fix later this week.
Comms error causing app to not terminate discovery process
App change to automatically terminate discovery process
App change to filter-out non-tapo devices (precluding comms error to begin with.
I repaired my version and that upgraded it. Didn't find the device when searching..
Removed this integration and reinstalled. Now the device was detected and added as a device. All working properly, and quickly seeing it's local.
So my question.. Is it worth investing in the hub just to use the contact sensors and motion sensors? Or really am I better of sticking with zigbee things for them rather than tapo seeing I don't own the hub yet.
This integration is being withdrawn for new installations. Unfortunately, TP-Link has chosen to change the encryption /handshake technique on at least some of the devices and I can not guarantee any devices will work into the future.
I am working on the KLAP encryption and will come back when the integration can use either encryption type.
No. Tapo branded devices will be separate in a community integration (it would be simple to add into a single integration; however, the built-in app is controlled by the Hubitat Staff. Kasa matter devices (that use the Tapo API) will be part of the built-in app.
Tapo community integration delivery: Working on some device unreachable issues that have popped up. Will take several more days to finish troubleshooting an testing (happen periodically with a 408 status (device unreachable). Again, not sure why yet.