This API is used to batch configure Scheduler V3 time segment settings for multiple devices asynchronously.The system first validates all request parameters, device serial numbers, and access permissions. The validation is all-or-nothing: if any device is invalid, unauthorized, or any scheduler time segment is invalid, the entire request is rejected and no task is submitted.After validation succeeds, the system accepts the batch request, splits it into individual device tasks, and submits them for asynchronous execution. The API returns immediately with ACCEPTED; it does not wait for all devices to finish. If notifyChannel is none, no completion notification is sent. If notifyChannel is webhook, a webhook notification is sent after all device tasks are completed. Webhook Signature VerificationSteps
1.
Read X-Foxess-Timestamp, X-Foxess-Nonce, and X-Foxess-Signature.
2.
Reject the request if any of these headers are missing.
3.
Optionally reject the request if the timestamp is too old, for example older than 1 Hour.
4.
Build the string to sign: timestamp + "\n" + nonce + "\n" + rawBody
5.
Calculate HMAC-SHA256 using the webhook secret.
6.
Hex-encode the result in lowercase.
7.
Compare it with the value after sha256= in X-Foxess-Signature.
8.
Use constant-time comparison to avoid timing attacks.
9.
Use X-Foxess-Event-Id for idempotency. If the same event ID is received again, it should not be processed twice.
Supported value ranges and enums for the scheduling parameters (work mode and extra parameters) vary by device model. Query the Get interface first, and set values based on the properties returned in its response (per-field enumList and range).