Skip to content

Enrol Devices

Add devices to N-Hub so they can send and receive data. You can enrol devices one at a time, or upload a CSV to enrol many at once.

Who can enrol devices

Tenant administrators of an enterprise with a configured network server can enrol devices for that enterprise. Users without a tenant-admin role can see the device list but the Enrol Device and Bulk Enrol buttons are hidden — ask your organisation's tenant administrator for access. Devices stay scoped to your own enterprise tree; you can't enrol into another organisation.

Before you start

Have these to hand for each device you want to enrol:

  • DevEUI — the 16-character hex identifier printed on the device or supplied by the manufacturer.
  • Device type — the model you're enrolling. If your device type isn't listed, ask your administrator to add it.
  • Activation keys — these come from the device vendor:
    • OTAA devices need an AppKey (32 hex characters).
    • ABP devices need a DevAddr, a NwkSKey, and an AppSKey.

Key safety

Activation keys are forwarded directly to the network server. They are never stored on this platform and cannot be retrieved after enrolment. Keep your vendor-supplied keys in a secure location — you'll need them again only if the device has to be re-provisioned.

Enrol one device

  1. From the sidebar, open Assets → Devices.
  2. In the top-right of the device list, click Enrol Device.
  3. Choose the device type. The form expands to show the fields required for that type's activation mode (OTAA or ABP).
  4. Fill in the device's DevEUI, a friendly name (something like meter-row-3-north), and the activation fields.
  5. Click Enrol. You'll land on the new device's detail page once the network server confirms creation.

If the network server rejects the device (duplicate DevEUI, malformed key, profile not found), the form returns with the error message inline. No partial state is created — you can fix and resubmit.

Enrol many devices at once

For larger fleets, upload a CSV.

  1. From the sidebar, open Assets → Devices.
  2. In the top-right of the device list, click Bulk Enrol (next to the Enrol Device button).

Prepare the CSV

The CSV format has five columns. Each row enrols one device. Pick the device type by its code (the same code shown on the Device Types page) — the activation mode and the meaning of each key column follow from that.

Column OTAA device type ABP device type
dev_eui required (16 hex) required (16 hex)
dev_addr leave blank required (8 hex)
device_type_code required required
key_1 AppKey (32 hex) NwkSKey (32 hex)
key_2 leave blank AppSKey (32 hex)

Example mixing OTAA and ABP device types:

AABBCCDDEEFF0001,,LS-300-OTAA,AABBCCDDEEFF00112233445566778899,
AABBCCDDEEFF0002,00ABC123,LS-300-ABP,AABBCCDDEEFF00112233445566778899,DDEEFF00112233445566778899AABBCC

The upload page has a Download a template CSV link under the CSV format section if you want a starter file in the correct format.

Limits

  • Maximum file size: 5 MB.
  • DevEUIs longer than 50 characters are rejected.
  • Duplicate DevEUIs within the same file are rejected — you'll see the offending line numbers in the error message.
  • Unknown device_type_code values are rejected.
  • Rows with the wrong activation columns for their device type (e.g. a dev_addr set against an OTAA device type) are rejected.
  • Cellular and NB-IoT device types aren't supported by bulk upload yet — enrol them one at a time for now.

Upload

  1. On the Bulk Enrol Devices page, pick your enterprise from the dropdown.
  2. Choose your CSV file.
  3. Click Upload & Enrol.
  4. You'll land on a status page that updates automatically as the network server processes the import.

Reading the result

The status page shows:

  • State — running, succeeded, partial, or failed.
  • Totals — total rows / succeeded / failed.
  • Per-row table — DevEUI, op type, result, and error message for each line of your CSV.

If any rows failed, click Download failures CSV to get a file containing just the failing rows plus the error message for each. Fix them in your CSV editor, save as a new file, and upload that.

Common per-row errors

  • Cross-tenant DevEUI — the DevEUI you supplied is already registered under a different enterprise. The device exists on the network server but isn't yours; contact your administrator.
  • Invalid key length — keys must be the exact hex length specified above (16 for DevEUI/DevAddr, 32 for AppKey/NwkSKey/ AppSKey). Whitespace and 0x prefixes aren't accepted.
  • Unknown device type — the device_type_code you supplied isn't a recognised device type for your enterprise. Check the Device Types page for the exact code.
  • Device type not provisioned for enrolment — your administrator hasn't yet configured this device type for network-server enrolment. Contact them.

If the status page sits at "running"

Most imports finish within seconds. A few minutes is normal for a large file. If a batch sits at running for more than a few minutes:

  • Keep the page open. It polls the network server on each refresh; closing the page doesn't cancel the import.
  • The polling stops automatically after 30 minutes. A notice appears asking you to refresh later — the import is still happening on the network server side, and revisiting the page will pick up the final result.
  • If a batch sits at running for hours, contact your platform administrator with the batch ID shown on the page.

What happens next

Once a device is enrolled:

  • It appears in your device list scoped to its enterprise.
  • The platform starts accepting telemetry as soon as the device begins transmitting.
  • You can assign it to a site from the device detail page.
  • You can tag and group it alongside other devices.

You don't need to do anything else to receive data — telemetry routing is automatic once the network server has the device.