@Wayne-TP  wrote:
"Tapo or Kasa API hasn't been released to the public, nor have we conducted compatibility adaptation specifically for these open-source platforms like Home Assistant. Since these apps have not undergone our stringent security review, when you enter your TP-Link account credentials and use devices on those platforms, it could potentially expose your devices and personal information to unauthorized access."

 

If that’s the official stance, then it’s time for TP-Link to seriously reevaluate its approach. Platforms like Home Assistant and other automation suites are exactly what modern consumers are looking for — ignoring that is a significant oversight on the part of your R&D team.

And let’s be honest — calling your internal security standards “stringent” in this context feels more like a convenient excuse than a justification. If security is truly the concern, TP-Link could have easily implemented a secure, internally-developed integration for Home Assistant that allows direct API interaction without compromising your ecosystem or user safety. Instead, this just reads like typical corporate deflection: “Not our problem — use our app.”

 

"It is the thing that connects Kasa devices to the non-supported third-party platforms brings possible security risks."

 

That’s not your job to police. If a user willingly chooses to expose their devices through third-party platforms, they do so at their own risk — and they accept that risk. They purchased a product marketed as “smart” and internet-enabled. At the very least, offer a path for those of us who are more technically inclined to use these devices the way we intended to when we invested in them.

"Given the demand for such usage, we now provide a third-party compatibility option to improve the product's compatibility with third-party platforms. You might consider enabling this option to see if it helps resolve the issues you’re facing. However, please be aware that this switch does not guarantee the product's functionality on the open-source third-party platforms."

 

This is a non-solution. A vague “compatibility option” is meaningless when API calls are actively being blocked. The only functioning Tapo integration for Home Assistant is now broken — not because of instability or misuse, but because TP-Link explicitly shut down the way it worked.

It's unfortunate, I had hoped that after a full week of waiting, I’d receive a thoughtful and constructive response from TP-Link. Instead, what I got amounts to “deal with it,” just dressed up in PR-friendly language.

I have 68 TP-Link devices currently in my home, not including my entire Omada infrastructure. If this stance stay, I think I'll be replacing them with products from vendors who understand and embrace openness. This response makes it painfully clear that TP-Link has no intention of resolving this, no plans to support Home Assistant, and no concern for the frustration of customers who invested in your ecosystem — only to be locked out of the functionality we expected, in a way we expected it to be available to us.