# By-pass "rate limited" state in the official Kasa app

**URL:** <https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795>\
**Category:** Ideas & Suggestions\
**Created:** [December 4, 2023, 5:18pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795 "2023-12-04T17:18:43Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andy\_Henderson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andy_henderson/32/80642_2.png) [@Andy\_Henderson](https://community.homey.app/u/Andy_Henderson)\
**Post date:** [December 4, 2023, 5:18pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/1 "2023-12-04T17:18:43Z")

</div>

I have an Amazon Fire HD (bought half price in a sale) that I’m using as dashboard via the excellent “Micro Web Server” and “Dashboard Controller” apps.

To prolong battery life I wanted to detect battery level below 20% and switch on the charger; and then detect battery level above 75% to switch it off again.

I had a spare HS100 power switch so I brought it into service.

At apparently random intervals the HS100 would appear in Homey with a red triangle and a “Rate limited” error.

Initially I thought that might be because my flow had an ‘And’ condition set so that it would switch the HS100 on when battery level was below 20% And the HS100 was not already on. I figured the flow might make an unnecessary status request every time the battery status was queried (set at 15 minute intervals). However, the problem persisted without the ‘And’. It even happened overnight when my phone was switched off so the only device making requests was Homey.

Experimentation suggested the issue was in the Homey Kasa app. I could still operate the HS100 through the Kasa phone app and Alexa even though Homey was rate limited. Restarting the Homey app immediately lifted the block.

To get around the problem I initially added a flow that restarted the Kasa app every few hours which worked for a few days. Not a definitive test but it looked like a fix, but not bullet proof.

It then occurred to me there was a better way.

I already had the Kasa skill in Alexa and the Alexa app installed in Homey. So I added the HS100 from the Alexa app and used it instead of the Kasa one. I’ve never had a problem with the Kasa skill so I figured it would be reliable and so it seems.

Obviously it would be good if the Kasa app could be fixed but I’ve added this note in case it helps someone else facing the same issue.

Andy

---

<div class="post-metadata">

**Author:** ![incog](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/incog/32/110193_2.png) [@incog](https://community.homey.app/u/incog)\
**Post date:** [December 26, 2023, 12:18pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/2 "2023-12-26T12:18:09Z")

</div>

I’m getting this as well, if you repair the device that has this it works straight away, but then does it after after 2 or 3 on/off’s which does appear to be the homey app rather the the kasa side of it.

Very annoying, much like all the zwave issues with the new homey pro.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [December 29, 2023, 3:20am UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/3 "2023-12-29T03:20:34Z")

</div>

@ all, please report to the app developer, otherwise this (long lasting bug) never gets addressed.  
You’ll find the correct support links at the homey.app store app page.

---

<div class="post-metadata">

**Author:** ![incog](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/incog/32/110193_2.png) [@incog](https://community.homey.app/u/incog)\
**Post date:** [December 29, 2023, 12:05pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/4 "2023-12-29T12:05:36Z")

</div>

Your right, and I’ve done so - this is an Athom app, so hopefully they fix it.

---

<div class="post-metadata">

**Author:** ![Vinod\_Sharma](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/vinod_sharma/32/79712_2.png) [@Vinod\_Sharma](https://community.homey.app/u/Vinod_Sharma)\
**Post date:** [April 9, 2024, 9:13pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/5 "2024-04-09T21:13:59Z")

</div>

I’m new to the Homey world! I have the same issue with Kasa and this post may help. Thanks for posting.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [April 9, 2024, 9:38pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/6 "2024-04-09T21:38:13Z")

</div>

They’re working on it, see this thread about the rate limit ‘bug’:

> [@\[BUG\] TP-Link Kasa devices get "rate limited" error every day](https://community.homey.app/t/bug-tp-link-kasa-devices-get-rate-limited-error-every-day/57760/79):
>
> I unfortunately haven’t heard from TP-Link about the issue, will nudge them tomorrow to see if we can increase the limit. Sorry for the inconvenience and keep y’all posted! +1

---

<div class="post-metadata">

**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\
**Post date:** [April 9, 2024, 10:07pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/7 "2024-04-09T22:07:59Z")

</div>

I just had a reply from TP-Link today, it pretty much states the following;

_“Are you still encountering this problem now? Because from our side, the call does not reach this limit. We can consider temporarily continuing to increase TPS for verification issues”_

So we’ll raise it temporarily to see if that fixes the issues, if not, it’s back to the drawing board 🫡

---

<div class="post-metadata">

**Author:** ![Andy\_Henderson](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/andy_henderson/32/80642_2.png) [@Andy\_Henderson](https://community.homey.app/u/Andy_Henderson)\
**Post date:** [April 10, 2024, 1:14pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/8 "2024-04-10T13:14:55Z")

</div>

In my original post I said I thought the issue was with the App rather than the interface to TP-Link because restarting the app made the problem go away (until the next time). I didn’t do a long test but writing a flow to restart the app each night stopped the problem for the duration of the test.

Do we have access to the source code for the app? That would allow us to eliminate/confirm it as the source of the problem.

Andy

---

<div class="post-metadata">

**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\
**Post date:** [April 10, 2024, 1:37pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/9 "2024-04-10T13:37:59Z")

</div>

The application avoids hitting rate limits immediately after restarting because it initiates with fewer calls. Over time, as it continues to run, the frequency of calls gradually increases.

Regrettably, we cannot disclose the code as portions of it are subject to a non-disclosure agreement (NDA).

---

<div class="post-metadata">

**Author:** ![Tori\_M](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tori_m/32/80769_2.png) [@Tori\_M](https://community.homey.app/u/Tori_M)\
**Post date:** [May 6, 2024, 8:10pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/10 "2024-05-06T20:10:19Z")

</div>

I am also having this issue still

---

<div class="post-metadata">

**Author:** ![incog](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/incog/32/110193_2.png) [@incog](https://community.homey.app/u/incog)\
**Post date:** [May 20, 2024, 10:43am UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/11 "2024-05-20T10:43:14Z")

</div>

I was able to turn 2 lights on and off about 10 times in a row and didn’t get the rate limit messages - seems pretty good to me

---

<div class="post-metadata">

**Author:** ![Nephilim983](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/nephilim983/32/118135_2.png) [@Nephilim983](https://community.homey.app/u/Nephilim983)\
**Post date:** [December 8, 2024, 3:19pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/12 "2024-12-08T15:19:59Z")

</div>

I’m encountering this issue right now. It’s getting tedious repeating devices all the time. I had to add notifications in flow every time there’s an issue. So far I’m noticing Homey Pro has a lot of issues that don’t get resolved.

---

<div class="post-metadata">

**Author:** ![Greg\_Hicks](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/greg_hicks/32/121024_2.png) [@Greg\_Hicks](https://community.homey.app/u/Greg_Hicks)\
**Post date:** [July 14, 2025, 3:07am UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/13 "2025-07-14T03:07:15Z")

</div>

Is there any type of solution??? Over halfway through 2025 andd still dealing with this.

---

<div class="post-metadata">

**Author:** ![Geert\_Wouters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/geert_wouters/32/116902_2.png) [@Geert\_Wouters](https://community.homey.app/u/Geert_Wouters)\
**Post date:** [July 14, 2025, 9:12pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/14 "2025-07-14T21:12:37Z")

</div>

I struggled with this issue too. I replaced all the tp-link gear with Shelly unfortunately..

---

<div class="post-metadata">

**Author:** ![Greg\_Hicks](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/greg_hicks/32/121024_2.png) [@Greg\_Hicks](https://community.homey.app/u/Greg_Hicks)\
**Post date:** [July 14, 2025, 10:16pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/15 "2025-07-14T22:16:34Z")

</div>

Thanks, but that is not a solution.

---

<div class="post-metadata">

**Author:** ![Chad\_Kotter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chad_kotter/32/121334_2.png) [@Chad\_Kotter](https://community.homey.app/u/Chad_Kotter)\
**Post date:** [September 2, 2025, 2:57am UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/16 "2025-09-02T02:57:56Z")

</div>

Just bought two HS300 power strips. Getting “rate limited” messages on several of the outlets. Very frustrating. Guess this is another long time problem being ignored… There doesn’t seem to be many other options for individual outlets on smart power strips. I use them for heat lamps, lights, and other accessories for my bearded dragon. I have two power strips because we keep him in two locations. Moving him from one to the other powers off accessories from the unoccupied location. Individual outlet control is needed to provide heat, but not light at night.

---

<div class="post-metadata">

**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\
**Post date:** [September 2, 2025, 4:52am UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/17 "2025-09-02T04:52:57Z")

</div>

> [@Chad\_Kotter](#):
>
> Guess this is another long time problem being ignored…

Unfortunately, we’re dependent on TP-Link in this case. We’re currently exploring ways to enable local control for at least the Tapo products, since the recurring rate limit issues keep affecting users. This would provide a solid solution for Homey Pro users, though unfortunately not for Homey Cloud.

I completely understand how frustrating it is that these products deliver a limited experience. Without TP-Link’s willingness to collaborate with us, there’s only so much we can do on our end.

---

<div class="post-metadata">

**Author:** ![Chad\_Kotter](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/chad_kotter/32/121334_2.png) [@Chad\_Kotter](https://community.homey.app/u/Chad_Kotter)\
**Post date:** [September 2, 2025, 7:30am UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/18 "2025-09-02T07:30:10Z")

</div>

Thank you for your reply. It is frustrating, and I agree that many of the problems are from the manufacturers. Since posting this, I found the **TP-Link KASA LAN** app that seems to be a good workaround so far. I appreciate your efforts!

---

<div class="post-metadata">

**Author:** ![Shoe](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/shoe/32/121229_2.png) [@Shoe](https://community.homey.app/u/Shoe)\
**Post date:** [February 11, 2026, 4:49am UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/19 "2026-02-11T04:49:35Z")

</div>

2026 and this is still an issue.

---

<div class="post-metadata">

**Author:** ![Doekse](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/doekse/32/109415_2.png) [@Doekse](https://community.homey.app/u/Doekse)\
**Post date:** [February 11, 2026, 2:38pm UTC](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795/20 "2026-02-11T14:38:32Z")

</div>

As long as TP-LINK doesn’t change their stance nothing much will/can change unfortunately

[Next page](https://community.homey.app/t/by-pass-rate-limited-state-in-the-official-kasa-app/96795.md?page=2)
