Command dispatch
Commands flow the opposite direction to telemetry: from a human (or an automation) down to a specific device. Because devices are intermittently connected, dispatch is store-and-forward with priority and delivery guarantees rather than fire-and-forget.
Devices are not always online
A command may be issued while the target device is asleep or offline. The Priority Queue holds it until the device reconnects, ordered so safety-critical commands jump ahead of routine ones.
Participants
Command Router
Validates, persists and routes outbound commands.
MQTT Broker
Delivers the command to the device’s session.
Edge Agent
Applies the command and reports the result.
Steps
Issue
An operator issues a command from the dashboard; the Command Router validates it and writes it to the command repository.
Queue by priority
The command is enqueued; safety-critical commands are dispatched ahead of routine configuration changes.
Deliver on connect
When the device has an active session the broker delivers the command to the edge agent.
Acknowledge
The device actuates and the result flows back as a delivery receipt, surfaced
to the operator as applied (or failed).