What the data for this category looks like
Small home appliance yield rate-related data comes from three main sources: real-time runtime logs of connected smart small home appliances, public tiered electricity rate standards from local power grids, and fixed rate configurations from lease or service contracts. Data is aggregated daily in the early morning to compile full runtime data from the previous day, generating daily report documents for each individual device. Each document includes the device’s unique SN code, total daily runtime, average daily electricity price, basic service fee rate, net daily revenue per device, and audit timestamp. Field units are as follows: runtime in hours, electricity price in yuan per kilowatt-hour, revenue in yuan, and audit timestamps use the ISO 8601 format. The data has fragmented characteristics: daily runtime fluctuations for a single device are wide, and reporting frequencies vary across different devices.
What constraints do these characteristics impose on conversation logs and auditing
The fragmented nature of small home appliance data requires conversation logs to include multi-source data verification logic. Logs must simultaneously record three types of information: device-reported runtime, grid electricity price data, and contract fee rates. This ensures cross-verification of data accuracy during audits. The daily update cycle of daily reports requires the auditing workflow to check data reporting completeness per calendar day. This prevents missing daily reports due to device offline status or failed reporting. The structured multi-field requirement means log storage must be partitioned by device SN code and audit timestamp. This enables retrieval by category or individual device. Additionally, small home appliance deployments typically involve large numbers of devices, leading to higher log generation volume. Reasonable log rolling and storage strategies must be configured to avoid retrieval delays or storage overflow during audits.
How to Set Configurations
| Config Item | Recommended Value | Basis for This Setting |
|---|---|---|
MAX_LOG_RETENTION_DAYS | 30 days | The standard audit cycle for small home appliance daily report data is monthly. Retaining 30 days of logs covers regular audit needs while controlling storage costs |
ENABLE_WORKFLOW_LOG | Enabled | The revenue announcement workflow relies on multi-source data verification. Enabling this setting records input and output for each component, making it easier to troubleshoot data inconsistency issues |
WORKFLOW_LOG_LEVEL | DEBUG | Small home appliance data is fragmented. Detailed logs are required to locate reporting anomalies for individual devices. DEBUG level logs record parameter transfer details between components |
API_LOG_ALLOW_SOURCES | ["api", "plugin", "mcp"] | Supports log recording for three types of sources: user queries, external plugin calls, and MCP service calls. This covers auditing requirements for all announcement scenarios |
LOG_ROTATE_MAX_SIZE | 100 MB | Small home appliance deployments involve large numbers of devices, leading to fast log generation. A 100 MB rolling size balances log query efficiency and storage usage |
AUDIT_ALERT_THRESHOLD | 10 missing devices | Triggers an alert when the number of devices with missing daily logs exceeds this threshold. Adapts to small and medium-sized small home appliance device clusters |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require individual analysis. Testing should be conducted on local samples before finalizing settings.
Three Common Configuration Mistakes
- Phenomenon: No corresponding call record appears in logs when invoking workflow nodes for external plugins or other applications. Cause:
pluginormcphas not been added to the whitelist of theAPI_LOG_ALLOW_SOURCESconfiguration item. - Phenomenon: When viewing logs for MCP services in a workflow, only call status is displayed, with no detailed parameters or return results. Cause: The
WORKFLOW_LOG_LEVELis set to INFO or lower, and DEBUG-level log collection is not enabled. - Phenomenon: Unable to retrieve small home appliance revenue logs for a specified time range in system logs. Cause: The
MAX_LOG_RETENTION_DAYSconfiguration value is smaller than the time span of the log retrieval, or log indexing is not configured by device SN code.
How to Verify Configurations Are Correct
- Call the revenue announcement interface, pass the test device's SN code, and check if the conversation log includes fields such as the device's runtime, electricity price, and revenue amount.
- Trigger a workflow call to an external plugin or MCP service, and check if the workflow log panel records the component's input parameters and return results.
- View the system configuration panel, confirm that the configuration values of
ENABLE_WORKFLOW_LOGandAPI_LOG_ALLOW_SOURCESmatch the preset values. - Simulate a scenario where logs for a single device are missing, and check if the preset audit alert rule is triggered.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.