While this problem has been brought up in the past I didn't find a resolution in the responses. I've used Kasa EP25s for quite a while and have been very happy with them. When I recently tried to add another, the Kasa integration couldn't find it. It is not a networking issue. I can communicate with the EP25 just fine via my phone app and pings. It's a discovery issue in the Kasa integration. Is there a workaround? Is there a fix? Do I dare uninstall the app and reinstall it? (I'd rather not lose access to the devices that currently do work.) Any suggestions?
BTW, I'm using a C8 with the current firmware update.
Try using the Custom TAPO integration. Some of the newer Kasa devices uses the TAPO protocol and security. The Custom Tapo integration is Local only but uses your credentials for local security.
Link: [RELEASE] TP-LINK TAPO Plug, Switch, Bulb, Hub and Robovac Integration
Note: The EP25 is one of the devices that Kasa is "Remodeling" to the TAPO protocol. Below is a list of these products (latest hardware versions are what are changing). Causes mass confusion.
SMART_TAPO_REMODEL_KASA_HUB_KH100 (works with Kasa TRV)
SMART_TAPO_REMODEL_KASA_PLUG_EP25
SMART_TAPO_REMODEL_KASA_PLUG_KP125M (Matter)
SMART_TAPO_REMODEL_KASA_POWER_STRIP_EP40M
SMART_TAPO_REMODEL_KASA_SWITCH_HS200
SMART_TAPO_REMODEL_KASA_SWITCH_HS220 (Dimmer)
SMART_TAPO_REMODEL_KASA_SWITCH_KS205 (Matter)
SMART_TAPO_REMODEL_KASA_SWITCH_KS225 (Dimmer, Matter)
SMART_TAPO_REMODEL_KASA_SWITCH_KS240 (Dual Fan Control/Dimmer)
Works great! Thank you very much.
1 Like
The KS240 child light does seemshow as a dimmer or switch when trying to add to a group. Am I missing something?
Great work on this!
The KS240 is a parent and two children (three drivers required).
- TpLink Parent - parent device for the two children
- TpLink Child Dimmer - the dimming switch function of the device.
- TpLink Child Fan - The Fan control function of the device.
All three drivers must be installed and then there are separate child devices for the switch and fan of the device.
Note on child fan - this is Beta version and comments are allowed.
I have them all installed. Just the switch doesn’t show up in the list of dimmers to add to a group.
On the Device Info Tap, bottom right, under "Device Data", what is the category? What is the type?
Note: Does it appear somewhere else (switch? Bulb?).
(Also try refreshing the lists in the Groups and Scenes app you create. That sometime adds new devices)
It is listed as “Child Dimmer”.
I see it as a dimmer in rule builder, just not in the Groups app.
But you can find it in the Groups app as another machine?
Examination: I have a child night-light on the P306 multi-plug. It uses the same driver as your KS240 dimming switch. It appears today as a dimmer in the groups type lists. Yesterday it was a bulb.
Conclusion: It is a nuance in the groups device-type (switch, dimmer, bulb) generation to assure a device does not appear on more than one type list. Probably first found type, first used type from the device's data used in the function.
Given the information you have given, unless you can't find the device on any list in your group, then I will have to close. I see nothing I can fix.
I just redid a couple of kasa due to wifi change the minis ... the app is finding them fine. Have u checked that the network settings in the app have the correct network and subnet ?
After a few reboots and adding and removing, it finally showed up. I removed the whole switch, rebooted and re-added and it was there.
Thank you!
1 Like
Issues again. Network configuration is fine. Reauthenticated with the TP-Link/Tapo cloud. Can't find a Tapo P115 that I'm trying to install. Debug log says localAuthHash != serverHash. I haven't figured out what this is trying to tell me yet. Any clues?
Goes back to the credentials in the Hubitat Tapo Integration app. they (both username and password) must match EXACTLY that in the Tapo phone (android/iphone) app. Watch out for spaces before or after password. This hash is checked as a part of the handshake between the device and the Tapo Integration app.
Verification: Checked in my dev. System by adding "aa" to username and
