Glad I switched to tuya local during all this mess. Seems to have been the right decision.
Is the Tuya developer trial yearly, or once it’s done, you have to start paying?
Regardless of that question, they have committed to implementing an official local Tuya at some point.
The trial edition is free to use but expires in 1 month. There is a special 6 months extended period on personal requests.
But check out the whole image of the service:
As you can see, all paid subscriptions expires just in 1 years instead of a month, and the smaller one is enough for 10 000 devices. This is why I wrote that the whole developer console and its possibilities are not for end-users but 3rd party developers/developer companies who want to use Tuya API. This is absolutely correct. There is no problem with it.
The problem is that Home Assistant will never pay for it, and we as end-users also will not. The situation is simply not the one what it have to be.
If Tuya really want to close its users into their services offers just paid method to use their API, Home Assistant as a ‘non-profit organization’ will never pay for it and this is the end of the road.
If Tuya could offer a free solution to directly to Home Assistant, that could save us, but if this is somewhere a counter-interest thingie, then this is really the end of the road (I mean the official/proper road). There are always be hacks, but they are usually not reliable for a long time.
But my trial says it expires May 2022 ?
I did sign up a while back , way before this integration to get my keys for Tuya Local.
Maybe the trial is just needed to hook into Tuya, to link your TuyaSmart or Smartlife App and pull in your devices,. Of note, looking at the HA code, there is definitely a HA specific dev api channel.
If anyone’s 1 month trial is up, can you post if it still works in HA?
Hi guys, the slow response issue of Tuya HA integration is been improved, please check if it’s fixed, thanks!
3 Likes
My first subscription was at 10.06.2021. A sadly simply not remember how long was the trial period of the ‘IoT Core’ service then.
Yesterday, when the tipp was appeared, I made a new resubscription, and the result was a 1 month period. This limit is just for the IoT Core service, all my others is valid for 1 year.
Maybe this is a new restriction or I don’t know, but all people who tried the solution yesterday based on Github info got the same result. (As I wrote there is a 6 months extension but just in case of personal requests. I did it but not got it yet.)
Sadly I don’t know more (yet).
Thanks for the update Oliver. I can confirm all Tuya devices for me (lights, switches, dimmer switches, power sockets) seem to working fine again.
I saw in a few other threads people tried to renew their Tuya developer account subscriptions. I didn’t do anything of that. It just started working fine by itself again.
@tjafbe yes, the slow response issue is not related to the Tuya developer account subscriptions. It’s related to the rapid growth of the Tuya Integration developers, which consumes our server resources fastly and result in the slow response. Thanks for everyone’s support on the Tuya Integration product, we have upgraded the server resources, and the issue should be improved now. Sorry for the inconvenience again.
2 Likes
I believe this is a beautiful use case to demonstrate to importance of HA Analytics and demonstrate to vendors the power of the HA community on the need for proper integrations and reliable service delivery 
Hi Oliver!
Thanks for your fast response, and also for your hard works and efforts.
Independently what you wrote could you please explain me how could help the ‘IoT Core’ resubsription from yesterday ‘morning’ on the problem? There were some people who tried it, included me and the result was fine really. After my resubscription all state reports seemed worked instantly while I wrote more reports before about the problem, how the things gone earlier.
I hope you do not misunderstand me, I totally accept your ‘report’ about the situation but it is really interesting that from yesterday morning there were no more problems, instantly after my resubscription.
Could it be your server side changes at the same time period when every relevant people tried to resubscribe?
Thanks for you answer in advance!
I believe it’s related to the server side changes, and glad that the slow response issue is improved now 
2 Likes
Ok, from my aspect the current result is fine. If the reason of that is ‘your changes’, then it’s fantastic, if the ‘IoT Core’ resubscription, then at least acceptable:) and in this case this is not your fault!
Works way better as we speak, thanks for the ones that put in effort !
Thanks zlinoliver! I’ve just ported over back to tuya integration and seems great so far. As this issue seems to arise from resource exhaustion over at your end, hope there are monitoring mechanisms in place to auto provision as Tuya products increase market share. Else we will face this once again. Cheers.
Unfortunately, it still doesn’t work for me. 
I have restarted HA multiple times since yesterday and there has been no change in behavior of my Tuya devices. There is still massive delay in updating their status. I will keep trying.
Did you try to resubscribe to ‘IoT Core’ Tuya API service? (If not please make a try, I’m just curiouos.)
Since I started my trial a month ago, this is what is says:
I haven’t changed anything.
Do you mean I should cancel my subscription and subscribe again? Thanks.
Wow, that’s much better. Almost instantaneous now. Thanks
This is what me and some other people did yesterday and the problem seemed to be solved from that point. But also this is what generated some bad tone comments as our new subscriptions limit its expiration to 1 month in total, what of course could lead for uncomfortable results.
Anyway I (we) did it, and seemed it solved my (our) problems, but Oliver told that not this was what solve it. I just throw this tip for you, as yesterday it really seemed that this was what solved our problems and my problems are currently really be solved
The choice is yours, but maybe this is really need because of some Tuya API ‘bugs’?!..