# \[APP\] Tuya - Smart Life. Smart Living

**URL:** <https://community.homey.app/t/app-tuya-smart-life-smart-living/146735>\
**Category:** Apps\
**Tags:** official, homey\
**Created:** [December 11, 2025, 1:00pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735 "2025-12-11T13:00:35Z")\
**Posts on this page:** 20\
**Page:** 24

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 18, 2026, 4:36pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/477 "2026-08-18T16:36:59Z")

</div>

I’d recommend using this script:

> [@\[HOW-TO\]\[Pro\]\[Cloud\] - Tool to FIX (advanced) flows after removing and re-adding devices](https://community.homey.app/t/how-to-pro-cloud-tool-to-fix-advanced-flows-after-removing-and-re-adding-devices/65018):
>
> information_source Also available as app: [[APP][Pro]Flow Converter](https://community.homey.app/t/app-pro-flow-converter/154906)rotating_lightwarning Use at own risk! warning rotating_light If you have a broken device which you want to replace or you have to fix flows for your device I made a script which can help with this. Instructions: Device ID you would like to update - - Go to the Homey web app - Devices - Right click on the device to show context menu - Hold down Alt / option key on keyboard - Select “Copy ID”. Write d…

To fix your Flows, if you still have the old device ID at least.

---

<div class="post-metadata">

**Author:** ![Autodidakt](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/autodidakt/32/119715_2.png) [@Autodidakt](https://community.homey.app/u/Autodidakt)\
**Post date:** [August 18, 2026, 4:47pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/478 "2026-08-18T16:47:36Z")

</div>

I have no flows with Tuya, i operate Tuya only manually with Desktop PC via webportal.  
Flows from other App companys tested, sometimes work, sometime not, need restart Company app für Homey Connect… few options… That’s here ot… Not all Tuya devics working with Homey. Alltimes back to smartphone. But want control all devices by PC with big screen anmd alltimes on. ☹  
In Germany we saying “Nichts Halbes, nichts Ganzes.”

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 18, 2026, 5:00pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/479 "2026-08-18T17:00:06Z")

</div>

After app restart, the door sensor via the Tuya Zigbee hub works again.

---

<div class="post-metadata">

**Author:** ![Autogedrocht](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/autogedrocht/32/103824_2.png) [@Autogedrocht](https://community.homey.app/u/Autogedrocht)\
**Post date:** [August 18, 2026, 8:29pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/480 "2026-08-18T20:29:22Z")

</div>

FYI

Sadly it still doenst work stable.

I constantly have to restart app to have connection with the devices. I automatically restart it every hour with a flow, but thats not enough apparently.

With Smartwares app devices always work instantly, so it has to do with Homey for sure.

---

<div class="post-metadata">

**Author:** ![Marcel\_van\_Haren](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marcel_van_haren/32/85849_2.png) [@Marcel\_van\_Haren](https://community.homey.app/u/Marcel_van_Haren)\
**Post date:** [August 19, 2026, 3:52pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/481 "2026-08-19T15:52:47Z")

</div>

Same issue here

---

<div class="post-metadata">

**Author:** ![drenso](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drenso/32/41300_2.png) [@drenso](https://community.homey.app/u/drenso)\
**Post date:** [August 20, 2026, 1:02pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/482 "2026-08-20T13:02:20Z")

</div>

At this time we are pretty confident that any issues that remain are solely caused by Tuya still enforcing an API limit that is a bit too strict. We just asked them again to relax this limit, which is unfortunately all we can do at this time.

---

<div class="post-metadata">

**Author:** ![Joep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joep/32/148855_2.png) [@Joep](https://community.homey.app/u/Joep)\
**Post date:** [August 20, 2026, 1:50pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/483 "2026-08-20T13:50:35Z")

</div>

After the latest update, it has been very stable at my home over the past few days. But I only have 4 Tuya lights and I control them twice a day with a flow (turning them on in the evening and turning them off when I go to bed). Maybe my configuration isn’t reaching the API rate limit.

It might be helpful if it doesn’t work for you, that you indicate how many Tuya devices you are using and how many calls you make in flows, because that way we might find a common thread (read, API rate limit).

What I mean: if a flow polls for information, you get more API calls than if I turn on 2 LED lights in the garden once it gets dark.

---

<div class="post-metadata">

**Author:** ![drenso](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drenso/32/41300_2.png) [@drenso](https://community.homey.app/u/drenso)\
**Post date:** [August 20, 2026, 2:01pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/484 "2026-08-20T14:01:47Z")

</div>

The rate limit only concerns the token endpoint, so the amount of devices is not a factor here.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 20, 2026, 2:04pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/485 "2026-08-20T14:04:16Z")

</div>

Do you mean the m1.tuyaeu endpoint? Because fetching a token every few seconds is quite strange, and that’s probably why Tuya implemented the limit

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/0/a/0a3ff9b093631192842a1369c9c18b19f5371473.png)

 ![image](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/7/c/7cfe87517c6e845681877c8c39a288389c2b064e.png)

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [August 20, 2026, 2:05pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/486 "2026-08-20T14:05:37Z")

</div>

Assuming that Tuya is rate-limiting on client ID, and the Homey app is using the Home Assistant client ID, does this mean that these issues are now also causing problems for HA users?

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 20, 2026, 2:06pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/487 "2026-08-20T14:06:35Z")

</div>

Probably rate limiting on IP. Else, a spammer/DDoS can just spam requests there from 1 IP and get the entire API taken down for everyone. That would be strange

---

<div class="post-metadata">

**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\
**Post date:** [August 20, 2026, 2:08pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/488 "2026-08-20T14:08:31Z")

</div>

But does the Homey app generate _that_ much traffic that single users are being rate-limited?

---

<div class="post-metadata">

**Author:** ![drenso](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drenso/32/41300_2.png) [@drenso](https://community.homey.app/u/drenso)\
**Post date:** [August 20, 2026, 2:17pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/489 "2026-08-20T14:17:46Z")

</div>

Yes, it is affecting Home Assistant users as well.

> [@smarthomesven](#):
>
> Do you mean the m1.tuyaeu endpoint?

Endpoints and domains are different things.

> [@smarthomesven](#):
>
> Probably rate limiting on IP

No, it is a generic endpoint rate limit that is being hit.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [August 20, 2026, 2:20pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/490 "2026-08-20T14:20:12Z")

</div>

> [@drenso](#):
>
> Endpoints and domains are different things.

I know, but is it the endpoint on [m1.tuyaeu.com](http://m1.tuyaeu.com)?

> [@drenso](#):
>
> No, it is a generic endpoint rate limit that is being hit.

That’s strange. So is it per endpoint per IP, or just per endpoint in general? If it’s a general rate limit, that would mean that anyone can take down the API by just spamming a few hundred requests to it, which would break the API for everyone.

---

<div class="post-metadata">

**Author:** ![Joep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joep/32/148855_2.png) [@Joep](https://community.homey.app/u/Joep)\
**Post date:** [August 20, 2026, 2:35pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/491 "2026-08-20T14:35:13Z")

</div>

I share the ID with my HA installation and when Tuya failed on Homey, on HA it just worked. 🫤

---

<div class="post-metadata">

**Author:** ![drenso](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drenso/32/41300_2.png) [@drenso](https://community.homey.app/u/drenso)\
**Post date:** [August 20, 2026, 2:38pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/492 "2026-08-20T14:38:19Z")

</div>

The API endpoint actually differs for each account, so it could very well be that that is the one used for your API calls, yes.

> [@smarthomesven](#):
>
> So is it per endpoint per IP, or just per endpoint in general?

You usually have multiple rate limits which can depend on multiple factors. This can be a relative low failure rate limit, a much higher generic rate limit on client id, and another one specific for an IP. But we are obviously not aware of the specifics at Tuya, just that the general limit was reached that also affected Home Assistant users.

> [@Joep](#):
>
> I share the ID with my HA installation and when Tuya failed on Homey, on HA it just worked. 🫤

That is very well possible. Not all users have the issues as it is all timing dependent (which is also good for us, as with the amount of users with this app answering all support request would have become impossible).

---

<div class="post-metadata">

**Author:** ![Autogedrocht](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/autogedrocht/32/103824_2.png) [@Autogedrocht](https://community.homey.app/u/Autogedrocht)\
**Post date:** [August 20, 2026, 10:21pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/493 "2026-08-20T22:21:53Z")

</div>

Sorry, I cant understand what the problem is with endpoints and rate limits etc.

What can I do to improve stability?

---

<div class="post-metadata">

**Author:** ![Morgan](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/morgan/32/15416_2.png) [@Morgan](https://community.homey.app/u/Morgan)\
**Post date:** [August 21, 2026, 8:18am UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/494 "2026-08-21T08:18:52Z")

</div>

I have no issues since version 1.5.6. 🙂 My devices are reporting if needed, at least every minute.

---

<div class="post-metadata">

**Author:** ![drenso](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/drenso/32/41300_2.png) [@drenso](https://community.homey.app/u/drenso)\
**Post date:** [August 21, 2026, 12:11pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/495 "2026-08-21T12:11:19Z")

</div>

> [@Autogedrocht](#):
>
> What can I do to improve stability?

Nothing! We just heard from Tuya that they are no longer seeing any issues and have removed the rate limit now! This means that everything should be resolved, which also means that we will stop monitoring this topic as closely as we did during this period. Make sure to shoot us an [email](mailto:homey-tuya@drenso.nl) if you are in need of additional support!

---

<div class="post-metadata">

**Author:** ![johnv](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johnv/32/16472_2.png) [@johnv](https://community.homey.app/u/johnv)\
**Post date:** [August 24, 2026, 8:59pm UTC](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735/496 "2026-08-24T20:59:01Z")

</div>

Since a few days, indeed my lamps/bulbs works as expected.  
I do however have an ‘LSC Moodlight RGB+CCT’ multicolor bulb, that is ‘not available’ as soon as I try to control the lamp.

It was working before with the ‘Tuya’ app, both on my Homey Pro (2019) and an additional (free) Homey Cloud account.  
(However, when controlling the device from SmartLife app, it requires a bluetooth connection. On mobile Homey app, it also required a Bluetooth connection. It gives a ‘not available’ upon trying to control it. On web app, the lamp does not change, but gives no error, either).  
The Homey status of the lamp is set to the same value as it was when problems started.

[Previous page](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735.md?page=23)

[Next page](https://community.homey.app/t/app-tuya-smart-life-smart-living/146735.md?page=25)
