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

[djgutheinz]

Version 6.6.0 Update.

• New Installation:
  • Use Hubitat Package Manager.
    • Title: "Kasa Plugs, Switches and Bulbs"
    • Plese DO NOT USE the old "Cloud Kasa Plugs, Switches and Bulbs"
  • Manual Installation:
    • Location: HubitatActive/KasaDevices at master · DaveGut/HubitatActive · GitHub
    • Instructions: HubitatActive/Documentation.pdf at master · DaveGut/HubitatActive · GitHub

App Update from 6.5.4:

• Moved manual and cloud installation to under a switch to avoid confusion. LAN is the preferred installation method.
• Updated configure devices to smooth out operation.

Driver Code Update:

• Fixed null level issue.
• Added link to help documentation on device's edit page.
• See: HubitatActive/Changes.pdf at master · DaveGut/HubitatActive · GitHub

Links:

• Kasa App: https://raw.githubusercontent.com/DaveGut/HubitatActive/master/KasaDevices/Application/KasaIntegrationApp.groovy
• Plug Switch, EM Plug, MultiPlug, EM MultiPlug: https://raw.githubusercontent.com/DaveGut/HubitatActive/master/KasaDevices/DeviceDrivers/Plug-Switch.groovy
• Dimming Switch: HubitatActive/DimmingSwitch.groovy at master · DaveGut/HubitatActive · GitHub
• Color Bulb: https://raw.githubusercontent.com/DaveGut/HubitatActive/master/KasaDevices/DeviceDrivers/ColorBulb.groovy
• CT Bulb: https://raw.githubusercontent.com/DaveGut/HubitatActive/master/KasaDevices/DeviceDrivers/CTBulb.groovy
• Mono Bulb: https://raw.githubusercontent.com/DaveGut/HubitatActive/master/KasaDevices/DeviceDrivers/WhiteBulb.groovy
• Light Strip: https://raw.githubusercontent.com/DaveGut/HubitatActive/master/KasaDevices/DeviceDrivers/LightStrip.groovy

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.

[cwwilson08]

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!!

[aaron]

THANK YOU DAVE!!! Truly appreciate your work!

[robert1]

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

[tjeannot44]

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.

[tjeannot44]

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

[djgutheinz]

do not see the tp-link for the POLL

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!

Dave

[tjeannot44]

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

Good work. Thanks you

[linh]

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?

[bobstrenger]

Has anyone got this to show up in the Dashboard?

[bjcowles]

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

[bobstrenger]

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

[bjcowles]

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)

[bobstrenger]

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

[cwwilson08]

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

Amazon.com: Smart Home Starting at $10

[GatVlieg]

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
J

[GatVlieg]

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

Note:
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

Disclaimer:
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.

[GatVlieg]

@djgutheinz

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?

Thanks
J

[GatVlieg]

Hi Dave (@djgutheinz)

The device also does NOT show up in RM for a refresh.

Looking at the driver code, it also appears it already has both capabilities: poll & refresh

metadata {
definition (name: "(Hub) TP-Link Plug-Switch",
namespace: "davegut",
author: "Dave Gutheinz") {
capability "Switch"
capability "Sensor"
capability "Actuator"
command "refresh"
command "poll"
}

Thanks
J

[ogiewon]

Those capabilities may be case sensitive. Change to Poll and Refresh.