Skip to content
NereusDocs

Enrol a Sensor

The enrolment flow connects a physical LoRaWAN sensor to your project. After enrolment the sensor appears in the fleet table, is assigned to an asset (or left in the Unassigned pool), and begins reporting telemetry on its next uplink.

Prerequisites

Section titled “Prerequisites”
  • Owner, Admin, or Engineer role in the project
  • The sensor’s DevEUI (a 16‑character hex string printed on the device label, e.g. 70B3D57ED10600A1)
  • The device profile that matches the sensor model — Arad Gladiator for flow meters, Dragino LDDS75 for level/pressure sensors. Profiles are registry-managed, not created in the app, so if your sensor’s model isn’t in the picker it needs to be added to the registry first — see Device profiles.

Steps

Section titled “Steps”

  1. Navigate to the Sensors screen from the project sidebar.

  2. Click the Enrol Device button in the toolbar.

  3. Paste the sensor’s DevEUI into the field. You can paste multiple DevEUIs — one per line or comma‑separated — to enrol several sensors at once.

  4. Select a device profile from the dropdown. The picker shows every profile in the project registry with its vendor, model, and supported metrics. Choosing the right profile is critical: it determines how the sensor’s raw payload bytes are decoded into structured telemetry.

  5. Enter a label (optional). The label is a human‑readable name for the sensor — e.g. “North Basin inlet” or “Pump Station 3”. If you leave it blank, the label auto‑generates from the asset name.

  6. Choose an asset (optional). The asset picker lists every asset in the project. Leave it empty to enrol the sensor into the Unassigned pool — you can assign it later from the sensor detail sheet or the assets screen.

  7. Click Enrol. Each DevEUI is provisioned and the sensor row appears in the fleet table immediately, counted under Awaiting (“no uplink yet”) with a last‑seen of Never. After the first uplink arrives (typically within the device’s cadence interval), the sensor moves to Live and the battery / signal columns populate.

After enrolment

Section titled “After enrolment”

The sensor appears in the fleet table immediately. Click its row to open the sensor detail sheet where you can:

  • View telemetry history as it accumulates (time‑series charts per metric)
  • Check the raw uplink log (payload bytes → decoded values)
  • Edit the label or reassign the sensor to a different asset
  • Monitor battery level and signal strength over time

If the sensor stops reporting for long enough (roughly 6× its cadence), its health chip flips to Offline and the staleness detector raises an offline alert automatically — see alert rules.

Section titled “Related”