[RELEASE] TP-Link/Kasa Plug, Switch, and Bulb integration

Version 6.4.0 Update.

  • New Installation:

    • Use Hubitat Package Manager.
      • Title: "Kasa Plugs, Switches and Bulbs"
      • Caution: DO NOT USE "Cloud Kasa Plugs, Switches and Bulbs"
  • Manual Installation:

  • Updates

    • New Driver for Light Strips.
      • Upgrade instructions:
      • Install the Driver
      • Open the device's edit page and under "Device Information" change "Type" to "Kasa Light Strip" from the drop-down. Save Device.
      • Do a Save Preferences (no need to change any preferences).
    • Function Changes from Color Bulb:
      • Effect Create: Creates an effect using the operating effect. Effect must be on when selecting.
      • Effect Delete: Deletes the effect named in the input. Input is CaSe sensitive.
      • Effect Set: Starts the listed effect on the light strip.
      • Bulb Preset Create: Creates the currently displaying bulb setting as the entered name. Works for non-strip settings. Good for naming preferred lighting states for day-to-day use.
      • Bulb Preset Delete: Deletes the named preset.
      • BulbPreset Set: Turns the device on and sets the light to the preset values.
    • Added Functions for Color Bulbs:
      • Bulb Preset Create: Creates the currently displaying bulb setting as the entered name.
      • Bulb Preset Delete: Deletes the named preset.
      • BulbPreset Set: Turns the device on and sets the light to the preset values.

Kasa Integration Installation, Reference, and Troubleshooting Guide.

Disclaimer: No association with Hubitat
This integration is custom code developed by a Hubitat community member - with support from other community members. It is in no way certified by Hubitat. The developer has fully tested this code within a home environment using available TP-Link/Kasa and other devices. No significant problems have been found that would impact other integrations; however, the complexity of the Hubitat system does not guarantee some level of adverse interaction in other installations.

TP-Link Cloud connect (working)
FS: TP-Link HS-100 wifi outlets (qty 3)
I'm off the cloud! (mostly)
Just got my hub and a quick question
New here; Migrating from ST as soon as HE arrives!
Community Apps
Control Alexa linked devices from Hubitat?
Testing socket, telnet and websocket interfaces
Kasa Integration HS300's not detected yet HS110's are
Where to start with buying devices in Canada
Newby stuck on adding or selecting Amazon Echo connected devices
LAN Device discovery - no devices found
Lighting, WiFi
Several beginner questions: Remote access, Scenes, Buttons, Schedules, etc
AU/NZ Deals
Non-Cloud Presence Sensing - What's Best?
Smart plugs
Time versus cost decision, to be made in the fog
Received C7 Hubitat - Need Help First Time Owner
Received C7 Hubitat - Need Help First Time Owner
[RELEASE] Echo Speaks v3 + Actions
Show Off Your Dashboards!
Suggestion: I need a 6-12 port power strip
Smart Life (Tuya) vs Kasa (TP-Link)?
Another User Jumping from Wink
Outdoor 2 outlet plug
Mode lighting not firing
AUS outlet switch with power wattage usage(not cumulative hours)
Can Hubitat Elevation be useful to me?
Cheap and good smart plug
Hubitat for AUS/NZ Chat
AU/NZ Products and Retailer Guide
Hubitat for AUS/NZ Chat
Hubitat for AUS/NZ Chat
Do any of you use WiFi devices with h.e? What access point do you use?
Washer / Dryer
Home automation Noob Questions
Migrating from Wink Hub 2 to Hubitat
Hubitat for AUS/NZ Chat
Kasa tp-link and currentValue
Here is my setup, sans Hubitat
Planning my move from smartthings
Move from wifi switches & Alexa to HE
Welp... I'm dead in the water!
TP-Link Cloud connect (working)
Considering move from ST to HE
New to this. Question on plugs
Anyone know if these can monitor power usage?
Kasa KS220M
Connecting Devices - Factory Reset
[RELEASE] Hubitat Dashboard - Android dashboard app
HE & Kasa, Aqara, HomeKit, GA, homebridge, HA, etc?
What comes first - Connect device to Google or Hubitat
Kasa HS300 energy monitor data?
Anyone have any personal experience with tp link kasa lightbulbs?
What's Next for HE?

Just want to post a thanks to Dave. First for being patient enough to deal with a total noobs questions and being very patient about it. Second for jumping on board and saving me any more suffering trying to figure this out.

EDIT: Works perfectly!!


THANK YOU DAVE!!! Truly appreciate your work!

Wow....super excited. Thanks Dave!!

I saw in the logs that devices this updated every 30 minutes. If someone manually activates it, the status will be synchronized within 30 minutes in Hubitat. However, the "refresh rate" command in the driver does not work. And if we change is parameter. The default 30 minutes refreshing will not work anymore.

Thanks for the feed-back. Actually, Hubitat does not have a Capability Refresh. I added the command in the metadata to keep the ability (since the device can be controlled outside Hubitat and SmartThings).

I just test. It works per spec after changing frequency. I did find that runEvery1Minute does not work in Hubitat.

With smartthings for tp-link devices. The poll function worked very well.

But in RM I do not see the tp-link for the POLL function

Poll is not there (forgot need). I can add back in (where poll does a refresh). Take about 5 minutes to add. Do you want it?

UPDATE. Just updated the code on GitHub for

  1. Remove "runEvery1Minute" command which causes an error in Hubitat.
  2. Add back the exposed "poll" command.

The poll add may or may not help your RM functions. Note that Hubitat does not have the Capability Poll. So if the app is looking for capabilities, it will not work. Same is true for Capability Refresh. If this is the case, you can look for the capability switch and know that the tp-link devices have the "poll" command and you can send them!


1 Like

the refreshrate in the driver every 5 minutes works really well. I will not even need the RM.

Good work. Thanks you :ok_hand:

1 Like

Thanks for this! I completely forgot I have TP Link plugs I don't use since I couldn't see them in ST (wanted a central place to see everything). What's the best way to subscribe to any updates you make have on this down the road?

Has anyone got this to show up in the Dashboard?

I have a plug on several dashboards set as an outlet and as a switch.

What did you have to do? Mine is working through Hubitat as a device, but does not appear within Dashboard as a device to add. Thanks

I didn’t do anything special, that I know of. If it is showing in your device list, it should be available. When you create a dashboard or edit an existing one from the apps web page, are you able to see the plug there in the list of devices to be exposed to the dashboard? (I select all devices for each dashboard because I have a terrible memory)


Too funny. All my Dashboards I had selected All Devices when I created them, Somehow, this one wasn't. Could be that I was testing the ability to chose the devices in advance to have the Dashboard auto create itself with those pre-selected device choices. Thanks for the sanity check :slight_smile:


Just thought I would leave this here.
Pretty good deal on these plugs.

1 Like

Hi Dave (@djgutheinz ) and/or anybody else

I have a new Pi 3. Installed node.js on it; version 10.8.0
Installed the Hubitat driver, added device & filled in the correct IP addresses as required for my switch in the Hubitat environment.

I'm stuck on what to do to integrate it with the node.js server...
Can somebody provide me with a little more granular information on how to implement the TP-Link node.js side of things (I'm a Pi noob)

Thanks in advance

1 Like

OK, figured it out by myself - well, Google did!

So for those that want to follow in some footsteps:

  • I created a folder TPLINK in /home/pi
  • Copied/Saved TP-LinkHub_v2.js to this new folder created above; no modifications were made to it
  • Edited the file \etc\rc.local; you may have to change permissions on it before editing to allow it to be saved again. This is done to allow the node server to start up after a pi reboot or power outtage
  • Added the line sudo node /home/pi/TPLINK/TP-LinkHub_v2.js < /dev/null & just above the exit 0 command; saved the file

Before rebooting the Pi, test this command sudo node /home/pi/TPLINK/TP-LinkHub_v2.js < /dev/null & from a Terminal window first to ensure it doesn't give any errors; cross-check in your Hubitat setup the commands are being executed/responded to via the Logs window

Several web sites listed the command to be added to the rc.local file as
su pi -c 'node /home/pi/app.js < /dev/null &'
While this worked from a Terminal window, it always prompted me for a password, so it would never execute properly in the rc.local file upon reboot

My knowledge on the Pi and any flavour of *ix is severely limited. While I may have managed to get it to work for me, your mileage may vary. Regrettably if you run into any issues with these steps I am 99% certain I will not be able to assist.


I am trying to use my newly configured Tp-Link switch in Rule Machine, specifically using the Poll command.

It does not however show up in both the device list of "Refresh and Poll" or "Poll". [Showing just Poll]
My understanding was 05-05-18 - Updated to remove "runEvery1Minute" and to add in "poll" command.

Any ideas?



Download the Hubitat app