Kasa KP125M Not Updating State

💬 Lounge
1

I'm attempting to use a few new Kasa KP125M plugs. I adopted them to my network using the Kasa app and specifically selected the option that called out that model and matter app.

To bring the plugs into Hubitat I'm using the community Tapo app. I'm able to control the plugs, but it doesn't return any state changes when they are on or off. It always shows them as off. If I tap "On" they turn on but still show as off in any of the Device listings or dashboards.

I do have numerous other Kasa plugs connected using the Kasa community plugin without issue. This app will not allow for the adoption of the KP125M so I was led to use the Tapo community app by recommendation in a few other posts. I'd appreciate any insight anyone has.

2

Have you considered bringing them into Hubitat as Matter devices?

1 Like
3

Matter is the best way to go. I can not duplicate in my environment using Tapo P125M Matter plugs (I really can not afford each and every model). The KP125M and P125M (Tapo) are (in reality) the same device using the same firmware.

If you want to use the community app, I need some more information:

  • Turn on info and debug log.
  • Turn the device on then off one time (observing the device is actually turning on/off).
  • Wait 1 minute then run Refresh.
  • Send me this and the last five event log lines (from the log page).
  • Also send the Model no and Firmware data on your explicit device (from the Kasa App).
2 Likes
4

I replaced a few Kasa switches with Tapo s505 and s515 I put one of each on Matter and the other 2 added to Tapo app then on to HE. The 2 Matter switches have glitches the s515 turns on by a contact sensor that turns on a light it works good but every few times the light turns off. The s505 motion turns the light on and off we usually manually turn lights off but this one turns it back on. The non Matter switches work like they should.

5

Interesting. It looks like the device is being commanded by the Matter initiator (Alexa, Google Home, Smart Things). This is always a possibility with Matter devices. There are always multiple controllers (the Matter initiator, Hubitat and the device's phone app (Tapo, Smart Home, and others).

I use Alexa (when I must), so I can talk to Alexa. Things to check /try to clear up dual command issues with Matter devices:

  • Check the Tapo Phone app and make sure there are no undesired Smart Actions using the device,
  • If installed in Hubitat and Alexa both
    • Check and make sure no Alexa Routines are active that use this device,
    • assure that the Hubitat Amazon Echo skill is not attaching the Hubitat instance to Echo (Alexa).
    • try disabling the Matter device (not uninstalling) in the Amazon Alexa app.
  • Alternate installation method (currently works on Tapo Matter plugs (not bulbs) and may work on Tapo Matter switches),
    • Indicator: Go to the Tapo phone App and select the device. In settings, select "Matter Setup Code". If the screen display includes a Countdown Expires in line, the the Tapo phone App can act as the initiator.
      • If true, try uninstalling the Matter device from Amazon and Hubitat and then reinstalling using the Tapo phone App Matter Setup Code to reinstall in Hubitat.
2 Likes
6

There is only 1 device left on my Tapo app the 1 not in use. I suspect Alexa is to blame since when is told Alexa to turn off the light and it stayed on. The contact sensor hasn't acted out today. I didn't see any difference in speed and I know they seem to always work on the HE I'm just go back to installing the old fashion way. Thanks for the help and have a Merry Christmas

7

Thank you for the response. I can try Matter, but I haven't gone down that road yet.

dev:922025-12-21 06:07:12.070 PMerrorcom.hubitat.app.exception.LimitExceededException: Device 92 generates excessive hub load on line 154 (method parseUpdates)
dev:922025-12-21 06:07:11.927 PMdebugMisc08 (KP125M)-2.4.2a: [method:asyncSend, reqData:refresh]
dev:922025-12-21 05:58:57.915 PMerrorcom.hubitat.app.exception.LimitExceededException: Device 92 generates excessive hub load on line 154 (method parseUpdates)
dev:922025-12-21 05:58:57.775 PMdebugMisc08 (KP125M)-2.4.2a: [method:asyncSend, reqData:setPower]
dev:922025-12-21 05:58:57.769 PMdebugMisc08 (KP125M)-2.4.2a: setPower: [device_on: true]
dev:922025-12-21 05:58:54.954 PMerrorcom.hubitat.app.exception.LimitExceededException: Device 92 generates excessive hub load on line 154 (method parseUpdates)
dev:922025-12-21 05:58:54.703 PMdebugMisc08 (KP125M)-2.4.2a: [method:asyncSend, reqData:setPower]
dev:922025-12-21 05:58:54.637 PMdebugMisc08 (KP125M)-2.4.2a: setPower: [device_on: false]
dev:922025-12-21 05:58:42.327 PMerrorcom.hubitat.app.exception.LimitExceededException: Device 92 generates excessive hub load on line 256 (method updated)
dev:922025-12-21 05:58:42.010 PMerrorcom.hubitat.app.exception.LimitExceededException: Device 92 generates excessive hub load on line 256 (method updated)

There are no events from today, even after witnessing it turn off and back on while commanding it from the device Commands tab.

Value
Unit
Description
Type
Produced by
Triggered apps
command-off			Command called: off()	command	Christmas Indoor On (On)		12/20/2025 8:05:39.774 pm
command-off			Command called: off()	command	Unknown app		12/20/2025 7:48:29.893 pm
command-off			Command called: off()	command	Unknown app		12/20/2025 7:48:24.289 pm
command-off			Command called: off()	command	* Main Dashboard		12/20/2025 7:47:40.079 pm
command-off			Command called: off()	command	* Main Dashboard		12/20/2025 7:47:37.514 pm
command-off			Command called: off()	command	Unknown app		12/20/2025 7:47:13.547 pm
command-off			Command called: off()	command	Unknown app		12/20/2025 7:43:54.833 pm
command-off			Command called: off()	command	* Main Dashboard		12/20/2025 7:42:10.399 pm
command-off			Command called: off()	command	Unknown device		12/20/2025 7:41:50.194 pm
command-off			Command called: off()	command	Unknown device		12/20/2025 7:41:22.048 pm
command-off			Command called: off()	command	Unknown device		12/20/2025 7:40:47.529 pm

Kasa App Info:

Model: KP125M
Hardware Version: 1.0
Firmware Version: 1.2.5 Build 241213 Rel. 172504

8

events show a lot of unknown app, unknown device. I would suggest:

Assure the community integration is the latest version.
Uninstall the device from Hubitat.
Unplug and replug device.
Reinstall to Hubitat.

What it will do:
a. Reset the device in-case it has gone insane.
b. Clear up the unknow associations in the logs.
c. Assure the driver/app are the latest versions.
d. Reset the security for the driver-device interface.

9

Thank you for your assistance so far. I've gone as far as trying those steps with two devices (KP125M) and I actually just installed a third fresh out of the box. Similar results. I can command them on and off, no events shown, no change in state and the logs look the same.

The only issue I'm finding is I installed the community driver using Package Manager and it's showing version 2.4.2a instead of 2.4.3 on your Github. I did completely remove all of the devices, remove the package and reinstall using package manager.

I thought the KP125M would be nice since it would report power usage, but it wasn't a make or break deal. Maybe I just need to go back to using my HS103's.