Skip to content
IntellobotsTechnologies

Use · How-to

Send commands to devices

Commands are stored, delivered, retried and acknowledged, so you always know whether a device did what you asked.

Updated 11 Nov 20261 min read

All ThingsX IoT Core pages

A command is a message to one device that IoT Core keeps until it is delivered and acknowledged, unlike a fire-and-forget publish.

  1. 1Queuedstored as soon as you send it
  2. 2Sentdelivered when the device is connected
  3. 3Acked or failedthe device replies with a status
  4. 4Expirednot delivered within its lifetime (default 1 day)

Send one

From the device's Commands tab, or from your application:

curl -X POST https://<your-endpoint>/v1/things/esl-hyd-01-a1-001/commands \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"name": "show-page", "payload": {"page": 2}}'
The Commands tab: send a payload and see every command's status
Commands: history with status for each command

How devices receive and answer

Device kindReceives onAnswers with
Wi-Fi / IoTtic/things/<name>/commands/<id>{"status":"ok"} on …/commands/<id>/response
Child behind a gatewayThe gateway's downlink topic, with command_idAny gateway uplink with command_id and status
LoRaWANThe next receive window, with fPortThe network's delivery confirmation

Good practice

  • Make commands safe to repeat (idempotent): a retry must not do the work twice.
  • Include what the device needs to check before acting, for example a firmware version.
  • Watch Commands waiting on the Overview: a growing number usually means devices are offline.