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

Version 6.3.1 Update. Color Bulbs only.
Fixed issue with Hubitat Dashboard "color bulb" tile where setting color temperature to zero when a color is set causes the Color Temp slider to disappear.

  • Fixed method setColorTemperature to properly range the set color temperature.
  • Fixed method updatBulbData to not reset attribute Color Temperature if the value from the device is 0.

New version 6.3.0 with following changes:

  • Attributes: connection(LAN/CLOUD) and commsError(true/false), Added and deleted associated states.
  • Communications:
    • Added LAN UDP Communications with associated changes to method parse and new state.lastCommand
    • Removed LAN Raw Socket Communication with associated states.
  • Error Handling. Change to repeat first command only, do not change poll/power poll intervals.
  • Multiplugs: Coordinate attribute connection, state.pollInterval, and settings bind / useCloud amoung devices.
  • On/Off Polling, Power Polling, and Refersh
  • Merged three function control into a single command, setPollInterval. I use a command to enable users access through rule machine.
  • Power reporting: Reduce event handling in overall system.
    • If power is below 5 W, will update if current power != new power +/- .5 W.
    • Otherwise, will update if current power != new power +/- 5 W.
  • Data Cleanup. Added method to clean up data, settings, and states from versions back to 5.3.3.
  • Bulbs. Converted capability Color Temperature to new definition.
  • Save Preferences: Added method to log all system states and data at the end the command.
    • This provides trouble shooting data for issue resolution with the developer.
  • Update Process: After updating code, run Application then Update Installed Devices.
    • Will execute method updated on each device, including data, setting, and state updates.
    • Still recommend checking each device's preferences and execute a Save Preferences.

Acknowldegement: To the many HubitatEnvironment, SmartThings, and gitHub users that have contributed to my knowledge and resolution of anomalies - Thanks now and forever.

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?
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
Considering move from ST to HE
Planning my move from smartthings
Move from wifi switches & Alexa to HE
Welp... I'm dead in the water!
TP-Link Cloud connect (working)
Here is my setup, sans Hubitat
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?
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

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