@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.

Agree. I've got a ton of Tp-Link/Tapo/Kasa cameras, lights, and plugs that I cannot control with HA.  A similar thing is happening with Bambu 3D printers. They have locked down their firmware so that third party slicers and other add ons will not work. I'm tired of people protecting me when I'm not asking to be protected.  I paid for, I own it and I want to use it the way I want to use it. 

  @Wayne-TP Still no followup?

If TP-Link's response is to treat HA like the ugly step child, I will move my business elsewhere. There are cheaper, more secure options (Zigbee-based).

I would love to see TP-Link establishing a local-first, cloud-second smart home approach, that empowers users to have FULL CONTROL. This would also include TP-Link offering official, secure integration with Home Assistant. After all, I would argue someone proficient enough to setup home assistant is also more likely to understand the security implications and actually prefer Home Assistant FOR security/privacy reasons.

I have 59 TPlink devices and just recently moved to Home Assistant from SmartThings. Being a 2nd class citizen in HA for JUST Tplink was something I wasn't expecting. Everything else in my house just works but almost half of my TPlink devices simple do not within HA after the recent firmware update. 

this is terrible news for sure.  I have been on HomeAssistqnt for years and recently ditched wyze for similar reasons and specifically switched to tapo cams becasue i was already satisfied with my KASA switches and plugs.  And they recently added third party support so I could add my cameras through scrypted.  Which has also been re-authing cams like crazy lately.  I hate that I just bought 3 more power strips and was about to start using them, but i guess ill be sending them back and finally going to all Zigbee and matter devices.  Like real Matter over thread stuff.  I can give all my battery cams to my dad and go all eufy I guess.  Was about to switch to ubiquity anyway, so I might as well drop DECO too.  Sad day for tp-link I guess.

@Wayne-TP

Look, I get you’re just the guy relaying the “official” word from TP-Link, but your response completely missed the point. Nobody here is buying the corporate excuse that this was done for “security.” TP-Link took devices that worked perfectly with Home Assistant and crippled them. That’s not security, that’s control.

@me-gomoto nailed it. We’re sick of companies locking down the products we own. @GuyFromMars said it best: Home Assistant users aren’t the problem, they’re the ones who actually know what they’re doing. Why punish them because others can’t follow simple instructions, or because you want to appeal to “Jonny Homeuser” instead of the people who will literally buy your products in packs of 60 when they work well?

@leftyfb lived it, moving an entire setup over only to find half his TP-Link gear dead after an update. Imagine saving years to automate your home, investing hundreds of dollars into outlets, switches, and control devices, and having it all ripped away by a firmware update that forces you into their app or a licensed third party. That’s exactly what’s happening here, and it’s enraging.

@wbarber69 walked away completely and switched to Matter and Zigbee. That’s the reality of “FAFO.” You just lost a loyal customer ready to go all in, potentially spending thousands over years to expand even further. And that’s not the only loss. “Oh, but that’s just one customer,” how many more walked away quietly? How many said “forget it” and never looked back? For every one voice, there are thousands who simply leave without complaint. That’s a real and silent exodus.

Like me, @n8petersen had a working setup, bought another unit weeks later, and found out the update rendered it useless for exactly the purpose he bought it for. I bought a pack of switches to replace the last dumb ones in my home with Kasa/Tapo, and that same day every single switch got the “No Local” update.

This isn’t a fluke. This is a pattern. Loyal customers who built ecosystems around TP-Link are being locked out. TP-Link needs to understand: people don’t choose your products because of “security.” They choose them because of quality, reliability, ecosystem, and trust. Most of us here are seasoned network and security pros. We know what we’re doing.

So here’s the truth: stop pushing PR responses. Stop brushing off user feedback. Give people local control back or watch the very community that built your brand walk away for good. Deco, Omada, Tapo, Kasa, those names are only strong because of your customers. Not because of “security” talking points.

Fix it. Now.

To every TP-Link customer reading this: if you care about local control, privacy, and the freedom to actually own your devices, speak up. Join this conversation. Demand change. This isn’t just a complaint, it’s a movement. And TP Link... fix your devices so they are VLAN aware... It's 2025 for god sakes.

  @ggbrad 

I specifically went with Tapo for local control.  I even avoided most of their cloud only based devices when I could. It's a good thing they're doing this now, I am only just breaking ground on my new 3200 square foot home and I still in the design phase of deciding what smart devices I'm going to use.  And it obviously won't be tplink.  As a matter of fact I've had a bunch of problems with a lot of their devices lately because of firmware updates.  Cameras not recording the right time in the app, the same model camera just one version newer basically useless compared to its matching predecessor. The switches losing local control.  Tapo bulbs that have to pe re-authenticated every month or so.  This isn't a movement so much as an exodus.  And to think I was going to buy more camera when they openened up the onvif and rtsp support at the request of the HACs integration provider.  I thought, "huh, finally a company that gets it..."  well they've lost my vote.  I guess they do t realize that HA and nabucasa are actually certifying manufacturers now for inclusion in smart home exosystems similar to what the matter consortium has been doing.  Imagine being the only kid on the block without the right certifications. 

wbarber69 wrote

  @ggbrad It's a good thing they're doing this now, I am only just breaking ground on my new 3200 square foot home and I still in the design phase of deciding what smart devices I'm going to use.  And it obviously won't be tplink. 

@wbarber69

As an avid TP-Link user myself, their lack of communication on this issue is infuriating.

As a fellow techie, you were ready to go all in just like me. I recently relocated from Central NY to South Georgia and the first thing I did was replace everything in my house with TP-Link smart devices. We ran lines for Omada networking. All of our cameras were originally set to Tapo but they lacked essential features. I had even planned to swap our locks to Tapo locks.

And sure while I can control these devices via their properitary app, that is not an acceptable solution when 95% of my home automation runs on Home Assistant.

If you are looking for cameras that work well with Home Assistant, literally anything PoE from Reolink is a solid choice. I would suggest Tapo as well if TP-Link actually listened to its users. Unfortunately they clearly do not care enough to fix this problem.

It is disappointing to see a fellow techie abandon the ecosystem but I cannot say I blame you. I am still holding out hope they will address this issue. Congratulations on your new home.

Ooof, this sucks. I recently started on my adventure down the home automation rabbit hole and picked up a pack of plugs during big deal day excited to start getting energy data into HA. Looks like I'll find another company to throw my money at. 

Open to suggestions, looking to get my per room power consumption so I can start planning my solar build out.