Run a Fleet Operation

Use this guide to apply a configuration property to a small first stage, review the results, and expand the change to the rest of the selected fleet. An operation records progress for each device and controls when each rollout stage can proceed.

Before You Start

You need a project with devices and permission to manage them. Operations must be enabled on your Nexigon Hub instance and included in your organization’s plan when subscriptions are enforced. The Operations sidebar entry appears only when the feature is available.

Choose a protected configuration property that your devices already read and apply. This example uses com.example.sensor.config; adapt it to your own integration. See Device Configuration to set up one.

Create the Operation

1. Open Operations, select the project, and choose New Operation.

2. Select Config.

3. Choose the target devices using search, status, groups, or a property predicate. Review the target preview.

4. Leave Re-enrollment interval blank to select a fixed snapshot when the operation starts. Set an interval if it should also enroll later matches.

5. Set the rollout stages to 10,100.

6. Enter com.example.sensor.config as the property name and a JSON value your device integration accepts, such as:

   { "sample_rate_hz": 10, "enabled_channels": ["temperature", "humidity"] }

7. Save the operation. It remains a draft until you start it.

The Config template confirms that Nexigon Hub wrote the property. If the operation must also verify that devices applied it, create it with Builder instead. Define the property write followed by a WaitForDeviceProperty step, then configure a stage guard. Define this sequence before creating the operation; saved operation definitions cannot be edited. See step definitions and guards for the fields.

The preview uses current device state. The selector is evaluated again at startup; a preview does not freeze membership.

Start and Review the Canary Stage

Choose Start. Nexigon Hub selects targets and begins the first stage. The target table shows each device’s stage, step, status, and any error.

Before advancing, confirm that devices applied the configuration. Inspect their reported state or check the sensor service through remote access. A successful property write alone does not confirm device-side application.

Advance, Pause, or Cancel

Choose Advance when the frontier stage’s guard passes and you are ready to expand the rollout. Advancing activates the next stage while unfinished work in earlier stages continues.

Choose Pause to stop enrollment and new work while investigating a problem. Devices can still report results for work already received. Choose Start to resume, or Cancel to stop permanently.

Review the final status and target errors after completion. An operation can finish with failed or timed-out targets; completion alone does not establish that every device applied the change.

Run Device Commands

For diagnostics or another command-driven workflow, choose Diagnostics or Builder and use a command name published by your devices.

Enable both features in Nexigon Agent and restart the service:

[commands]
enabled = true
directory = "/etc/nexigon/agent/commands"

[operations]
enabled = true
poll-interval-secs = 60

Commands and operation polling are disabled by default. The polling interval controls how soon an idle device notices work. After receiving work, Nexigon Agent executes it and polls again immediately. Shorter idle intervals increase the load on Nexigon Hub across the fleet.

The command name must match the device’s command manifest. Follow Create a Device Command to add one. DeviceTask steps have no executor in Nexigon Agent; use DeviceCommand for on-device work.

Choose Another Workflow

The editor also provides OTA Command and OTA Property templates for system updates, Builder for structured selectors, stages, guards, and steps, and Custom Operation for a JSON definition.

For automation, use the operation API actions. For the enrollment and staging model, read Fleet Operations.