state array can contain multiple {desired: {...}} groups; server executes serially in array order (devices do not support concurrent commands; cloud concurrency mostly fails); if previous desired fails, interrupts subsequent; not an atomic transaction. Authentication: caller must have organization-level access permission for devices in organization; for some sensitive attributes (e.g. bay forced cover open, etc.), must also currently hold control authority for the device (returns non-zero code without control authority; frontend guides user to preempt control authority first). This is the key difference from "Update Project Device Shadow Configuration" API (project level has no control authority check, but triggers flight record notification). Parameter Values: full attribute key list and value range for each attribute per corresponding model SDK documentation; this API is only the configuration dispatch channel; parameter value validity is validated by device side per model thing model.{
"device_sn": "3ABDQ12345678",
"state": [
{
"desired": {
"night_lights_state": 1
}
}
]
}curl --location '/openapi/v2.0/manage/api/v1/organizations//manage-devices/shadows' \
--header 'x-user-token;' \
--header 'x-user-token;' \
--header 'X-Request-Id;' \
--header 'X-Request-Id;' \
--header 'X-Project-Uuid;' \
--header 'Content-Type: application/json' \
--data '{
"device_sn": "3ABDQ12345678",
"state": [
{
"desired": {
"night_lights_state": 1
}
}
]
}'{
"code": 0,
"message": "OK",
"data": null
}