Przeglądaj źródła

Docs: iot.tuya.com API Explorer has been reorganised.

Change references to API functions to reflect the new locations.
The old function to get a single device's information that worked for
getting product id and local key seems no longer available, but the
bulk function is available.  Both that and the function for listing dp
ids have gotten new names in the API Explorer and been shuffled around
the heirarchy.  Overall the new heirarchy is an improvement, with less
duplication and no confusingly similar names.

Discussion #823, thanks to @longavailable for the heads up.
Jason Rumney 2 lat temu
rodzic
commit
f5729829ed
2 zmienionych plików z 10 dodań i 12 usunięć
  1. 6 8
      .github/ISSUE_TEMPLATE/new-device.md
  2. 4 4
      README.md

+ 6 - 8
.github/ISSUE_TEMPLATE/new-device.md

@@ -53,9 +53,8 @@ Please paste logs here
 
 <!--
 If you have an iot.tuya.com account, please go to "Cloud" -> "API
-Explorer".  Under "Smart Home Device System"/"Device Control", select
-the last "Get Device Specification Attribute" function, check the
-server is set correctly, and enter your device ID.
+Explorer".  Under "Device Control", select the "Query Properties"
+function, check the server is set correctly, and enter your device ID.
 -->
 ```
 Please paste the output here.
@@ -85,11 +84,10 @@ values and their meanings for any input strings (enums).
 
 <!--
 If you have access to the IoT portal, please paste just the product_id
-line from API Explorer: General Device Capabilities" / "General
-Devices management" / "Get Device Information".  You will also find
-the local_key in here, please take care not to post that publicly.  If
-you do, then re-pairing the device with the mobile app will refresh
-the local key.
+line from API Explorer: "Devices Management" / "Query Device Details in Bulk".
+You will also find the local_key in here, please take care not to post that
+publicly.  If you do, then re-pairing the device with the mobile app will
+refresh the local key.
 
 Although this information is optional and not required, it will be
 used in future to identify matching devices.

+ 4 - 4
README.md

@@ -52,7 +52,7 @@ configuration for it in the following locations:
 
 1. When attempting to add the device, if it is not supported, you will either get a message saying the device cannot be recognised at all, or you will be offered a list of devices (maybe a list of length 1) that are partial matches, often simple switch is among them.  You can cancel the process at this point, and look in the Home Assistant log - there should be a message there containing the current data points (dps) returned by the device.
 
-2. If you have signed up for iot.tuya.com to get your local key, you should also have access to the API Explorer under "Cloud".  One of the functions under the "Smart Home Device System" / "Device Control" section - the last "Get Device Specification Attribute" function listed, returns the dp_id in addition to range information that is needed for integer and enum data types.
+2. If you have signed up for 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 Properties", which returns the dp_id in addition to range information that is needed for integer and enum data types.
 
 3. By following the method described at the link below, you can find information for all the data points supported by your device, including those not listed by the API explorer method above and those that are only returned under specific conditions. Ignore the requirement for a Tuya Zigbee gateway, that is for Zigbee devices, and this integration does not currently support devices connected via a gateway, but the non-Zigbee/gateway specific parts of the procedure apply also to WiFi devices.
 
@@ -332,9 +332,9 @@ If you don't see them, check your server is set correctly at the top
 of the page.  Make a note of the Device IDs for all your devices, then
 select Cloud on the side bar again and go to the API Explorer.
 
-Under General Device Capabilities / General Devices Management, select the
-"Get Device Information" function, and enter your Device ID.  In the results
-you should see your local_key.
+Under "Devices Management", select the "Query Device Details in Bulk"
+function, and enter your Device IDs, separated by commas.
+In the results you should see your local_key.
 
 The IP address you should be able to get from your router.  Using a
 command line Tuya client like tuyaapi/cli or