This works for me for the Smart Life app, I have only 1 device as a test, so all good. BUT historically, I installed all my devices on the Tuya app. As the Tuya app is not discussed in the video ,but only the Smart Life app, I can not reach my devices to get the Local Keys. Has anyone a good advice how I get to see my Tuya installed devices in the Smartlife app? OR Has anyone a trick to get the Tuya app installed in BS tweaker and Bluestack?
thanks
nope, this one doesn’t help
you go to Cloud → Cloud services. Click on Iot Basics, there going to be Iot Core. Its gonna say that “there are problems but its working” you click on Subscribe to resource pack. Got through the process, it will tell you that you already have this service and then you gonna see the button to Extend. Then you fill out the form and wait for “manual review” for extension approval.
Thanks, it works.
I can extend the cloud service for free and get the local key
So I had Local Tuya working with many devices. I got new devices and I see these new devices are reporting there is no local_key.
I have taken your advice and refreshed my trial to IoT Core. Still not able to pull a local_key.
Could it be this device just has no local key? The local tuya integration forces me to input the local_key value.
local_key seems to be empty, sorry I haven’t seen this happen before so I can’t help. Maybe someone else has more experience with this issue.
it seems this isnt a new issue either. Looking like local tuya is dead, they killed it.
{
“code”: 40001900,
“msg”: “No space permission”,
“success”: false,
“t”: 1719246162375,
“tid”: “fb5c44de324511ef9e3b1acebe103cd3”
}
And what is this in relation to?
This is a public forum and not a help desk.
If the Tuya links from my original post don’t work anymore, then please state that in your post and maybe look for the working ones and post that here to help others.
f you have signed up for [iot.tuya.com] (https://iot.tuya.com/) to get your local key, you should also have access to the API Explorer under “Cloud”. Under “Device Control” there is a function called “Query Device Details in Bulk”. Enter the device ID
For anyone struggling with permissions/expired trial, the solution is to simply use API explorer from “smart home basic service”, NOT iot core. You don’t need to extend IoT core trial. The select field for that is at the top left of the page in API explorer. You can then get device details from smart home device management section.
Nope, you can’t, just tried
Which video is this (setting up “local” smart life)?
Link please
Thanks
no, this is not working anymore - you need a payed cloud subscription
I have been able to access my localkeys without a paid subscription - I had signed up for the free IoT Core trial in October whic had expired, but I was able to apply for a free extension from the Cloud->Cloud Services page by clicking on “View Details” of my expired trial and giving a very basic “I want to test home integration” reason for the request
Yes, this method worked for me, thanks a lot!!!
I do confirm, that is indeed working to get the local key!! THanks a lot
Just confirming none of the above solutions work with expired trial still, however was able to extend my trial for 6 months pretty quickly.
Submitted late evening, trial was extended within about 10 mins which was surprising.
Cloud->Cloud Services->IoT Core (View Details)->IoT Core (Extend Trial)
I just submitted a request for under 50 devices, stating testing integration with Home Assistant.
You saved me after hours of searching and trying everything — even dumped the entire Android data and searched through it…
Thanks, man!! 
Yeh the Tuya Developer Platform can be a bit of a nightmare to navigate.
The old app v3.6.1 method actually still does work as I later found out, but I was lead astray by the characters Tuya uses now for local keys.
Previously it’s always been limited to hex characters but seems now its all characters including special.
I had a couple of devices added recently so like I normally do, I got the prefs xml from v3.6.1 on an old rooted phone I kept for this sort of thing.
The old app said it didn’t support the new devices but still listed them and had the details in the xml. However looking at it I thought the local key was encrypted because of all the special characters which made me try using the API, but after finally getting that to work found that it was the actual key all along.
Oh well, live and learn.