How does an integration work?

This article explains how integrations are used when registering IoT devices, reviewing unknown devices, linking sensors, and making readings available to scheduled jobs.

Register a device with an integration

Use this process when a device has not been provisioned by a vendor.

1. Open IoT Devices and select Add a device by DevEUI.
2. Enter, paste, or scan the device's 16-character identifier.
3. Enter the required Integration, Device name, and Device Type.
4. Optionally select a Location and its Asset under Assign to a location.
5. Select Add device or Add and create another.

If a vendor provisioned the device, select A vendor provisioned this device for you, choose the installation Locations, optionally enter a Device name, and select Claim device. A claimed device is not connected yet. Select Connect this device and then Link Device to connect it to an Asset, Area, or System.

Review devices that report before registration

An integration can hold unknown devices for review instead of registering or dropping them. A new integration starts with unknown devices queued for approval.

1. Open IoT Devices.
2. Select the Pending action and open Pending Approvals.
3. Review the device's Device EUI, Integration, Detected Type, Messages, First Seen, and Last Seen.
4. To admit the device, select Approve device, enter or confirm the Device Name, select the required Device Type, and select Approve.
5. To prevent the device from being admitted, select Reject device and then Reject.

Use the search field to search by identifier or integration. Select Refresh to reload the list. A device marked Expired has No actions available and cannot be admitted from this list.

Connect a device and map its sensors

Registering or claiming a device does not connect it to the thing it measures. Link the device and map its sensors before readings can fill scheduled jobs.

1. Open the device and select Link Device on the unlinked row.
2. For What do you want to link this device to?, select Asset, Room, or System.
3. Select the target at its Location and select Link Device.
4. For an Asset link, open Sensor Mappings, select Map, and choose Add Sensor Mapping.
5. Select Select sensor, select Select parameter, and select Add Mapping.

Every link automatically maps sensors. Only an Asset link shows Sensor Mappings for review. If a sensor could match more than one parameter, confirm the suggested mappings with Confirm Mappings.

Understand how readings are used

• Only mapped sensors can fill scheduled jobs. Unmapped readings remain visible on the device's readings chart.
• One sensor can be mapped to one parameter. After it is mapped, it is removed from the picker.
• A mapping's staleness threshold is 24 hours by default. A reading older than the threshold is skipped when filling a job.
• If no due job needs a parameter when a reading arrives, the reading is stored and shown on the device's readings chart. No job moves, recommendation is created, or notification is sent.
• A job created after the reading can still use it when the reading is younger than the mapping's staleness threshold.

Provision several devices at once

Use bulk provisioning when a shipment shares one integration, device type, and Location.

1. Open IoT Devices and select Add many.
2. On Add devices in bulk, select the shared Integration, Device Type, and Site.
3. Enter one identifier per line in DevEUIs, or select Or upload a CSV for a single-column file.
4. Review the counts for ready, repeated, and invalid identifiers.
5. Select the provision button, which shows the number of ready devices.

The identifiers are normalised before counting, so the same identifier with and without dashes counts once. A CSV header row is ignored. A file with no valid identifiers is rejected. Bulk provisioning is a Manager action; Engineers can see the form, but their submission is refused.

Important limitations

• A claimed device is not connected until it is linked to an Asset, Area, or System. Until then, its readings do not feed a compliance check.
• A device added without an Asset under Assign to a location is not linked to an Asset.
• A device can be linked to one target only.
• Linking or unlinking a sensor requires device-edit permission. Mapping requires Asset edit access.
• A device registered outside the Locations you can reach cannot be taken over. The panel identifies the organisation holding it or directs you to support.