Firmware operations

Prepare a safe release

DAT
Release operatorPrivate portal
1UploadAdd signed binary
2ValidateSafety checks
3PublishCreate release
4Roll outNotify devices
STEP 1

Firmware binary

SIGNED IMAGE REQUIRED
↑
Drop app_update.bin hereor click to choose a signed MCUboot image
!The portal never deploys on upload. The binary must pass validation, be published, and receive separate rollout approval.
STEP 2

Release details

ALL FIELDS CHECKED
Declared targetNot suppliedUsed in MQTT command
Signed MCUboot headerUpload to detectRead from binary
SAFETY GATE

Pre-flight validation

NOT RUN
Waiting for release details

Add the firmware file and complete the form, then run the safety checks.

Nothing can be published yetThe final proceed option appears only after every check passes.
ROLLOUT PREVIEW

Eligible devices

NO COMMANDS SENT YET
Reported fleet versions → Target version

After the release is published, the portal finds compatible devices by their reported application version and prepares one retained MQTT command per IMEI.

—Eligible
—Online now
—Awaiting check-in
—Incompatible
Publishing records the immutable release. Device rollout remains a separate final approval.