We received updated documentation from TP-Link, allowing us to implement webhook-based API calls for both Tapo and Kasa devices. Implementation for Tapo is already complete and currently undergoing testing, with Kasa next in line.
4 Likes
Great to hear. Although a little slow to give me much confidence in future compatibility.
Any chance you have a rough timeline on the Kasa upgrades?
I have given up on TP-Link, I think it shows that they do not care about their customers to have this going on for so long. Wonât be buying any further TP-Link devices.
Iâve moved to the Ikea TRĂ DFRI smart bulbs, which are cheaper and better, IMO.
1 Like
Please keep us updated on the web hook-based AP. I am new to the community and to Homey Pro. I have just purchased my Home Pro 3 days ago and I am rebuilding my smart home on this platform. I have close to 88 Kasa switches/plugs/lights in my entire home. I use the Kasa switches to trigger flows and have spend the better part of 2 days starting the journey of switching everything with over 200 Hue Lights, and over 400 total smart devices in my home, the majority of which are web based. I have a very high bred wifi set up as well with 5 error max-7âs and 2 error exterior 7âs. Everything was working great with my original set up but I like the idea of consolidating everything to a couple of apps running my homes subroutines (over 400 running at all times). I am hoping that Homey can handle the load. I really am not interested in rewiring my entire home with different switches. That would be ridiculous and I would just send back my homey pro hub while in the return dates of Amazon. However, looking and reading all of these comments, I am not certain that Tapo/Kasa will get it resolved on any type of immediate timeline. I have about 3/4 of my homes devices into Homey and have written my first advanced flow for my upstairs recording studio devises and lighting. Most of the smart switches are Kasa as well triggering my studio equipment and mixing consul equipment and computers. The Homey device and software and beautiful and elegant but that wonât cut it if it doesnât work. The process of my rebuild will take months and I would rather cut the journey short if it isnât going to work. I have saved all of my routines in the other apps and am just disabling them as I build the new flows. That way if it isnât going to work, I can factory reboot the homey and re-enable the separate apps routines. Jim
1 Like
Hi Jim!
With the Homey Pro you have the option of using the TP-Link Kasa Lan App as well. I imagine this will require more work setting up (and do check device compatibility before using it), but thought Iâd mention it since you just started.
Iâm confident Homey will come around on the web-based Kasa app, but if I were you i would hold off migrating to Homey for a while.
2 Likes
Any updates on this? I just got a Homey and have some Kasa devices that are getting this ârate limitâ error.
Homey or Homey Pro?
I just purchased two HS300 power strips with 5 devices (lights, small ceramic heaters) plugged into one and 3 devices plugged into the other. Both are used for light and heat for a bearded dragon in two different locations. Immediately started getting rate limit errors, and found this thread. Thanks.
Read thru this entire thread and deleted this app, replaced with the TP-Link KASA LAN app, and rebuilt my flows. The TP-Link KASA LAN has a faster response, and I like how I can block these devices from the internet and work local only. Reserving static IPs for my surge protectors was easy. I donât love these surge protectors, but there doesnât seem to be many choices for us in North America.
Me llego mi Homey Pro (2026) ayer 23 de marzo de 2026 y lo compre simplemente por el sensor de presencia Aqara FP300 porque no pude ponerlo a funcionar con el Alexa que la mayoria de mis automatizaciones se encuentran alli porque no quiero nada complicado pero decidi comprar el Homey y ahora veo que tambien da problemas y mas con los dispositivos TP-Link / Kasa que se deconectan.
Traduccion al ingles:
My Homey Pro (2026) arrived yesterday, March 23, 2026, and I bought it simply for the Aqara FP300 presence sensor because I couldnât get it to work with Alexa, where most of my automations are located. I didnât want anything complicated, but I decided to buy the Homey, and now I see that it also has problems, especially with TP-Link/Kasa devices that keep disconnecting.
If you could please keep the conversation in English as much as possible, then more people will be able to participate and help you. Please translate your post into English, otherwise it will be deleted in three days to keep the thread in just one language as stated in the forum rules Welcome to the forum!
Please do also check out the categories in other languages:
Dansk (Danish)
Deutsch (German)
Español (Spanish)
Français (French)
Italiano (Italian)
Nederlands (Dutch)
Norsk (Norwegian)
Polskie (Polish)
Suomeksi (Finnish)
Svenska (Swedish)
If you need help, because depending on the trust level of your account, you may have limited permissions, please PM me or another moderator or reply to this post.
I am still getting KASA app crashed, even when it not been used. IT is crashing like every second hour. Frustrating !! invested so much in KASA and Homey and automation does not work at all!! I have Homey Pro and using TP-Link KASA LAN
Any solution yet or we move to other devices?
Not sure who youâre shouting to, RSB?
This is just a Homey users forum.
So. This tight rate limit threshold doesnât seem to to get fixed by TP / Kasa;
Did you try the LOCAL app already? This doesnât cinnect to the cloud, and rate limits are not related:
https://homey.app/en-us/app/nu.baretta.tplink/TP-Link-KASA-LAN/.
Youâd really contact Kasa. They throttle the cloud connections for 3rd party controllers like Homey.
This is on local, the kasa app keeps crashing !
You might want to share the issue you are running into, in the dedicated topic for the local Kasa app: [APP][Pro] TP-Link KASA LAN - Smart Plugs and Bulbs (WIFI).
You can also reach out to the developer via the contact details in the app store or via the linked topic.
It also helps if you could provide more details on the crashes and what troubleshooting steps you have already taken. Most community members and developers donât have a crystal ball⊠
I already answered âthe userâ⊠unfortunately sharing no info except of âitâs crashing!â is not helpful (and logs shows no problem because crash, if any, is not in the crash log)
1 Like
