TP-Link Kasa smart plugs are no longer compatible with Home Assistant

Disclosure: This post contains affiliate links. If you click through and make a purchase, I will earn a commission, at no additional cost to you. Read my full disclosure here.

Update: Nov 23, 2020

A change of heart: TP-Link restores local APIs after user outcry

In a surprising and welcome turn of events, TP-Link has decided to restore local APIs for their Kasa smart plugs, reversing their previous decision to remove local access. This change comes after a considerable number of users voiced their dissatisfaction and concerns regarding the removal of a feature they had initially paid for.

By bringing back local access, TP-Link has demonstrated its willingness to listen and respond to customer feedback, highlighting the importance of a strong user community. With the reinstatement of local APIs, Home Assistant users can once again enjoy seamless integration with their TP-Link Kasa smart plugs, and all customers can benefit from the flexibility that local access provides.

This outcome underscores the power of collective voices in shaping company decisions and ensuring that user needs are not only heard but also addressed. It's a testament to the open-source community's strength and ability to come together in pursuit of a common goal.

In a disheartening turn of events for the open-source and privacy-loving community, TP-Link has decided to block local access to their Kasa smart plugs. A forced update, which leaves users with no choice but to comply if their plugs are connected to the internet, has effectively severed the connection between TP-Link Kasa smart plugs and Home Assistant, our favourite home automation platform.

Despite TP-Link's claim that this move was driven by security concerns, it appears more likely that the company is attempting to lock users into their own ecosystem. This decision doesn't just impact Home Assistant users, but sets a troubling precedent for all customers.

By blocking local access, TP-Link has essentially stripped away a feature that customers originally paid for. This leaves users, regardless of whether they use Home Assistant or not, in a precarious position. What would happen if TP-Link decided to remove a feature that you rely on daily?

As it stands, users have reported on Twitter that TP-Link's HS100 and HS110 smart plugs can no longer be controlled by Home Assistant. These particular smart plugs offered a budget-friendly option for those looking to incorporate non-smart devices into their Home Assistant setup. With the blockade of local access, there's a possibility that this restriction could extend to other Kasa branded products, if not all of them.

If you're keen on maintaining local access to your TP-Link Kasa smart plugs, it's crucial to ensure that they never connect to the internet again. However, if you haven't already blocked their internet access, it's likely that the update has taken effect. Fear not, for there is a glimmer of hope: a script claims to restore local access after the update has occurred.

There's still a chance that TP-Link could reverse their decision, but this will require a concerted effort from users like you. Reach out to them via emails, tweets, and Facebook mentions – public call-outs tend to yield better results. At the very least, TP-Link should consider making local access an opt-in feature, as it's something their customers have already paid for.

Exploring alternatives: ESPHome-compatible devices for Home Assistant users

In light of the recent TP-Link Kasa smart plug issues, a more reliable alternative for Home Assistant users might be plugs and sockets that can be flashed with ESPHome. You can find a comprehensive list of compatible devices here. One popular choice, which I can personally vouch for, is the SONOFF smart plug. These devices are not only affordable but, in my experience, also highly dependable.

A portrait photo oif Liam Alexander Colman, the author, creator, and owner of Home Assistant Guide wearing a suit.

About Liam Alexander Colman

is an experienced Home Assistant user who has been utilizing the platform for a variety of projects over an extended period. His journey began with a Raspberry Pi, which quickly grew to three Raspberry Pis and eventually a full-fledged server. Liam's current operating system of choice is Unraid, with Home Assistant comfortably running in a Docker container.
With a deep understanding of the intricacies of Home Assistant, Liam has an impressive setup, consisting of various Zigbee devices, and seamless integrations with existing products such as his Android TV box. For those interested in learning more about Liam's experience with Home Assistant, he shares his insights on how he first started using the platform and his subsequent journey.

Leave a comment

Share to...