Driver is primarily designed to support activation via Hubitat - not the switch nor the Tapo App. One limitation of wifi devices in Hubitat is that getting status changes is not passive. Hubitat must send a refresh command which gets the current state. HOWEVER, you can change the Refresh Interval in Preferences down to as low as 5 seconds.
I already have the refresh for these particular switches set to 5 seconds. They work for a few hours, then state changes stop getting updated.
If I manually refresh them from the WEBUI, they start working again for a few hours, then stop communicating again.
This is only happening with the TP link driver. Devices that use the Kasa driver are working fine.
More information:
- What model is giving you an issue?
- What version of the integration are you currently on? You need to assure you are on 2.4.1a. This can be found in the logs on any log line.
- Any Log Warn in the logs for the device?
- On the device's "scheduled jobs" tab, are there any jobs scheduled? If so, I need to see that data. Example from one of my devices (I am looking for the refresh):
-
refresh 2025-04-15T16:34:03+0000 2025-04-15T16:33:03+0000 PENDING 3 */1 * * * ?
-
- I am testing vs 2.4.1a to see if I can duplicate. Initial look is all is OK.
models: KS205 & S505 (I just noticed these are matter devices...Should I switch these over to the Matter integration instead?)
Log shows 2.4.1a
Here's my logs:
dev:862025-04-13 04:43:41.089 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 03:43:56.131 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 03:04:31.139 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 02:51:51.125 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 02:44:26.121 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 02:25:03.160 AM
warn
Big Pantry-2.4.1a: [method:ping, ip:192.168.3.17, pingData:PingData(rttAvg: 0.0, rttMin: 0.0, rttMax: 0.0, packetsTransmitted: 1, packetsReceived: 0, packetLoss: 100), pingStatus:FAILED. There may be issues with your LAN.]
dev:862025-04-13 02:24:51.267 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 02:04:56.107 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 01:25:18.187 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Connect to 192.168.3.17:80 [/192.168.3.17] failed: connect timed out, count:2]
dev:862025-04-13 01:25:18.122 AM
warn
Big Pantry-2.4.1a: [method:ping, ip:192.168.3.17, pingData:PingData(rttAvg: 0.0, rttMin: 0.0, rttMax: 0.0, packetsTransmitted: 1, packetsReceived: 0, packetLoss: 100), pingStatus:FAILED. There may be issues with your LAN.]
dev:862025-04-13 01:25:06.118 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 01:12:36.097 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 12:46:00.891 AM
info
Big Pantry-2.4.1a: [method:updated, commonUpdated:[commsError:false, pollInterval:5 sec, logging:[logEnable:false], updateDevSettings:Updated]]
dev:862025-04-13 12:46:00.859 AM
warn
Big Pantry-2.4.1a: Poll intervals of less than 1 minute may overload the Hub
dev:862025-04-13 12:45:59.395 AM
info
Big Pantry-2.4.1a: [method:parseCommsTest, testStatus:success, userMessage:Comms Path (lan/crypto module) OK]
dev:862025-04-13 12:45:59.334 AM
info
Big Pantry-2.4.1a: [method:parseCommsTest, testStatus:success, userMessage:Comms Path (lan/crypto module) OK]
dev:862025-04-13 12:45:58.847 AM
info
Big Pantry-2.4.1a: [method:configure2, dni:242FD0225013, hubDni:242FD0225013, status:OK, action:configure3]
dev:862025-04-13 12:45:58.845 AM
info
Big Pantry-2.4.1a: [method:deviceHandshake, parentChecked:false, updateDeviceData:updating with app data, protocol:KLAP, handshakeInterval:3 Hours, action:exec updated]
dev:862025-04-13 12:45:47.947 AM
info
Big Pantry-2.4.1a: [method:updateChild, baseUrl:http://192.168.3.17:80/app, protocol:KLAP, isEm:false, hasLed:true, currVersion:2.4.1a, newVersion:2.4.1a]
dev:862025-04-13 12:45:45.845 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Connect to 192.168.3.17:80 [/192.168.3.17] failed: connect timed out, count:3, action:Find on LAN then login]
dev:862025-04-13 12:45:45.796 AM
info
Big Pantry-2.4.1a: [method:configure, ip:192.168.3.17]
dev:862025-04-13 12:45:45.268 AM
info
Big Pantry-2.4.1a: executing [method:configure, ip:192.168.3.17]
dev:862025-04-13 12:45:45.248 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Connect to 192.168.3.17:80 [/192.168.3.17] failed: connect timed out, count:2]
dev:862025-04-13 12:45:45.111 AM
warn
Big Pantry-2.4.1a: [method:ping, ip:192.168.3.17, pingData:PingData(rttAvg: 0.0, rttMin: 0.0, rttMax: 0.0, packetsTransmitted: 1, packetsReceived: 0, packetLoss: 100), pingStatus:FAILED. There may be issues with your LAN.]
dev:862025-04-13 12:45:33.095 AM
info
Big Pantry-2.4.1a: [method:handleCommsError, status:408, msg:Read timed out, count:1]
dev:862025-04-13 12:38:18.533 AM
info
Big Pantry-2.4.1a: [method:updated, commonUpdated:[commsError:false, pollInterval:5 sec, logging:[logEnable:false], updateDevSettings:Updated]]
dev:862025-04-13 12:38:18.474 AM
warn
Big Pantry-2.4.1a: Poll intervals of less than 1 minute may overload the Hub
dev:862025-04-13 12:38:16.735 AM
info
Big Pantry-2.4.1a: [method:parseCommsTest, testStatus:success, userMessage:Comms Path (lan/crypto module) OK]
dev:862025-04-13 12:38:16.714 AM
info
Big Pantry-2.4.1a: [method:parseCommsTest, testStatus:success, userMessage:Comms Path (lan/crypto module) OK]
dev:862025-04-13 12:38:16.380 AM
info
Big Pantry-2.4.1a: [method:configure2, dni:242FD0225013, hubDni:242FD0225013, status:OK, action:configure3]
dev:862025-04-13 12:38:16.377 AM
info
Big Pantry-2.4.1a: [method:deviceHandshake, parentChecked:false, updateDeviceData:updating with app data, protocol:KLAP, handshakeInterval:3 Hours, action:exec updated]
*** I just triple verified that there is a static DHCP reservation for this device.
There are no scheduled jobs.
Here's the logs from an HS210 using the Kasa integration. You can see it's complaining about similar, but again, there is a DHCP reserved address. It is also functioning as expected, despite the errors.
dev:1312025-04-16 07:50:19.139 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-16 12:21:39.133 AM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-16 12:21:23.142 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-15 10:13:10.170 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-15 09:47:11.182 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-15 09:30:36.341 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-15 07:13:21.167 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-15 03:05:55.117 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-15 02:44:56.153 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-15 01:43:19.274 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-15 01:42:19.281 PM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 01:42:15.153 PM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 01:25:51.170 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-15 01:25:46.253 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-15 01:24:26.244 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-15 12:42:20.249 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-15 11:18:56.249 AM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-15 11:17:56.236 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 11:17:52.104 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 11:15:08.142 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-15 11:09:33.141 AM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-15 09:48:18.354 AM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-15 09:47:18.319 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 06:25:29.214 AM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-15 06:24:29.192 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 06:24:25.093 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 06:23:29.218 AM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-15 06:22:29.196 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 06:22:25.121 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-15 04:58:26.153 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-15 04:39:41.156 AM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-15 04:34:21.143 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-14 09:36:40.161 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-14 09:22:55.170 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-14 07:36:26.237 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-14 07:15:46.142 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-14 06:44:21.141 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-14 04:52:43.835 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-14 04:52:41.141 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-14 03:40:04.209 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-14 03:38:43.155 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-14 03:37:21.251 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-14 03:36:21.221 PM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-14 03:36:17.133 PM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-14 02:44:10.143 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-14 09:49:06.151 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-14 09:24:16.139 AM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-14 09:22:45.269 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-14 09:22:41.139 AM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-14 09:20:35.214 AM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-14 08:55:27.166 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-14 06:25:34.372 AM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-14 06:24:34.304 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-14 06:24:30.181 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-14 05:05:33.468 AM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-14 05:04:30.857 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-14 05:03:46.190 AM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-14 05:00:35.050 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-14 05:00:13.539 AM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-14 04:59:44.680 AM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-13 08:20:38.498 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-13 07:07:05.392 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-13 07:06:05.404 PM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-13 07:06:01.140 PM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-13 03:32:07.141 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-13 02:46:57.152 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-13 02:46:22.145 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-13 02:30:17.191 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-13 02:30:07.292 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-13 02:27:32.147 PM
info
Down Stairs : setSysinfo: [switch:off]
dev:1312025-04-13 12:36:52.140 PM
info
Down Stairs : setSysinfo: [switch:on]
dev:1312025-04-13 12:26:36.144 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-13 12:25:10.165 PM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-13 08:31:47.490 AM
warn
Down Stairs : setPollInterval: Polling intervals of less than one minute can take high resources and may impact hub performance.
dev:1312025-04-13 08:30:47.490 AM
warn
Down Stairs : [method:handleCommsError, count:4, command:{"system":{"get_sysinfo":{}}}, setCommsError:true, status:retriesDisabled, TRY: CONFIGURE, commonERROR:IP Address not static in Router]
dev:1312025-04-13 08:24:51.134 AM
warn
Down Stairs : setPollInterval: Polling interva
The way you are using them, I would. (By that I mean you rely on a state change for other actions when the action is done externally via the Tapo app or direct pushing of a switch.)
I could not duplicate; however, your logs indicate a significant amount of LAN issues. Sometimes this is caused by routers dropping "inactive" devices because they can not handle the total number of devices. SEARCH on Google using "router dropping devices" for more information.
So I now have several HS200 switches that have suddenly decided to stop talking to Hubitat. They've been fine for a LONG time. Now I can only operate them from the TP Link App but hubitat does not list them, or control them. The Lan Segment is correct. I even got a new one out and used the TP link app to install it. But neither the Kasa or the TP link integration in Hubitat will detect it.
Has there been an update that eliminates these going forward?
No. But some have transitioned to the TP-LInk (Tapo) API and no longer work with the Built-In Integration. That could be the reason. See early posts in this segment for more information.
What is the HW version and the Firmware Version for your devices?
Looking at your Router, are the devices on your router?
HW version is 5.0 and FW version is 1.0.11 for the spare one I just activated. I assume it's on the network because is shows being there in the TP link phone app and it is working with that app.
Thanks for the response Dave!
Best guess is the model has transitioned over to the TP-Link Tapo API. The company is not forthcoming on exact details, but you could TRY the community integration at
Developers / Code Share - HubitatPS - I may write an app that can tell you which to use.
I already tried the TP Link integration too. They don't show up there either.
Check you lan configuraiton. Need to be on the same segment and need to assure your Hub has access to your device.
They are on the same segment and i'm not sure how to be sure my hub has access to the device. It has access to everything else on Hubitat including other TP link devices such as P105 devices.
Do you see any error/warning logs while trying to add to Hubitat?
No sir. In the Kasa Integration it does show everything in the removal drop down if that means anything.
I do show this error in the past log. 2025-07-25 03:27:22.858 PM
error
org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'ERROR' with class 'java.lang.String' to class 'java.util.Map' on line 1142 (method getSmartLanData)
If it is in the "removal" drop down box, the device is still installed. Remove it there and try reinstalling.
The new HS200 is not in the Kasa Integration removal drop-down. The old ones are there and I removed an old/current one and tried to re-install it and it was not found.
I found in the Kasa app there is a full IP address instead of just the first three segments. How that happened, I don't know but let me see what that does when I fix it.
Nope. Still NFG. Quite frustrating and crazy. Maybe I should go back to an old hub backup? And it could it be an update from TP Link to the devices causing the problem?
I would be hearing a lot more. Last firmware update was last year and yours is that version.
You could also try entering you Kasa Credentials and rediscover. This will first try local and if not found, it will find cloud. One condition: tapo/Kasa account must NOT have two-factor authentication.
