Kasa and Tapo Switches, Plugs, and Bulbs - Hubitat Support

🛎️ Get Help Devices
25

Hi,
I bought a load of Tapo smart plugs with energy monitoring. I got P110 and P110M (matter version).

They're pretty good - small, cheap, Tapo app is nice. And I've had some success adding them into Hubitat. I say "some" because I've got most of them added, and some just refuse to be found. Tried removing them, adding them, turning them on and off while searching, all sorts.

Any clues as to what might be going wrong, or what I'm doing wrong, please?

(Adding the Matter ones goes okay, but they don't show the energy status. Not a deal breaker, but a pity.)

Thanks!

1 Like
26

Reference CUSTOM INTEGRATION INSTRUCTIONS: [RELEASE] TP-LINK TAPO Plug, Switch, Bulb, Hub and Robovac Integration

The information you provided is insufficient to provide any explicit guidance. However, I suggest the following at this point - RELATIVE TO THE NON-MATTER Devices only.
a. Uninstall the Custom Tapo integration and devices.
b. Reread the instructions above.
c. Open a log window.
d. Try reinstalling being careful to note what is happening. After starting the app, select debug logging at the bottom of the page
e. Private message the log messages for the APP only to me and provide the following information:

  • model, firmware version and IP Address of at least one failed device.
  • model, firmware version and IP Address of at least one successful device.
  • your Hub IP address

After garnering that data, I may be able to provide further guidance.

The Hubitat Matter driver does not yet support the energy status functions. The Custom integration does, AFTER resolving your other problems you could (but do not have to) uninstall the Hubitat Matter installation and then reinstall the plug using the Custom Integration.

1 Like
27

Does this integration support Tapo L930-5 - Amazon.com: Tapo TP-Link RGBWIC Smart LED Light Strip 16.4Ft, 1000 Lumens, 16M Dimmable Colors, 50 Color Zones, Works w/Apple HomeKit/Alexa/Google Home, Sync-to-Sound, IP44 PU Coating, Trimmable L930-5 : Tools & Home Improvement
TIA

28

Yes. But only as a single string.

1 Like
29

Dave is the Tapo T100 motion sensor supported. I looked but couldn't find that answer without bothering you.

30

Yes, the Tapo Integration support the T100 as a child to the H100 hub. (It does not yet support the (weird) H200/H500 hubs).

Dave

31

I assume from your reply that I would also need a hub to use it. So I'll go back to a Zooz sensor or something. Thanks for the reply though!

1 Like
32

yes

33

I have a Kasa strip light KL400L5 that I've been using a few years with the Kasa integration. Is this now supported with the Tapo integration (this one)? I'm trying to reduce the (about 1 second) lag time. It's currently on a secondary hub using Hub Mesh and I plan to move it to the primary hub and use whatever the current integration software is recommended. Also any tips in making it as fast as possible to respond would be much appreciated. Thanks!

34

TP-Link jumps from the legacy Kasa protocol to the new Tapo protocol in firmware updates. If as device it is working with the Kasa integration, it has not transitioned.

35

@djgutheinz I can't get a HS300 to work, keep seeing this in the logs:

image
image2642×259 117 KB

Only the energy attributes works, the Switch and LED attributes don't display and the commands don't work at all. I have other Kasa plugs/power strips that works fine and able to to control this HS300 from the Kasa and Tapo apps just fine. Is there any suggestions, I did see the noted about special handling for HS300 but can't find any instructions anywhere for the HS300 specifically.

The name also shows as TEMP:
image

I even removed the HS300 and repaired it multiple times on the Kasa app and tried just in the Tapo app as well.

36
  1. See the below. Names are way too long. (For the HS300 there is a work-around since the Hubitat UDP implementation does will only pass the 1024 characters to the requesting method). This note got dropped sometime several years ago. I will fix the documentation. I suggest shortening the name of the power strip as well as the six outlets using the Tapo/Kasa App.

image
image976×213 9.66 KB

  1. The Temp names are due to the same issue. When the message reads, the actual alias will be transferred from the device to the Hubitat instantiation.

  2. If a device has switched to the Tapo integration, it will appear on the list on the add devices page below the drop-down box.
    image

1 Like
37

Thanks that fixed it by shortening the names. Even though they are moved to Tapo, they seem to work fine on the Kasa Integration.

The Tapo Integration shows this is the logs:

image
image1283×86 24.9 KB

38

any hope on getting access back to our cloud only connect kasa legacy switches.. as mention i have some on a different unreacheable subnet than the hub and would like to be able to control them.

39

Trying to get a Kasa parent/child fan/child dimmer KS240.
I think I have read all the docs and messages, but as a newbie I cetainly may have missed something(s).
Hubitat Package Manager View:
The apps and drivers listed below are managed by the Hubitat Package Manager.

  • Hubitat Package Manager Documentation | Community Thread
    • Hubitat Package Manager v1.9.4 (app)
  • Tapo Plugs, Switches and Bulbs Documentation | Community Thread
    • Tapo Integration v2.4.3 (app)
    • TpLink Child Dimmer v2.4.3 (driver)
    • TpLink Child Fan v2.4.3 (driver)
    • TpLink Child Plug v2.4.3 (driver)
    • TpLink Parent v2.4.3 (driver)

Executing Scan and Add from Tapo Integration log:
app:102026-01-04 11:26:01.219 AM

debug

Tapo Integration-2.4.2a: [method:getInstalledDrivers, drivers:[TpLink Child Dimmer, TpLink Child Fan, TpLink Child Plug, TpLink Parent]]

app:102026-01-04 11:25:56.071 AM

debug

Tapo Integration-2.4.2a: [method:udpTimeout, status:no devices found, error:udpTimeout]

app:102026-01-04 11:25:41.085 AM

info

Tapo Integration-2.4.2a: [method:findTpLinkDevices, action:getTpLinkLanData, timeOut:10, hostArray:[2, 254], pollSegments:[192.168.0], pollSegment:192.168.0, pass1:port 20002, pass2:port 20004]

app:102026-01-04 11:25:38.162 AM

debug

Tapo Integration-2.4.2a: [method:getAllTpLinkDeviceData, discData:1]

app:102026-01-04 11:25:37.450 AM

warn

Tapo Integration-2.4.2a: [parseKlapHandshake:[devData:[udpPort:4e22, type:SMART.KASASWITCH, model:KS240(US), baseUrl:http://192.168.0.27:80/app, dni:F0A731F1D763, ip:192.168.0.27, port:80, protocol:KLAP, status:OK], respStatus:ERROR: localAuthHash != serverHash, action:Check credentials and try again, hs1Success:false]]

app:102026-01-04 11:25:37.144 AM

warn

Tapo Integration-2.4.2a: [status:INVALID, respData:null, error:java.lang.NullPointerException: Cannot get property 'encrypt_type' on null object]

app:102026-01-04 11:25:37.141 AM

warn

Tapo Integration-2.4.2a: [status:INVALID, respData:null, error:java.lang.NullPointerException: Cannot get property 'encrypt_type' on null object]

app:102026-01-04 11:25:37.137 AM

warn

Tapo Integration-2.4.2a: [status:INVALID, respData:null, error:java.lang.NullPointerException: Cannot get property 'encrypt_type' on null object]

app:102026-01-04 11:25:37.131 AM

debug

Tapo Integration-2.4.2a: [udpPort:4e22, type:SMART.KASASWITCH, model:KS240(US), baseUrl:http://192.168.0.27:80/app, dni:F0A731F1D763, ip:192.168.0.27, port:80, protocol:KLAP, status:OK]

app:102026-01-04 11:25:37.113 AM

info

Tapo Integration-2.4.2a: [method:getTpLinkLanData, action:Completed LAN Discovery, smartDevicesFound:4]

app:102026-01-04 11:25:23.982 AM

debug

Tapo Integration-2.4.2a: addDevicesPage

I have just run out of things to try but would be glad to try something more.
--bill

40

The device is being found. The protocol is KLAP (as expected). So we are down to the below message:

The above indicates a potential credential issue.

  • Make sure the case of all characters in the userName are the same as in the Tapo Phone App. (there are reports (unverified) that this occurs)
  • Check the password for special characters. Some of these (unidentified) can cause the login to fail. General recommendation us use a LONGER alpha-numeric password (1.5X the length will provide approximately same protection as allowing special characters). (see the below from a google search:

image
image714×52 4.55 KB

41

Thank you. I do use a period as part of my password. I can change that.
How do I change the password for Hubitat and the Tapo android app?

42

You do not need to change in the Hubitat password. For the Tapo Android app:

For the TP-LInk Tapo (android) app, the following is from a Google search.

image

43

One other item is two-factor authentication. Recommend not enabling it.