A new way of getting deviceId and localKey

Hello, I’ve found out, that an official Smart Life app shows you deviceId. I’ve tested that deviceId with tuya OpenAPI and it works (at least for my smart sockets). This means, that you can get localKey from an OpenAPI /v1.0/devices/{{device_id}}.

I think, that this may be useful to simplify tuyapi setup workflow.

The new setup will consist of three steps:

• after creating app on iot.tuya.com and getting key/secret, you need to link your devices, but instead of doing that with @tuyapi/cli, you should “Link device by Tuya Smart App Account”:
• then you can grab id from an app. From the main screen tap on device you interested in, then tap “edit icon” to get to the screen where you can manage/share/rename device. On that screen there is “Device information” menu option, where you can look up for the deviceId:
• finally request device info from tuya OpenAPI, where you can get localKey value:

[Thunderbird2086]

It’s from postman, a standalone application.

where is this screenshot from?

[kinstray]

Rejigged the earlier comment with some extra stuff I had to do. Thanks to @Moudoux for the info!

I found this method the easiest

Follow this guide first: https://developer.tuya.com/en/docs/iot/open-api/quick-start/quick-start1?id=K95ztz9u9t89n

Make sure you import your devices using ‘Link devices by App account’. Also under ‘API Group’, enable the API’s giving any random reason. I’m not sure which, I just enabled them all. Remember there are 3 pages!

You’ll need your Client ID, Client Secret and Device ID for the plug you need the Local ID for. Those are all in the Tuya portal.

<Mostly> Written by @Moudoux on 23 May, thanks to them for this bit! :

1. Install Postman
2. Download and import the environment and collection in postman
3. Set up the variables according to your Tuya developer profile client_id, device_id (from the app as described in this post) and url (region based, i.e. https://openapi.tuyaeu.com for EU) - Make sure you’ve enabled the API’s (mentioned above) and wait 5 to 10 mins or so for them to take effect!
4. Run the access_token task in collections in postman
5. Run the {{url}}/v1.0/devices/{{device_id}} request to get your local_key

Found this much easier than messing around with SSL certificates on Android devices and Proxy apps!