Add a sensor

This article explains how to add a sensor to BriqSafe, connect it to what it measures, and allow its readings to complete scheduled jobs automatically.

Note

Required role: Engineer

Add a vendor-provisioned sensor

1. Open IoT Devices and select Add a device by DevEUI.
2. Paste, type, or scan the sensor's 16-character identifier.
3. When BriqSafe shows A vendor provisioned this device for you, select that option.
4. Under Where is this device installed?, select one or more available Locations. Enter an optional Device name.
5. Select Claim device.
6. When BriqSafe shows Device claimed — it is not connected yet, select Connect this device.
7. Select Link Device, choose the Asset, Room, or System that the sensor measures, and select Link Device again.

A claimed sensor is not connected until it is linked to an Asset, Area, or System. Until then, its readings do not feed a compliance check.

Register a sensor that is not vendor-provisioned

1. Open IoT Devices and select Add a device by DevEUI.
2. Enter the 16-character identifier. For an unrecognised identifier, complete the registration fields.
3. Select the required Integration, check the pre-filled Device name, and select the required Device Type.
4. Optionally select Assign to a location, then choose the Location and its Asset.
5. Select Add device, or select Add and create another.

If you add the device without selecting an Asset under Assign to a location, the device is registered but not linked to what it measures. Link it from the device page before using its readings for jobs.

Map the sensor to a parameter

Every link automatically matches the device's sensors where possible. Review or add mappings when the device is linked to an Asset.

1. Open the device and select Map in Sensor Mappings.
2. Select Add Sensor Mapping.
3. Under Select sensor, choose a sensor.
4. Under Select parameter, choose the parameter it measures.
5. Select Add Mapping.

If a sensor could match more than one parameter, review Sensor Mapping Results and select Confirm Mappings first. Only mapped sensors feed jobs. Unmapped readings remain available on the device chart. One sensor can be mapped to one parameter.

An Asset, Area, or System link can have only one target. An Asset link shows Sensor Mappings for review; mappings for Area and System links feed their jobs without this review screen.

How automatic job completion works

No action is needed after the sensor is linked and mapped. BriqSafe checks jobs with status To do or In Progress that are due today or earlier in the Location's own day.

• The latest reading fills a matching parameter when it is within the mapping's staleness threshold. This is 24 hours by default.
• When all parameters have a value from a sensor or manual entry, the job becomes Done.
• When only some parameters have a value, the job becomes In Progress.
• When no sensor values are used, the job keeps its current status.

A job that is not due yet is not auto-filled. A reading older than the staleness threshold is skipped. A parameter that no sensor measures, including an optional parameter, remains for manual completion. Automatic filling is disabled for all jobs under a Structure when Automatic Job Execution is switched off.

Check the identifier result

The Add a device by DevEUI field can show different results:

• This device is already registered: select View device.
• This device is registered somewhere else: use Contact support or ask the named vendor to look it up. It cannot be claimed from this field.
• A vendor provisioned this device for you: this device can be claimed.
• Invalid DevEUI format. Must be 16 hex characters.: correct the identifier.
• We could not check this DevEUI: select Try again. A failed check does not mean the identifier is available.

Check a device that has not reported

A registered device that has never transmitted shows Pending and a Waiting for First Data card. Check the gateway, select Verify Device Activation, and select Confirm Integration Settings. The status clears when the first reading arrives.