Operate devices

Device operations keep user intent, local execution, and verification connected. SenHub owns the durable operation record; a local executor owns only the capabilities required to interact with the attached device.

Start with the Device Operation model to understand intent, planning, step execution, events, reported facts, and terminal status. Use Troubleshooting when a plan cannot be created, an executor lacks a required capability, a step fails, or the device facts do not match the expected outcome.

Operational documentation is organized by outcome:

• install or replace firmware;
• apply an Application or configuration;
• provision licenses and protected values;
• perform an OTA update;
• inspect progress, retry policy, cancellation, and recovery;
• verify the device identity and resulting state.

The Device Operation Reference defines the exact outcomes and errors shared by SenHub, SenHub Web, and SenCLI.