Dispatch Command to Devices in Project - FlightHub 2 OpenAPI V2.0 (On-Premises)

Send operation commands to devices within the project through the project-dimension command channel. device_cmd_method determines the command type, and the device_cmd_data field structure varies with the method value. After successful dispatch, the command batch ID (bid) is returned for subsequent polling of progress and results. Differences from the organization-level command channel ("Send Custom Commands to Organization Devices (Universal cmds Channel) [Develop Query-type as Interface, Retain Config-type]" interface):

The path is anchored to the project, and the server will verify "whether the device belongs to the project";

Authentication differences: Except for fill light commands (supplement_light_open / supplement_light_close), other commands require project administrator permissions;

Commands such as one-click calibration (rtk_calibration) are transparently passed after verification. device_cmd_method common value quick reference:

supplement_light_open / supplement_light_close (turn on/off fill light): device_cmd_data passes {}, only requires project member permissions;

rtk_calibration (RTK one-click calibration): device_cmd_data is defined by the model SDK documentation, requires project administrator;

ptz_control (gimbal control): device_cmd_data is defined by the model SDK documentation (target angle/speed, etc.), requires project administrator;

device_reboot (device reboot) / cover_open / cover_close (dock cover open/close) / drone_open / drone_close (drone power on/off): {}, requires project administrator;

Other methods: determined by the device thing model, requires project administrator. Refer to the model SDK documentation for the complete method list.

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

Responses

🟢200

application/json

Success

Bodyapplication/json

Example

{
    "code": 0,
    "message": "OK",
    "data": {
        "bid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
        "tid": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy",
        "timestamp": 1717555200000,
        "output": {}
    }
}

🟠400

🔴500