New device template: mention the log as source for product id.

This will be the easiest location for most users now that it is output there.

.github/ISSUE_TEMPLATE/new-device.yaml

@@ -26,28 +26,28 @@ body:
       render: text
     validations:
       required: true
-  - type: textarea
-    id: data_model
-    attributes:
-      label: DPS information
-      description: |
-        Preferred data is QueryThingsDataModel API result from iot.tuya.com (under Cloud / API Explorer / Device Control)
-        If you do not have access to iot.tuya.com, but have other ways of obtaining dps information, the minimum info required is the numeric dp id, name/description, data type, and for settable dps, the range for numeric values, and the list of possible values for enum values. If you cannot obtain this info, there is no way for us to support you, as only owners of devices have access to the data about them.
-      render: text
-    validations:
-      required: true
   - type: input
     id: productid
     attributes:
       label: Product ID
       description: |
         The product ID or productKey for the device.
-        You can get this from the same iot.tuya.com API functions that provide the local key or from `tinytuya scan` or other tools doing local discovery
+        You can get this from the HA log when using tuya-local 2024.11.0 and later. Otherwise the same iot.tuya.com API functions that provide the local key or from `tinytuya scan` or other tools doing local discovery
   - type: input
     id: productname
     attributes:
       label: Product Name
       description: The product name (usually brand and model name/number)
+  - type: textarea
+    id: data_model
+    attributes:
+      label: DPS information
+      description: |
+        Preferred data is QueryThingsDataModel API result from iot.tuya.com (under Cloud / API Explorer / Device Control)
+        If you do not have access to iot.tuya.com, but have other ways of obtaining dps information, the minimum info required is the numeric dp id, name/description, data type, and for settable dps, the range for numeric values, and the list of possible values for enum values. If you cannot obtain this info, there is no way for us to support you, as only owners of devices have access to the data about them.
+      render: text
+    validations:
+      required: true
   - type: textarea
     id: info
     attributes: