Not mine… still takes minutes for the UI to update once changed.
Same problem here. Is it complicated to flash tuya cover switches ?
My unflashed Tuya lights are behaving again (turning on and off From HA dashboard with the same delay as asking google to do it).
That issue is apparently due to new and highly variable rate limiting by the Tuya servers. Therefore we can expect to see variations, but it doesn’t mean the issue has been fixed.
1 Like
Is it complicated to flash tuya cover switches ?
I guess it depends on your definition of “complicated”. I’m sure some who have done it successfully would say that it’s not too complicated.
But:
- Many people report issues with the process that prevented it from working for them, maybe to do with the complexity of the process, maybe issues to do with particular devices or software platforms.
- It’s not guaranteed to provide all of the original functionality of your device, but it’s hard to tell what it might affect unless you can find specific comments about your specific device.
- It depends a great deal on the version of firmware on your devices. Tuya has lately been putting out firmware updates designed to block Tuya Convert from working, unless you are prepared to open up the device and do some soldering.
I think in the end all you can do is try it and hope it doesn’t brick your device. Fortunately that doesn’t seem to happen too much, even if the conversion is unsuccessful.
mmm ok, thanks for your reply. I’ll wait to see if tuya will increse this rate limit…
I wouldn’t hold your breath for that one
I’m more concerned about the Tuya api change that broke light colors at the same time as the rate limiting issue. I don’t know if anyone is working to fix that.
I have been having this issue for a week or two and finally started looking to see if I was alone. I guess I am not. Anyway, one thing I noticed is that when the state is incorrect in HA and I restart the server they are always correct on reboot. Now this may just be a timing thing, but if not, does HA check the state at boot differently that it does at other times?
does HA check the state at boot differently that it does at other times?
No, it’s that rate limit thing. HA just does the same state check as normal at startup.
About half the time now when I turn a Tuya device on or off from Home Assistant, it bounces back to the wrong state, then corrects itself after about 30 seconds. The problem is that it is getting that Rate Limit response instead of a valid state response when it checks right after the on/off, but it’s erratic.
Hey, the color bulb color setting issue is suddenly fixed with the Tuya component. No change in code, so it must have been fixed by Tuya in the api as mysteriously as it was broken last week.
Still no help for the rate limit issue, but I that’s not as as serious for me since it fixes itself within 30 seconds. Unfortunate if you have any automation depending on the state of the bulb though.
I honestly don’t see tuya reverting back to before with their rate limiting; it serves them no purpose to do so with 3rd party intergrations they don’t officially approve of us using.
From their point 0f view I could see why they did this; how many people using HA alone were blasting their servers 10000+ times a day with improper state or polling checks? I know after the last break HA implemented the tuya.force_update service which i can only imagine how abused that was. I’ve seen posts on these forms with automations to poll force_update every second!!!
So I think we’re going to have to find a new solution to get real-time states without relying on tuya to provide them in real-time.
Is the consensus here then that Tuya will be this way indefinitely and we need to move away from Tuya smart plugs?
What are some good alternatives that are equally easy to use?
I’ve actually (in the short term) started moving to IKEA Tradfri bulbs running off my HUE hub. There not very expensive, and seem to Integrate well with hue and hass.
I have this same issue, and I see that you have been at it for some time. Rebooting my HA makes the integration work great for a little while. (sometimes)
Can you tell me the github issue number that you opened for support on this? The last time we had an issue with Tuya we needed to open a few GitHub issues until the correct guy noticed, and took action.
I haven’t personally opened one; but some people have. I’ll try and find those when I’m home. But if I remember correctly when I read them, this is a Tuya API issue and nothing to do with hass. Tuya has decided to enforce a rate limit now which severely delays state polls. That seems to be the only issue at the moment with tuya. As far as functionality, they do “work” when toggled, but any automations or scripts that rely on a bulb/switches state won’t function very well; as that state takes upwards of 5-10min sometimes (if at all) now.
There’s a few really shitty solutions. Some include using input boolens and basing the state off those (not very reliable), some have gone with some py scripts to attempt to guess the state based off a few variables (again, not very reliable, and definitely not instant), some have decided to flash what they can with tasmota (best solution. If you can).
But speaking for myself, I’m done with Tuya and their BS. This is not the first time something like this has happened. They love changing and restricting their API. I’m slowly moving away from Tuya products.
Mama always said “you get what you pay for”; this is a perfect scenario
It’s not completely beyond hope that Tuya might make adjustments to fix the problem. They did fix the issue with color not setting correctly for color bulbs via the api used by HA. That problem happened at the same time as the rate limit change. They also just said that they have solved their cost dispute with IFTTT and expect to have IFTTT service back up by the end of June.
Yeah, i saw that “resolve with IFTTT” thing… basically they bullied them into a much lower cost point, citing their “massive influence” in the market — But thats not my business. IFTTT isn’t a solution to this either though; although, it may allow a bit more requests and lead to slightly faster state responses. But ultimately now we have to add another wheel into the gearbox for the most basic of functionalities. The state of my hallway light will circle the globe 5 times before it sets to “off”… useless and inefficient.
The color issue wasn’t one they added to save on resources; it was a problem. The rate limit was purposely implemented to slow down our requests to save their servers being bashed to death by some people here using tuya.force_update @ 1sec intervals 24/7. They have zero incentive to open up the rate limits again; especially when their apps take priority. With their apps they have complete control and can collect the use-data they want.
But hey, who knows… but I’m not betting on it. Ive already replaced 80% of my bulbs and switches, and found workarounds to manage my tuya curtains and shades on my windows. IKEA Tradfri color bulbs work with Hue/Hass and cost $20. They work flawlessly through the hue bridge.
Does smart life have this same issue? Is is the same API servers?
It’s more of an issue with what medium you’re using to control your devices. If your devices go through the SmartLife/Tuya app (or Tuya HA intergration) then you’ll have this issue. But if your devices are controlled locally, or through another medium (I’d assume SmartLife included) it should be fine.
Hello. I’ve also had a problem with my Tuya devices for about a week. No matter which app I use, the Tuya devices work without problems with the app. In HA, the Tuya devices are sometimes shown as unreachable, or sometimes with an incorrect status. When HA is restarted, other devices are suddenly accessible and others are not, so logic remains recognizable at all. In my “Google Home” app, the status of a device is not changed when I do this via the Tuya app. If I switch the device on or off by voice there is no problem … I suspect that Tuya has changed something serious in the firmware !!! Hopefully these are not America’s sanctions against China, see “Huawei”!?!