Operator commands should not be treated like replaceable telemetry. A responsive button is only one part of the system; the client needs to distinguish submitted, accepted, executing, completed, and rejected states.
Model the command lifecycle
Assign a unique command ID and expose explicit lifecycle states. Do not show success merely because a request was written to a socket.
Keep commands separate from telemetry
Do not queue critical commands behind camera metadata or diagnostics. Use a dedicated path with authentication, authorization, timeouts, and rate limits.
Prevent duplicate actions
Disable or debounce controls while pending where appropriate, but make the server idempotent using command IDs.
Show uncertainty honestly
If the connection drops after submission, show outcome unknown until reconciled.…