location of getting local_key has changed #823
Replies: 5 comments 5 replies
-
|
Thanks for the heads up. They seem to have rearranged and relabeled everything, and removed duplicates that were everywhere so now there is only one of each call. A bit strange that they have removed the call to get a single device's details, but the bulk one works with a single device id as input. The other useful one is now under "Device Control" / "Query Properties", which is easier to find now, because the name is not confusingly similar to half a dozen other functions. |
Beta Was this translation helpful? Give feedback.
-
|
Don't know when it changed again...but local keys are no longer displayed for devices other than gateways (it just shows local_key: "" for results). A post from Tuya says it is to protect users since this local key is a key to hackers as well (I guess if you are handing out your local keys to anyone that wants to see them??). Anyway, for the moment...Tuya IoT website is no longer a viable option for acquiring local keys for all your devices now (just gateways). If this changes yet again, please someone update this thread accordingly. |
Beta Was this translation helpful? Give feedback.
-
|
I just checked today... website showing my device local keys just fine. Checked multiple different devices. |
Beta Was this translation helpful? Give feedback.
-
|
Saw your reply...I went directly to Query Device Details (on IoT Tuya) and this was the response I get for one of my humidity & temperature sensors: "ip": "", So as you can see, no local_key for me. If I put in any of my gateways though, the local_key will be filled in (but it won't be for any sub device). So why you are able to get this information for your sub devices when I don't (and from many postings I've seen, neither do most other people) I'm both clueless and curious. Is there possibly a service you are subscribed to that I am not and this service is able to provide the sub device's local_key? In the end two things solved my problem. The first was to install Tuya CLI on a local Linux box and then run The second was the installation of a forked LocalTuya integration https://xzetsubou.github.io/hass-localtuya/ that is able to get the local_keys for you when you go to install a sub device. It also automatically adds the entities. So I've mostly been using that integration since. |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps it's because all of my devices are individual WiFi devices and don't use hubs/gateways. |
Beta Was this translation helpful? Give feedback.
-
|
Well that could be a possibility. I don't have any Tuya WiFi devices currently connected (only KASA WiFi) so I can't confirm this. If true, I would assume then that this issue is specific to ZigBee sub devices only (regardless of manufacturer since I recently added a ThirdReality motion sensor to my Tuya gateway and same thing, no local_key shown for it). |
Beta Was this translation helpful? Give feedback.
-
|
Zigbee devices use standard zigbee protocols between the device and the hub rather than tuya(s own protocol, so do not have individual local keys. For the Wifi communication, the hub's local_key should be used. |
Beta Was this translation helpful? Give feedback.
-
Does not seem working anymore - says my dev account is suspended (I used it once 11 months ago) and now they want money. |
Beta Was this translation helpful? Give feedback.
-
|
You can extend your original trial every 6 months. |
Beta Was this translation helpful? Give feedback.
-
|
I'm in this state too. Is that the 'IoT Core' subscription? Mine expired in May 2023 so hopefully they'll let me renew. I was able to get local keys for my two devices via the HA core Tuya integration but not the local key for the bluetooth wifi gateway hub that I need to get access to the second device. Update: Got it renewed and the web site gave me the same key for the gateway that the HA core Tuya integration claimed was for the water timer. And a different one for the water timer. Tried both to add the sub-device to the integration and just got: Ah, I need the node_id for the sub-device which I haven't been able to get as tinytuya isn't detecting any of the devices when it gets to the local device polling step. Ah I forgot that wsl isn't really on my main network. Installed tinytuya on my home assistant server and was able to get the devices.json list but it turns out node_id == uuid and I'd already tried that as the sub device id. But I'm seeing that this integration can't connect to my wifi irrigation device either with the same 901 error where localtuya can. ...except I tried once more to add the sub-device and this time it worked! 2024-05-04 02:18:46.257 DEBUG (SyncWorker_2) [custom_components.tuya_local.device] Test refreshed device state: {"dps": {"1": false, "2": false, "17": 600, "18": 600, "42": 0, "43": false, "45": "cancel", "47": "3", "53": 0, "101": 2, "102": 2, "103": 600, "104": 600, "105": "idle", "106": "idle"}, "cid": "8c63534780ffa00f", "device": "Non-JSON: (Device( 'eb080db33d218a98f9mlrg', address=None, local_key='', dev_type='default', connection_timeout=5, version=3.4, persist=False, cid='8c63534780ffa00f', parent='eb080db33d218a98f9mlrg', children={} ))"} Still can't get the 8 zone irrigation controller to add to this integration instead of localtuya - maybe I need to remove it from that first? Well that seemed to help - the initial connection attempt worked and it got detected as an SH07 controller and added 8 valves and 8 disabled values under configuration. I tried to enable one of those to see what it did and that was probably the cause of runtime errors: 2024-05-04 10:03:08.417 DEBUG (MainThread) [custom_components.tuya_local] Unloading entry for device: 24142854d8bfc0c9dcd0 Tried deleting the device and re-adding it but now I'm back to 901 errors. So close! |
Beta Was this translation helpful? Give feedback.
-
The layout of API Explorer on Tuya IoT Platform has changed. There is no
Get Device Informationas described in https://github.com/make-all/tuya-local#finding-your-device-id-and-local-key any more.Current path is
Devices Management→Query Device Details in Bulk. Type your device_id(s) and pressSubmit Requestbutton.Beta Was this translation helpful? Give feedback.
All reactions