Skip to content

Deliver to devices

Delivery is an end-to-end platform operation, not an isolated flash button. SenHub Web or SenCLI requests an outcome from the shared platform service. The service creates one immutable DeviceOperationPlan; an eligible local executor performs the hardware-facing actions and reports evidence for platform verification.

Choose an executor

For a local hardware operation, SenHub Web can provide a browser-local executor and SenCLI can provide a terminal-local executor. This is one role within each product, not the definition of the whole product. Both implementations execute the same plan contract and do not own separate delivery business rules.

Delivery path

  1. Register the device and associate it with the intended project.
  2. Confirm the selected SenCore release, component-definition revision, Application, and build artifact.
  3. Request the delivery intent through SenHub Web or SenCLI.
  4. Execute the returned plan with Web or SenCLI.
  5. Return operation events and reported device facts to the shared platform service.
  6. Treat the operation as successful only after final verification.

Install, flash, OTA, Application, Config, License, and Secrets are related operation intents. Their exact actions and prerequisites are defined in the Device Operation Reference.

Was this page helpful?

A cross-hardware capability platform for intelligent devices.