TP-Link ended support for its IFTTT integration, so the Kasa and Tapo services stopped working on August 1, 2026. Your devices are fine. The official fix is to link your TP-Link account inside the free SmartThings app, then swap each applet's TP-Link triggers and actions for their SmartThings equivalents. Alternatives: rebuild simple schedules inside the Tapo or Kasa app, or move to Home Assistant if you want out of vendor clouds entirely.
If your Kasa smart plugs stopped responding to IFTTT applets in the last week, nothing is wrong with your devices, your Wi-Fi, or your applet logic. TP-Link decided to end support for its IFTTT integration, and the Tapo and Kasa services on IFTTT stopped working on August 1, 2026. IFTTT's own team confirmed the shutdown and posted the official workaround on r/ifttt.
The frustrating part is how quietly this kind of thing fails. Applets do not throw an error on your phone. They just stop firing, and you find out days later when the porch light never came on. Here are your three real options, with the honest trade-offs of each.
What Exactly Happened on August 1?
This was TP-Link's call, not IFTTT's. TP-Link ended support for the integration on their side, which killed both of their IFTTT services at once: TP-Link Kasa and TP-Link Tapo. Every applet that used a Kasa or Tapo trigger, query, or action stopped working on that date.
Your TP-Link hardware still works with its own app, and IFTTT still works with the thousand-plus other services it connects. Only the bridge between them is gone. So the question is which new bridge, if any, you rebuild on.
Option 1: The Official Fix, Bridge Through SmartThings
IFTTT's recommended path is Samsung's SmartThings platform, which supports both Tapo and Kasa devices as partner integrations. SmartThings still has a live IFTTT service, so it becomes the middleman: your TP-Link account links to SmartThings, and IFTTT talks to SmartThings.
Step 1: get your devices into SmartThings. Download the free SmartThings app, tap the plus icon, choose Add device, then Add under Partner devices, search for Tapo or Kasa, pick your device type, and follow the prompts to link your TP-Link account. Your devices appear inside SmartThings without any re-pairing of the hardware itself. Nothing in the official steps requires buying a Samsung hub.
Step 2: swap your applets over. Connect the SmartThings service on IFTTT, then edit each applet: remove the TP-Link trigger or action and add the equivalent SmartThings one, pointing at the same device. If you have a handful of applets, doing this manually takes a few minutes each.
Doing it in bulk. If you have dozens of applets, IFTTT's conversational builder at ifttt.com/create can do a systematic pass: you paste an instruction telling it to find every applet using the TP-Link Tapo and Kasa services and swap those triggers and actions to the SmartThings equivalents on the same devices. We packaged the exact prompt, a migration checklist, and the full walkthrough in a free, MIT-licensed repo: kasa-tapo-ifttt-smartthings-migration on GitHub.
The trade-off: you now depend on two vendor clouds instead of one. If either TP-Link's SmartThings partnership or SmartThings' IFTTT service changes someday, you are back here reading another migration post. For most people that risk is acceptable, because the setup takes an evening and everything keeps living in IFTTT where your other applets already are.
Option 2: Rebuild Inside the Tapo or Kasa App
If your applets were simple schedules or device-to-device rules, you may not need IFTTT for them at all. The Tapo and Kasa apps have their own automation features: schedules, timers, and smart actions between TP-Link devices.
Where this wins: no third-party dependency, no extra accounts, and the automations run in the ecosystem the hardware was built for. A plug that turns on at sunset does not need three cloud services in the loop.
Where it clearly loses: anything cross-service. The moment your automation touches a calendar, an email, a webhook, a location trigger from your phone, or another brand's device, the native apps cannot do it. That cross-service glue is the entire reason IFTTT existed in your setup, so treat this option as a way to simplify the automations that never needed IFTTT in the first place, not as a replacement.
Option 3: Home Assistant, for People Done With Vendor Clouds
The third path is the one the tinkerer crowd will tell you about: Home Assistant, the open-source home automation platform, has long-standing community support for controlling Kasa devices on your local network. Automations run on hardware you own, and a vendor ending a partnership generally cannot reach into your house and break them.
Honest assessment: this is the steepest option. You need always-on hardware to run it, a weekend to learn the basics, and a willingness to maintain your own system. If you have exactly four applets and they are all lights, this is overkill.
But if August 1 was the second or third time a vendor decision broke your automations, Home Assistant is the structural fix rather than the patch. You trade convenience today for independence from every future deprecation notice.
Which Option Should You Pick?
Our plain recommendation:
- Most people: take the SmartThings bridge. It is the official path, it keeps your applets in IFTTT next to everything else you run there, and it requires no new hardware.
- Simple schedules only: rebuild them natively in the Tapo or Kasa app and delete the applets. Fewer moving parts beats more.
- Burned twice and technically comfortable: start a Home Assistant build. It is the only option that removes the vendor-deprecation class of problem instead of relocating it.
Whichever you choose, do it deliberately rather than letting dead applets pile up. Silent failures are the worst kind of automation debt.
The Bigger Lesson: Integrations Break on the Vendor's Schedule
This shutdown is a small consumer example of something we see constantly in business automation: the platforms your workflows depend on change their minds. APIs get deprecated, partnerships end, pricing tiers move, and the automation that quietly ran your operations stops quietly running them.
The fix is not avoiding integrations. It is building them like they will someday need to move: an inventory of what runs where, monitoring that tells you the day something stops firing instead of the week after, and a migration plan per critical workflow. That is true whether the workflow is a porch light or the pipeline that routes every lead your business gets.
Did an Integration Change Just Break Something That Matters?
If IFTTT, Zapier, Make, or a vendor API change took down an automation your business relies on, we rebuild it properly: monitored, documented, and with a migration path. Book a free call and bring the broken workflow.
Book Your Free Strategy Call →