So did I.
Hi there,
I have 3 HS100 integrated to HE and I very satisfied with both the device and the integration (thanks @djgutheinz!).
I decided to buy again these HS100 but I can't find them at amazon.es (at least for a normal price!).
There's a new device, Tapo P100, and I couldn't find any clear information if it is supported by this integration or not. Anyone could help me clarifying it?
It's not. The Tapo lineup is different from the Kasa lineup and is not supported by this app/driver.
2 Likes
I've never really looked at the logging for these devices as I haven't really had a need to. I'm looking now though so I can get average load for a particular plug to size an UPS. I currently have descriptionText enabled and debugging turned off, but all of the logs just about are trace level.
And no, I don't care if you know the MAC of this plug.
being fixed in next version.
1 Like
New version 2.4.1-1 Available.
Fixes following issues:
- HS300 truncated responses: Further address to allow going back to UPD messaging after fixing the name length and schedule issue through the Kasa App (simply do a Save Preferences)
- Removed trace log message that was inadvertently left in last version
Cosmetic changes for better match with Hubitat "built-in" drivers. - Added back driver/app version to code and to logging lines.
Dave
1 Like
I'm confused by the version numbers. I'm currently on version 6.7.2, and package manager is currently telling me 2.3.4-1 is available, but here you just posted 2.4.1-1 is available. Should I wait for 2.4 to hit HPM? And why are the new version numbers less than the current version?
My confusion. i mistyped in package manager.
Hi @djgutheinz. I have just bought my first KL430 light strip and I have successfully installed it. I notice there are a few predefined light effects available through the Kasa app. Is it possible to activate those using your community Kasa driver? I see there are a few options available that refers to Effects, but I have been unable to activate one of the Kasa effects by following my nose.
When I activate one of the effects from the Kasa app, the driver reports which effect is active:
There is a custom command set to create, set, and delete light effects. Essentially, to create, you set the preset up in the Kasa phone app, then name the app in the command create the effect. Then to use in the future, use the setEffect command. You can also share effects with other Light Strips (for users with multiple strips).
Effect create, set and delete:
Toggle effects via hubitat (from the set effects in Hubitat:
Preference to share effects with other strips:
2 Likes
Thanks @djgutheinz. I got it to work with your instructions. Though I cannot get next and previous effects to work, but I don’t require those functions anyway.
Not sure if this is the right thread to post in ... but here goes. I don't understand how to upgrade. I see:
Kasa Integration Update Available (but clicking on the app doesn't allow me to update?)
HPM indicates "Kasa Integration v2.3.4-1 (app)" (so maybe I don't need an update?)
Device List of a Kasa device shows
- releaseNotes : See: HubitatActive/ChangeLog.pdf at master · DaveGut/HubitatActive · GitHub
- UPDATE_AVAILABLE : App and driver updates are available to version 2.3.4-1. Consider updating.
- lastCommand : {"system":{"get_sysinfo":{}}}
- DRIVER_MISMATCH : Driver version (6.6.0) not the same as App version (6.6.1)
Device/Configure doesn't cause anything to happen
I am so confused. Can someone please advise as to if I need an update, and if so, how would I go about it?
You are good to go with the latest app. The driver mismatch is a spurious error that does not impact performance. You might try doing a Save Preferences to eliminate this error, but no big deal.
1 Like
If I want timely response to the on/off state of switches, then I simply need to reduce the pollInterval from the default 30 minutes? Is there a centralize way to change the polling interval or do I need to edit each device?
Any negative effects to having more frequent polling? Like every 10 minutes?
You must do pollInterval on one device at a time.
Poll intervals down to five minutes have limited and acceptable impact on the Hubitat processing.
The drivers were developed to minimize Hubitat process utilization and a few simple considerations assures no impact to the Hub and the devices:
- Polling. It is only necessary to track device control through the Kasa Phone app and/or physical activation through the wall switch (for Kasa Switches) or power switch on the Kasa power strips. Using Hubitat, Hubitat Rules, or Alexa with the Hubitat Integration do NOT require polling to update almost immediately.
- Alexa. If using Alexa, use the Hubitat integration of the device. Do not use the Alexa Kasa capability. Using the Hubitat integration will assure the device updates immediately when issuing a command through Alexa. (The same is also probably true for Google.)
- Use low intervals on a device only when necessary to capture non-hubitat activation of a device.
- HS300 device. limit sub-one-minute interval on no more that two plugs at a time. It caused issues where the HS300 becomes too busy and non-responsive to polls and commands.
2 Likes
Thanks for the rapid response. I also see that all the update messages are clear today ... so perhaps I'll wait a bit next time, prior to asking for help. 
1 Like
I guess I’m confused. I switched from the community app to the built in one some time ago. Probably hadn’t added a new device since then. Picked up the EP40 outdoor plug for Christmas lights and can’t seem to add it to Hubitat. Added to the Kasa app no problem. The Kasa app on HE doesn’t see it. Plus it seems to keep trying to re-add two existing devices. Of note is the button that says “Migrate Kasa devices to built in app.” Does the built in app have that button? Anyway, I remember when I used HPM to install the community version you had to add drivers for each new type of device before it would add it. Is that the issue? Confused.
TIA
If you use this, you are running the built-in app. The Community App does not have this button.
Please explain what you mean by this.
If you are using the community app, then the driver for the EP-40 should be there.
I would try relocating the plug (temporarily) nearer your wifi router. Make sure you assign a static IP address, and try to add again. If it works, relocate to the final location and see if it still works. If that does not work, Private Message me.
PS - you might want to look at the installation section. Link: HubitatActive/KasaDevices/Docs/Install.pdf at master · DaveGut/HubitatActive · GitHub
I"m working through this now. The installation guide was super helpful. I hadn't seen it. The big problem (now resolved) is the the Kasa Integration does not inherit the subnet mask from the hub. These new devices are not on a second Class C address space. All my previous IP addresses were in 192.168.4.x and that EP40 was assigned 192.168.5.1 by my Eero network. Hence it couldn't see it. I added 192.168.5 as a network to scan and it is working. I am now adding static addresses for all of my Kasa devices. I have two devices that keep showing up as newly found devices, even though they already exist. When I try to add them I get an error:
dev:852022-11-27 07:05:34.200 AMinfoStudy Motion is active
app:25792022-11-27 07:05:22.217 AMerrorgroovy.lang.MissingMethodException: No signature of method: davegut_KasaIntegration.prodVer() is applicable for argument types: () values: []
Possible solutions: println(), println(), grep() on line 336 (method addDevStatus)
app:25792022-11-27 07:05:22.074 AMinfoKasaInt: addDevStatus
app:25792022-11-27 07:05:19.066 AMwarnKasaInt: addDevice: [status:failedToAdd, label:Workshop Vac, driver:Kasa Plug Switch, ip:192.168.4.232, errorMsg:java.lang.IllegalArgumentException: A device with the same device network ID exists, Please use a different DNI]
app:25792022-11-27 07:05:19.028 AMinfoKasaInt: addDevices: [selectedDevices: [50C7BF114CF8]]
So, I'm guessing something got messed up along the way in the past and I am going to try removing these two devices and re-adding them. Neither have a lot of rules built around them so it's relatively easy to remove and re-add. Thanks for the quick response and I apologize for how long it took me to try these things out. Yesterday was an all-out decorate-a-thon.
And that worked. I removed HS100 device called ShopVac and then I was able to re-add it successfully. Don't know how it got messed up, but it's good now. One more to go and then I think I'll be all straightened out. Thanks for your help and pointing me at the installation instructions.
