Device Commands

Send commands to a device: reboot, shut down, run a command the device declares, or recover buffered historical data. Each command returns a reqSeqId; use List a device's command history to follow the result.

📄️Reboot a device

Requests a remote reboot. Side effect: the device goes offline while it restarts and is briefly unreachable before it reconnects. 202 returns a command-result object; then GET commands/results and match the returned reqSeqId in the items to follow the outcome.

📄️Shut down a device

Requests a remote shutdown. Side effect: the device powers off and stays off. It will not respond again until it is manually powered on. 202 returns a command-result object; then GET commands/results and match the returned reqSeqId in the items to follow the outcome.

📄️Run a device command

Run a command declared by the target device. Read its command definitions first with GET capabilities/schema?type=commands. Use the Command's name with each underscore replaced by a dot (for example, set_di becomes set.di) as deviceCommand, and build parameters from the Command's request schema. A command the device does not declare is rejected with 422. Keep the returned reqSeqId and match it in the device's command history (GET commands/results) to follow the outcome. The set.di command in the request example is only an example. It works only on devices that declare it.

📄️Recover buffered device data

Requests manual recovery of cloud data lost while the device was online and still holds it in its local buffer. Issues the edge command report.historical for one device and one time range; the device re-uploads the whole range and the cloud overwrites it (full replace, no gap detection). startedAt must be strictly before endedAt and no older than the 7-day recovery horizon (else 422). Runs asynchronously. 202 returns a command-result object; then GET commands/results and match the returned reqSeqId in the items to follow pending -> ack -> progress -> result.

📄️List device command results

Paged command history (newest first). Each item is the WEDA command-result envelope. data.status is the result flag (0 = success/received, 1 = failed, with data.error). data.phase is the device-interaction stage, one of pending (dispatched, awaiting ack), ack (received+validated at device), progress (in-progress report for long-running commands), result (done, reported); reboot/shutdown go pending->result, others pending->ack->(progress)->result. Poll here after issuing a command, matching the reqSeqId returned by the issue call against the items.