Yes, thats what this thread is dicussing.
The HA Tuya component uses a different Tuya api than Tuya’s app and others, so it has its own unique issues.
Yup but there is an option to use the SmartLife API instead of the Tuya API and I know both work pretty much identically so I was hoping that maybe the SmartLife API was on different servers and would be unaffected. I used to use SmartLife but had to abandon it because of an issue where the integration between it and Google Home got messed up and I could not get it fixed. That issue finally sorted itself out recently so I could switch back if it would help.
Yes, but in this case we know what the issue is, and its on Tuya’s end — rate limiting.
There’s a few posts about this already, just search the forums. Many tests have been done, and the conclusion seems to be that Tuya is seriously limiting the amount of “response” requests. So yeah, we can turn our devices on and off quickly, but its state takes much much much longer to report — sometimes not at all.
As its been said a bunch of time already here, Tuya has absolutely zero need to change this back to the way it was before — Their apps update just fine. They’ve never been fans of 3rd parties like HA — especially with people here running “tuya.force_update” @ 1sec intervals 24/7…
So as it stands now, if anyone is going to use Tuya devices, they have to come up with workarounds to state reporting.
Response from tuya API:
{
“payload”: {},
“header”: {
“msg”: “you can discovery once in 300 seconds”,
“code”: “FrequentlyInvoke”,
“payloadVersion”: 1
}
}
Has anyone else noticed the Tuya API has been working correctly over the last several weeks? My Tuya devices suddenly worked instantly and have been fine since then.
Mine is still the same, takes a long time to update if at all.
1 Like
Has there been any update on this issue?
I am getting the below error in localtuya in HA - any pointers on how to resolve it?
No local control