[APP][Pro] TP-Link KASA LAN - Smart Plugs and Bulbs (WIFI)

Apps
, ,
309

I honestly don’t see anywhere to debug from that kasa app, but at this point this is over my head. I’ve tried removing the devices and adding them again and it’s the same error every time. If it was just one switch that would be one thing but it’s every one of my kasa switches. They still work with no issues from the kasa app, and they still work with no issues throughout Alexa, but for whatever reason they will not work with Homey. They didn’t work with the official TP-Link kasa app which brought me to this app, which worked great for awhile and then just one night all kasa switches stopped working with homey

310

Is this what you need?

f7be36fd-fd9a-4e91-b255-dc03235e324b

311

I’m looking into some possibilities to incorporate some of the devices which are not supported by the API, which are :

Plugs: EP25, HS100, KP125M
Power Strips: EP40M
Wall Switches: HS200, HS220, KS205, KS225, KS240

Without having those devices myself nor having official API, can’t even attempt to do the magic despite I can’t promise I will make it work after all.

I’m searching for someone willing to support this app development, who has skills and ability to provide :

  • port forwarding for external access (public IP might be necessary or knowledge of Tailscale solution) - both can be revoked after end of tests - necessary for CLI installation and debugging
  • access to Homey on manager level (please beware of the privacy risk) - same as above
  • TPLink credentials (again can be reset after the tests) - can’t test authentication without credentials

For period of 1 week up to 1 month, can be provided adhoc only, if needed (enable/disable) as my free time for this hobby allows.

If you are the right person, contact me via DM.

Beware, you are letting stranger in to your house, literally. So it’s recommended only to those of you knowing what they do, despite I have some history here, you can’t trust stranger. But still offering this option to everyone.

312

I start seeing some reports about some devices not being reachable anymore.
If those devices are listed in my message above, that’s the reason.
If not, please check in the KASA App you have enabled 3rd party compatibility :

3rd party
3rd party1245×948 50.7 KB

313

Sharkys, ping me, I will assist you.

314

I have prepared a substantial update for the TP-Link KASA LAN app.

https://homey.app/en-cz/app/nu.baretta.tplink/TP-Link-KASA-LAN/test

This update adds authenticated local-LAN support for newer TP-Link SMART devices:

  • KS225 — on/off, dimming and LED control
  • S500D — on/off, dimming and LED control
  • KS240 — separate fan and light devices, including on/off and level control

The app still communicates with these devices locally. TP-Link account credentials are required only to authenticate the newer encrypted local protocol.

The update also includes:

  • TP-Link TDP v2 discovery while retaining legacy Kasa discovery.
  • Automatic discovery and manual-IP pairing.
  • Separate and safely cleaned-up pairing sessions.
  • Improved polling for ES20M, HS110, HS220 and KS230.
  • Compatibility preservation for existing paired devices and Flows.

I previously asked for help from owners of these devices in this post, followed by this reminder. Not even a single volunteer with suitable hardware was available, so physical-device testing has still not been possible.

What I need tested

For KS225, S500D and KS240:

  1. Automatic discovery.
  2. Manual-IP pairing if automatic discovery fails.
  3. Pairing with your TP-Link account email and password.
  4. On/off control and status updates.
  5. Dimming or level control.
  6. LED control on KS225 and S500D.
  7. Both fan and light channels on KS240.
  8. Operation after restarting the TP-Link KASA LAN app.
  9. Recovery after the device’s IP address changes.

For existing ES20M, HS110, HS220 and KS230 installations:

  1. Confirm that existing paired devices remain available.
  2. Test controls and status updates.
  3. Test power measurements where supported.
  4. Confirm that existing Flows still work.
  5. Restart the app and confirm that communication resumes.

Existing KS225, S500D or KS240 devices may require TP-Link credentials to be entered in the device’s Advanced Settings after updating.

If something stops working

Please do not remove the paired device immediately, because doing so may affect existing Flows.

Instead:

  1. Restart the TP-Link KASA LAN app once.

  2. Reproduce the problem.

  3. Generate an app diagnostic report immediately.

  4. Share the diagnostic-report ID together with:

    • Exact TP-Link model.
    • Hardware and firmware version, if you are able to obtain it (eg. via oficial KASA App).
    • Whether the device was newly paired or already installed.
    • Whether automatic discovery or manual IP was used.
    • The action that failed.

For legacy Kasa devices that suddenly become unreachable, also verify that “Third-Party Compatibility” remains enabled in the Kasa app.

Successful reports are welcome, but failure reports with diagnostics are equally valuable. Community testing is the only practical way to make this update reliable across the different hardware and firmware revisions.