Skip to main content

Intro

Connhex updates devices through campaigns: you simply pick a release, pick the devices and roll it out in waves.

How the update reaches the device is a separate decision, and there are possible three options:

  • Connhex Edge for applications and services.
  • SWUpdate/RAUC for whole system images.
  • plain HTTP poll for custom implementations.

Start at Choosing an update path.

Devices check in on their own schedule, over a connection they opened. Nothing is forwarded in, nothing is pushed at them, and a device that was switched off simply picks up its update at the next check-in. A device also cannot be handed anything outside the maintenance window and the policy you set on the campaign.

Reported and inferred progress​

A device running SWUpdate reports each step it takes, so the monitor follows the update as it happens.

A device that only polls, only says one thing: which version it is running now. Connhex reads the outcome from that, without knowing which step the device was on. Those states are marked inferred wherever they appear.

Before your first rollout, read Firmware and releases for how updates are organized, and Campaigns for how they are delivered.