[BUG] TP-Link Kasa devices get "rate limited" error every day

[Frederic_Guariento]

Hi same issue.

4 tp-link HS110 with metering.
And they do not ansered anymore with Alexa.
Only working with the kasa app

[robertklep]

@perfectmedia

But it is quite stupid that these devices get rate limited every single day, and sometimes multiple times a day.

You do understand that TP-Link is doing the rate limiting, right?

[Peter_Kawa]

@perfectmedia

And while the LAN app sounds like an option,

So, there you have your fix!
But because you don’t want to do anything, and others should in your eyes?

@perfectmedia

It’d just be nice if Athom team would acknowledge this more and actively work on a fix or open it up for third party development and let some other team fix it.

.

@perfectmedia

who probably has 20 devices, then needing to set up static ip addresses, and connect all that over again.

Hmmm… so yeah, that’s at least 5 minutes of work. Less than writing your post

You can consider increasing the DHCP lease time to 1 year (can come with downsides, but it is a way.)
And it saves you 5 minutes!

[fohswe]

Peter, while it’s fine and helpful to suggest workarounds, it is perfectly reasonable to want to have the app fixed (if possible). Not everyone wants to tinker.

Fact remains that this has been an issue since Homey Bridge launched (going on 2 years now), and the app is an official app by Athom. If it doesn’t work as advertised, it should not be put up on the app store.

I can understand that Athom want to advertise the Bridge as working with Kasa (it’s a big brand), but it really doesn’t work out of the box. Simple as that.

[Dijker]

@fohswe

@robertklep

You do understand that TP-Link is doing the rate limiting, right?

So not much Athom can do except pulling the App from the store for everyone…

[perfectmedia]

Well according to Doeske above. He says that tp link is not doing any rate limiting and seeing as this issue doesnt happen with other apps and smart home setups, yes I would say this is an Athom issue that they should be communicating directly with TP Link to resolve. And seeing that this has been an issue since 2019… kind of ridiculous. Get my point of view now? Or should this just still be considered my fault and i should just figure it out myself.

[Dijker]

@perfectmedia

Or should this just still be considered my fault

No one said that afaik, just start bugging TP-LINK and Kasa. The community can’t do anything, Athom says it is kasa and choose your battles

Do you want Homey or TP-LINK more? Replace the one you want.

[Glenn_Seegers]

Tp-link is a horrible company when it comes to support, i had a lot of different devices from them because they where relatively cheap and neat looking. But after a few issues with the devices and support not even responding or just acknowledging the problem and never fixing it i dumped everything in the garbage bin and switched to different brands. Ubiquity for networking, ikea for the plugs, and a synology nas with some quality 4k cameras instead of the tp-link “HD” junk.

[Peter_Kawa]

@fohswe

Not everyone wants to tinker.

I get that, Martin. But it’s not a specific Kasa LAN app issue here.
Also, when using wifi enabled smart home stuff, you’d best gather some knowledge about reserving IP addresses imho.

And, having wifi devices with ever changing IP addresses is very annoying, isn’t it? To me it is.

Unfortunately, for any device which uses wifi with Homey, it’s best practice to use a reserved IP address. Somehow Homey can’t find devices which change IP adresses along the way.
This results in “Device unavailable” errors.

So, just to prevent headaches, it’s best practice to use reserved IP addresses for any wifi enabled device on Homey (and Homey itself).

[fohswe]

I’m not sure what reserved IP addresses has to do with it. It hasn’t been working for me. I reserve IPs for all my smart devices too.

@Dijker
I’m not sure why the combination of TP-Link and Homey is an issue, seems other platforms make it work? Maybe it is the number of Homey users and devices that causes the rate limiting.

In my opinion it doesn’t really matter if it is Athoms implementation or TP-Link “not playing nice”. Fact is the app doesn’t work properly and as such there should at the very least be some kind of disclaimer.

Personally, I think I’m gonna try adding the Kasa devices to Home Assistant and then add them to Homey through the Home Assistant add-on, just to see if that works.

[Sharkys]

@perfectmedia

And while the LAN app sounds like an option, it would not be a quick/easy task for someone like myself who probably has 20 devices, then needing to set up static ip addresses,

There is solution in the Kasa LAN App for dynamic IPs but never tested it - personally using statically assigned IPs for everything. You can give a try and let me know in the Kasa LAN App thread, if you want.
Please note there is test version, which has improved auto-discovery for new plugs/bulb (except of HS300), currently in TEST

[Darrel_Narayan]

how do i get the new version of kasa lan the homey app store only shows 0.2.7

[robertklep]

@perfectmedia

He says that tp link is not doing any rate limiting

And yet I can find posts from people using completely different platforms that are running into rate limiting when using the TP Link API

Also, he’s not saying that they’re not doing any rate limiting, he’s saying that “we aren’t hitting any rate limits”. Which suggests that they are rate limiting.

[fohswe]

I mean, it would be surprising if TP-Link didn’t rate limit, wouldn’t it? Seems reasonable as a protective measure.

That doesn’t make this a user problem to fix, unless this limit is acknowledged by Athom. If Athom can’t work around this, they need to put a disclaimer on the Kasa app

Current “workarounds” as suggested in the thread:

• Use Kasa LAN app if you have a Homey Pro
• Add the devices through a third party service like Alexa (Homey Pro) or Home Assistant (probably works)

If you are on Homey Bridge you are pretty much out of luck.

[BGSmith]

This was very helpful. I am new to Homey (installed Homey Pro today) and was thinking the control was entirely local.

Is the Kasa app on Homey Pro connecting to TP-Kasa through the cloud, exclusively? Not using local WiFi to control the devices?

If so, is the best solution to do the Kasa LAN app, and deal with the static IP assignment?

{My goal is to move my IoTs to a local-only network and manage with Homey Pro (which will have outbound access). Trying to derisk and de-latency my smart home}

[Dijker]

@BGSmith

move my IoTs to a local-only network

This topic is forr the bug in the Athom official app

Please use the community app on a Homey Pro for local connections

[APP][Pro] TP-Link Smart Devices KASA - central topic

TP-Link Smart KASA Devices (KASA non cloud - LAN control only) [TPLINK] Live version : TP-Link Smart Devices Test version : TP-Link Smart Devices | test This app lets you control TP-Link Smart Plugs HS100/KP105 (plug with no energy monitoring) HS110/KP115 (plug with energy monitoring) and Smart Bulbs LB100/110/120 and LB130 as well as the KL50/60/110/120/130 and HS200 from within flows and the (mobile) app Usage note: Use fixed IP addresses for the TP Link devices by reserv…

[robertklep]

@BGSmith

I am new to Homey (installed Homey Pro today) and was thinking the control was entirely local.

Homey itself isn’t entirely local.

[Andy_Henderson]

@BGSmith

If so, is the best solution to do the Kasa LAN app, and deal with the static IP assignment?

That’s where I’d start. The other Kasa app is too unreliable because of the rate limiting problem which seems specific to that app (according to my experimentation - see above).

I also managed to connect successfully via Alexa.

Andy

[BGSmith]

Totally understand. I have this error and was trying workarounds. More than half of my TP-Link Kasa devices have the “Rate Limited” error.

Someone in this thread mentioned that it is Kasa limiting the connections on their cloud API, as opposed to it being on the Homey Pro side.

I have tried the other community supported app, and found it to be a viable workaround, but it does not solve the problem with the official app.

Is there something as a user experiencing this error I can contribute to the community to help troubleshoot or resolve the error? I’m happy to do whatever I can.

[BGSmith]

So far, so good. I’m able to connect the handful of devices that I’ve tried, and control them locally using the community supported app. So far, discovery has worked pretty well. Optimistic.