Configure Report Frequency Limit Rules

This topic describes how to configure report frequency limit rules. After a device restarts, the device limits data point (DP) reports per unit time according to the configured rules.

Prerequisites

• You have created at least one smart product on the Tuya Developer Platform. For more information, see Create Products.
• You have at least one activated device for the product.

Procedure

Entry 1

Select the target product and go to Product Development > Product Configuration > Other Configurations > Report Frequency Limit. Click Settings.

You can set the global report frequency limit to restrict total DP reports per unit time. The report frequency can be set in times/minute, times/hour, or times/day. If you leave the rule empty, reports for this DP are not limited.

You can set the custom function frequency limit to restrict the report frequency of custom functions based on their DP IDs. Select a frequency unit: times/minute, times/hour, or times/day. If you leave the rule empty, reports for this DP are not limited.

If both global and custom report frequency limits are configured, reports are restricted when either the global limit or the DP-specific limit is reached.

Entry 2

Select the target product and go to Product Development > Function Definition > Product Functions. Click Add Function to create a custom function, or click Edit to modify an existing custom function and configure its report frequency limit.

In the Create Custom Function window, you can set the custom function frequency limit to restrict the report frequency of custom functions based on their DP IDs. Select a frequency unit: times/minute, times/hour, or times/day. If you leave the rule empty, reports for this DP are not limited.

After you delete a custom function, the associated custom function frequency limit rule is also deleted.

SDK version requirements

• Non-IPC devices: SDK baseline version 2.3.0 or later
• IPC devices: SDK version 5.0 or later

Otherwise, the report frequency limit configuration does not take effect.

When the configuration takes effect

After configuration, no manual refresh is required. The configuration takes effect automatically when either of the following conditions is met:

• The device is paired again.
• The system automatically updates and applies the rule after 24 hours.

Troubleshooting

If the frequency limit configuration does not take effect, check the following:

• Device restart resets counter:
  If the device restarts during testing, the report counter resets, which can cause unusual short-term frequency limiting.

• Query reports are not counted:
  Query-triggered reports from the device are not included in the frequency limit statistics and do not trigger frequency limiting.

• Counter reset mechanism:
  The device resets the report counter when the cloud issues new frequency limit rules, or when the device automatically pulls the latest rules every 24 hours. Counting then starts again.