Seeking advice:

I have 29 TP-Link devices on my network (mix of Kasa and Tapo), integrated locally with Home Assistant via the official TP-Link Smart Home integration. I've enabled 3rd Party Compatibility globally and all devices are running the latest firmware.

The Problem:
7 of my newer devices — 6x HS300 v2.0 and 1x KP115 v1.0, all purchased in the last few months — periodically lose local connectivity with the KLAP authentication error:

"Device response did not match our challenge"

 

My older HS300s and plenty of other KP115s that I've had for a while work perfectly with the same setup. It's only these newer units.

What Happens:
When one of these newer devices drops off, toggling 3rd Party Compatibility doesn't bring it back. The only recovery I've found is to fully remove the device from the integration and re-add it, hoping it re-enumerates properly. This is disruptive — I lose automations, entity history, and dashboard configurations each time.

What I've Verified:

• 3rd Party Compatibility is enabled (global toggle)
• All devices are on the latest available firmware
• Credentials are correct — cloud API and other devices work fine
• python-kasa debug logs confirm the KLAP handshake itself is being rejected by the device
• Older units of the same models (HS300, KP115) have zero issues
• Reference: your FAQ at https://www.tp-link.com/support/faq/4416/ and community thread at https://community.tp-link.com/en/smart-home/forum/topic/845326

My Questions:

1. Is there a known difference in the KLAP implementation on newer hardware revisions of the HS300 v2.0 and KP115 v1.0 that would cause this?
2. Would removing all devices from the Kasa app and re-adding them exclusively through the Tapo app resolve the authentication issue permanently?
3. Is there a firmware fix planned that addresses KLAP stability on these newer units?

The older devices are rock-solid, so something changed in the newer production runs. Any guidance would be appreciated.

Thank you.