I’ve hit a practical wall with my Hubitat → Tuya Cloud integration project: Hubitat-Tuya-Cloud-Bridge.
The Hubitat app can authenticate successfully and obtain a Tuya token, so the credentials, endpoint and signing logic is working.
The failure happens after authentication, when trying to access Tuya devices or scenes. Tuya returns: No permissions. Your subscription to cloud development plan has expired.
The confusing part is that the project still shows several authorised services, including IoT Core and Smart Home Basic Service, while the scene-related service is marked as deprecated.
So the issue appears to be Tuya’s cloud entitlement model rather than the integration code itself. Has anyone found a practical workaround for this, other than creating a new Tuya account or a fresh Tuya project?
In the Tuya Developer Platform, the project has several services authorised, including IoT Core, Smart Home Basic Service, Data Dashboard Service and the now deprecated Smart Home Scene Linkage service.
This used to be a free service, but I cant see any way to reactivate it, even via a paid upgrade;
What I really like about the HA Tuya integration is that it requires no development account. You simply enter the code found in your Tuya app for your personal Tuya account settings and you are done.
As such, I use HA, the Tuya Integration, and HADB to bring my Tuya Iot Devices into Hubitat. I wish the Hubitat Tuya integration was based on personal accounts and the code like the HA integration, I don’t see why that isn’t doable.
IIRC, HA has 2 (well, at least 2, but 2 main ones ) versions of “local (wifi) tuya” solutions, and IIRC yet again, both are even named similarly…
But I thought one was now considered notably better than the other – for any future readers of this thread who may be interested in exploring an HA-integration option, can you please remind us all what that go-to local-tuya integration is (and perhaps which one(s) to avoid)?
I don’t know if it’s the “official” (non-official) go-to “LocalTuya”, but this is the one that works for me because my few remaining cloud Tuya devices go through a gateway and this is the only one that seems to pick them up correctly.
As far as I remember, between signing up years ago and a few months ago, the features required from Smart Home Scene Linkage were moved to IoT Core and/or Smart Home Basic Services and made free.
The setup for Tuya Cloud is definitely a pain in the I set it up years ago, and then had to make changes when reintegrating more recently. It was a huge balance between following directions EXACTLY, and ignoring the large bits that really were not necessary.
I just found out that Tuya has libraries of IR codes. My problem is that my Zigbee devices can't be added to the Tuya account because I don't have I have bridge, and not planning on getting one. I used the device ID of another IR blaster in my Tuya account and eventually figured out that there are 61 possible remotes available for Haier TVs. Yeah, no. I'm just going to get a $6 replacement remote from Amazon and learn the few codes I haven't worked out yet.
So, once you get the integration working, you'll have access to libraries of IR codes for your Wifi IR blaster, by adding a $0 non-expiring "subscription" to IR Control Hub Open Service.
I did a full test last night again, so I blew away the existing Tuya project and started from scratch. This time I added what looked like the right Cloud API entitlements from the Tuya cloud side.
I then managed to bridge my Smart Life app back into the project. From the Tuya portal I could see my devices , inspect permissions, and change access settings. So the account linking side appeared to be working.
From the Groovy code in Hubitat, I could also successfully reach Tuya, authenticate, and acquire a token. So the basic integration path works.
The problem was that every useful API call still came back with the same permission / entitlement failure, saying I did not have access to the required API services.
After digging further, it looks like Tuya may have deprecated or withdrawn some of those API entitlements for new individual hobbyist developers. Apparently they have kept access working for existing users who already had those API services enabled, but new users/projects can no longer get access to the same APIs.
It may simply be that the required cloud API access is no longer available to new individual users in the way older integrations expected.
At this point, rather than spending more time fighting Tuya’s cloud entitlement model, I am going to keep using SmartThings as the integration layer for now and bridge the required controls back into Hubitat that way. It is not as clean as a direct Hubitat-to-Tuya integration, but at least it works.
) versions of “local (wifi) tuya” solutions, and IIRC yet again, both are even named similarly…
I set it up years ago, and then had to make changes when reintegrating more recently. It was a huge balance between following directions EXACTLY, and ignoring the large bits that really were not necessary.