Configuration

By default, Nexigon Agent loads its configuration from /etc/nexigon/agent.toml. To configure Nexigon Agent, you need to provide the URL to your Nexigon Hub instance as well as a project-specific deployment token. Furthermore, you need to provide a path to a device fingerprint script. The agent will use the output of that script to compute a device-specific fingerprint.

Here is an example:

hub-url = "https://eu.nexigon.cloud"
token = "deployment_UvsBJTcAKWo6LfPXMyDUXA2UvvTjHozDfMT3suY4SosZk2JrgH5JRzCYzX2yPEsRuC"

fingerprint-script = "/usr/libexec/nexigon/nexigon-device-fingerprint"

Device Fingerprints

Device fingerprints are meant to be hardware-specific and never change over the lifetime of a device. If the storage of a device is never replaced and /etc/machine-id is persisted, then you may use the following script:

#!/usr/bin/env bash

set -euo pipefail

cat "/etc/machine-id"

Feature Configuration

Several agent features are optional. Enable only the capabilities you want a device to expose.

To allow Nexigon to run device commands, enable commands and point the agent at a directory of command definition files:

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

To let the agent pick up device-executable operation steps, configure operation polling:

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

Operation polling and commands are both disabled by default. DeviceCommand steps only work when both are enabled and the referenced command exists on the device. The bundled agent does not execute DeviceTask steps.