No. The plugs seem to be working great! I have installed 2 of the dual plugs and they work fine.
I even created a virtual switch that controls all 4 plugs and they ripple on/off great.
I just wish I could force a static IP add. in the plugs. The best I can do is to manually assign an IP address within the router's DHCP range. That eats up addresses within the DHCP server's range.
Still about the same though.
Thank you for your help!
@djgutheinz, I may have have missed it in this thread but has polling been removed for HS200. I'm getting this error.
java.lang.IllegalArgumentException: Command 'setPollInterval' is not supported by device. on line 6429 (appButtonHandler)
The error occurs from RM4: setPollInterval(10) on Garage light (garage sw)
The setPollInterval is no longer an option in the custom action. The rule worked until the last update.
I've done a repair of the driver, Saved preferences.
I think I have missed something.
I do not think i have the most recent integration, though it updated through Hubitat Package Manager.
I am running Kasa Local Hubitat Integration, Version 6.0.0
is that the most recent version?
When I check the documentation, it lists preferences I do not have for my devices.
Set Poll Interval is no longer an available external command for the plugs. Poll interval is now set via preferences. The error is rule machine not seeing the command.
If you want (tell me), I can add setPollInterval back into the code.
I assume you are talking about the documentation at the link:
"HubitatActive/Documentation.pdf at master Ā· DaveGut/HubitatActive Ā· GitHub"
That is the current documentation.
I would like to quick poll a wall switch HS200. I understand the risks of quick polling. With quick polling I can optimize the use of Hubitat resources.
In the preferences I have the poll set to 5 minutes. I don't need any polling almost all the time. Once the light is on I poll for a manual off at the switch. The quick poll is only on for a few minutes before it is turned off.
I appreciate all the time and effort you put into the TPlink drivers. Thank you.
If you could put the quick polling back for the HS200 I would be grateful and happy.
Next version will add back the command setQuickPoll with input in seconds. Probably next week. Sorry for my error.
I do something similar to that as well with my monitoring of the dishwasher and washing machine. The plugs normally only poll every 30 minutes since Iām not interested in when the appliances are turned on. But once the normal poll detects that the appliance has been turned on, RM will set quick poll to every 30 seconds as I want to know when it has finished. Once it has finished it goes back to polling every 30 minutes.
Thanks for considering putting it back @djgutheinz!
No apologies required.
Well yes I am.
In your screen shots of the device's configuration, there is a box for the IP address.
I do NOT have that box, nor the same application's page.
Has this been removed?
I did assign a static IP address for my two double outlets in my router, and when I click on the gear icon on Kasa app, I see in the application state my four plugs listed with the IP addresses that I assigned to each pair, but no where in the device's page is there any ability to set the IP address.
Has this changed?
I have uninstalled and reinstalled about 3 times, and nothing has changed.
Just wondering if this has been changed?
Thank you.
You can no longer set the IP address directly (the Wiki is being updated now). To update, run the app and select add devices/ update device data.
The IP for the device is on the device's page at the botom under data value deviceIp.
also, in the log I am getting this error:
dev:3682021-02-01 11:58:23.131 warnone SendCmd: IP address updat attempted within last hour./nCheck your device. Disable if not longer in use.
dev:3682021-02-01 11:58:21.936 infoone setSysInfo: switch: on
dev:3682021-02-01 11:58:16.772 warnone Check: Device Name must be first 5 characters of Model (i.e., HS200).
dev:3682021-02-01 11:58:16.768 warnone socketStatus = send error: Socket closed
dev:3682021-02-01 11:58:16.554 warnone Check: Device Name must be first 5 characters of Model (i.e., HS200).
dev:3682021-02-01 11:58:16.550 warnone socketStatus = send error: Socket closed
dev:3682021-02-01 11:35:38.855 infoone setSysInfo: switch: off
dev:3682021-02-01 11:35:38.222 infoone setSysInfo: switch: on
--- Live Log Started, waiting for events ---
The device name is KP400 so it IS the device name and it IS 5 characters.
Strange! When this happens, the plug(s) take about 30 to 60 seconds to respond sometimes, and other times it is right away.
I have created a virtual switch to turn them all on and off together, just to test.
OK that answers that question. I thought I had missed something and that is why I tried several times and read and re-read the instructions multiple times just to make sure.
Thanks!
I think I found the loooong delay problem and what might be causing it.
I have 5 ecobee4 stats and am running Ecobee Suite Manager ver. 1.8.52 by Barry Burke.
I has tons of features that I have yet to fully use.
I does update the stat's status over the internet and is cloud based using wifi.
Ecobee has been know to be very slow with stat updates and sometimes goes down as well. A VERY big negative in the Ecobee community!
From what I have seen so far is that when the stats are updating/polling, wifi response from other apps (like Kasa) seem to halt, or at least have to wait for the stats to finish. Probably because Ecobee Suite has "grabbed" the wifi interface and doesn't let go until it's polling has completed.
This would probably be true with any wifi app in Hubitat.
I will watch it further just to see.
This is my wild guess... I am NOT versed in how Hubitat uses wifi.
Thanks, I will also look at in next version. The error is coming from the socket connect method and is due to the device being unreachable. Probably the unreachable is due to the Ecobee?????
AHHA!!! That makes sense!
Multiple problems would be solved IF the Ecobee's could be local, but Ecobee is not AND they don't seem to want to provide that option!
VERY poor decision on their part!
The more I test the delay problem, the more I see it related to when the Ecobee's update and "hog" the wifi/network connection.
Frustrating!
I am impressed with all the detail you went through for the Kasa integration! Very nice!
Thank You!
Oh, this is a a great idea. Can you share how you set this up? Currently I'm polling every minute regardless of whether the device is in use.
Hi,
Struggling with a plug, for some reason. It fails to install the device and i can't understand why.
I followed the instructions as pr the instructions, and when I come to point 9, I'm stumped.
Log:
app:642021-02-07 21:25:56.768 info6.0.0 initialize
app:642021-02-07 21:25:50.458 warn6.0.0 Failed to install device. Data = 98DAC4322488={ip=192.168.1.155, appServerUrl=https://eu-wap.tplinkcloud.com, plugNo=null, alias=Juletre, model=HS110, type=EM Plug, deviceId=80060C81F0348EB0A8DD54A3EF6DCEC51B920B55, dni=98DAC4322488, plugId=null}
app:642021-02-07 21:25:50.444 debug6.0.0 addDevices: [98DAC4322488]
app:642021-02-07 21:25:50.441 info6.0.0 starting Kasa Integration
Any help or insight is much appreciated..
//
You must have the driver with name "Kasa EM Plug" installed (on your"drivers Code"). For convenience, the link is below.
Dave Gutheinz
Download the Hubitat app
it helped immensely.. thanks.