Set Relay Jog Duration
Use device.operation.execute to set the jog duration for one relay.
Permission
text
device:configRequest
json
{
"type": "request",
"requestId": "req_jog_config_001",
"topic": "device.operation.execute",
"data": {
"deviceId": "abc123456789",
"idempotencyKey": "idem_jog_config_001",
"operation": {
"name": "device.relay.jogConfig.set",
"params": {
"relayIndex": 1,
"durationSec": 2
}
}
}
}| Field | Type | Required | Description |
|---|---|---|---|
relayIndex | integer | Yes | Relay index starting at 1 |
durationSec | integer | Yes | Jog duration from 1 through 8000 seconds |
Reply
json
{
"type": "reply",
"requestId": "req_jog_config_001",
"code": "COMMAND_ACCEPTED",
"message": "Command accepted.",
"data": {
"command": {
"id": "cmd_01JA...",
"deviceId": "abc123456789",
"operation": "device.relay.jogConfig.set",
"status": "SUCCESS",
"params": {
"relayIndex": 1,
"durationSec": 2
},
"result": {
"relayIndex": 1,
"durationSec": 2
},
"createdAt": "2026-07-15T08:30:00Z"
}
}
}params contains the requested values. result is present only when the device confirms the configuration. Jog configuration changes do not produce WebSocket configuration events. Use REST Get Device Configuration when you need the current configuration.
Possible errors include INVALID_REQUEST, AUTH_SCOPE_DENIED, DEVICE_NOT_FOUND, DEVICE_BUSY, DEVICE_OFFLINE, IDEMPOTENCY_CONFLICT, COMMAND_REJECTED, RATE_LIMITED, GATEWAY_UNAVAILABLE, and INTERNAL_ERROR.
