Devices App
Devices are the physical gateways that connect your equipment to the platform. Each device is a cellular industrial gateway installed on an asset, responsible for collecting sensor data from the equipment and transmitting it securely to the cloud in real time.
📖 What Is a Device?
In the platform, a Device (also referred to as a Gateway) is the hardware bridge between a physical asset and the platform. It reads data from the asset's onboard controller — pressure readings, runtime hours, engine status, fault codes, and more — and sends that data to the platform over a secure cellular or network connection.
Each asset has one dedicated gateway. Once a gateway is registered and activated, the asset begins transmitting live telemetry automatically.
Key Terminology
| Term | Meaning |
|---|---|
| Device / Gateway | The cellular industrial gateway installed on the asset |
| Asset / Machine | The equipment the gateway is connected to (e.g., a compressor) |
| Connector | The communication protocol used to interface with the asset's controller (Modbus, Canbus, or BLE) |
| TSN | Telematics Serial Number — the unique identifier linking the gateway to its asset |
| OTA | Over-the-Air update — remotely pushing firmware or configuration changes to a gateway |
🖥️ Devices Dashboard
The Devices landing page presents three real-time summary panels at the top, followed by the full device list.
Summary Panels
📊 Device Statistics — A line chart showing the count of Available vs. Unavailable devices over time. Use this panel to monitor fleet connectivity health at a glance — a sudden drop in available devices may indicate a network or power issue in the field.
🔵 Device Status — A pie chart breaking down the current status distribution of all devices across the four lifecycle stages: Provisioned, Registered, Activated, and Available/Unavailable.
🔌 Device Connector Statistics — A pie chart showing the breakdown of connector protocols in use across all registered devices — Modbus, Canbus, and BLE.
Device List
Below the summary panels, the Device List displays every gateway in the system.
What does each column mean?
| Column | Description |
|---|---|
| Name | Gateway display name |
| Serial Number | Unique hardware serial number of the gateway |
| Model | Gateway hardware model |
| Status | Current lifecycle status — see status definitions below |
| Last Communicated | Timestamp of the most recent data transmission from this gateway |
| Action | Register or configure the device |
Available tools: Search by name or serial number · Toggle between grid and list views · Bulk select with checkboxes
🚦 Device Status Definitions
Every gateway progresses through the following lifecycle stages.
| Status | Color | Meaning |
|---|---|---|
| Provisioned | 🟡 Orange | The gateway has been manufactured and pre-configured. It is powered on and communicating with the platform, but has not yet been registered to an asset. |
| Registered | 🟢 Green | The gateway has been registered by a user, linked to an asset via its Telematics Serial Number, and is ready to transmit data. |
| Activated | 🟢 Green | The associated asset is active and the gateway is transmitting live sensor data. |
| Available | 🟢 Green | The gateway is online and connected. |
| Unavailable | 🟠 Orange | The gateway is offline or not currently reachable. |
💡 A device in Provisioned status is waiting to be registered. If you have installed a new gateway in the field and it is not yet appearing as Registered, it will show here as Provisioned until you complete the registration process.
🔍 Device Detail View
Click any device name in the list to open its detail page. The page is organized into four information panels and a Job Details log.
📋 Device Info
What does each field mean?
| Field | Description |
|---|---|
| Serial Number | Hardware serial number of the gateway unit |
| Telematics # | The TSN linking this gateway to its associated asset |
| Model | Hardware model designation |
| Manufacturer | Gateway hardware manufacturer |
| Firmware Version | Currently installed firmware version on the device |
⚙️ Device Configuration
What does each field mean?
| Field | Description |
|---|---|
| Connection Type | Network protocol in use (e.g., 3G, 4G LTE) |
| IMSI | Identifies the SIM card |
| ICCID | SIM card serial number |
| SIM Provider | Cellular carrier providing connectivity |
| IMEI | Hardware identifier for the cellular module |
🔌 Device Connector Info
What does each field mean?
| Field | Description |
|---|---|
| Status | Current registration status (Provisioned, Registered, Activated) |
| Connector Type | Communication protocol in use — Modbus, Canbus, or BLE |
| Connector Version | Installed version of the connector configuration |
| Availability | Whether the connector is currently available or unavailable |
| Last Connected | Timestamp of the most recent successful connector communication |
📍 Device Location
Displays the last known GPS coordinates and physical location of the gateway, updated with each data transmission. If no location data has been received yet, this panel will show "Not found."
🔧 Job Details
A log of all Over-the-Air (OTA) update jobs that have been dispatched to this gateway.
What does each column mean?
| Column | Description |
|---|---|
| Activity | Description of the job (firmware update, configuration update, etc.) |
| Version | The version being deployed |
| Status | Current job state (pending, in progress, completed, failed) |
| Created At | When the job was initiated |
| Completed At | When the job finished |
📝 Device Registration
Before a gateway can transmit live data, it must be registered and linked to its corresponding asset. Registration is a one-time process performed when a new gateway is deployed in the field.
The Registration Lifecycle
📦 Provisioned
Gateway is powered on and communicating with the platform.
Awaiting registration.
↓
📝 Registered
User registers the gateway using its serial number.
Gateway is linked to an asset via its Telematics Serial Number.
Initial firmware and connector configuration are applied.
↓
✅ Activated
Asset is activated. Gateway begins transmitting live sensor data.
↓
🟢 Available / 🟠 Unavailable
Ongoing connectivity status — updates in real time.
How to Register a Gateway
- Locate the gateway's serial number on the physical unit or in the Device List (where it will appear as Provisioned)
- Click the registration action (➕ icon) on that device's row
- Enter the serial number to confirm the device
- The platform links the gateway to its associated asset using the Telematics Serial Number
- An initial firmware update and default connector configuration are applied automatically
- The device status changes to Registered and begins transmitting data
⚠️ Non-obvious: The gateway must be powered on and connected to a network before registration can complete. A device that cannot reach the platform will not advance past the Provisioned state.
🔌 Connector Types
The connector is the communication protocol the gateway uses to read data from the asset's onboard controller.
| Connector | Protocol | Typical Use |
|---|---|---|
| Modbus | Serial / TCP-IP | Industrial controllers, PLCs, compressors, drives |
| Canbus | CAN 2.0 | Mobile equipment, vehicle-based controllers |
| BLE | Bluetooth Low Energy | Wireless sensors, beacon-based part tracking |
The connector type is configured during registration and can be updated remotely via an OTA configuration update at any time.
📡 Over-the-Air (OTA) Updates
The platform supports two types of remote updates that can be pushed to any registered gateway without requiring physical access to the device.
Firmware Updates
Deploys a new version of the gateway's core software — used to introduce new capabilities, apply security patches, or resolve known issues. Once dispatched, the gateway downloads the new version, applies it, and restarts the necessary services automatically. The updated firmware version is reflected in the Device Info panel after completion.
Connector Configuration Updates
Updates the configuration that controls how the gateway communicates with the asset's controller. Used when sensor parameters change, new data points need to be enabled, or connector settings need to be adjusted for a specific asset model. The new sensor data begins flowing to the platform immediately after the gateway applies the updated configuration.
📌 All OTA job activity is logged in the Job Details section of the device detail page, including the activity description, version deployed, and completion status — providing a full audit trail of every remote update performed on the device.
🔄 Common Workflows
Workflow 1 — Deploying a New Gateway in the Field
- Install the gateway hardware on the asset
- Power the device on — it connects automatically and appears as Provisioned in the Device List
- In the Devices app, locate the device by its serial number
- Click the registration action and complete the registration form
- Confirm the TSN to link the gateway to the correct asset
- The platform pushes the initial firmware and connector configuration automatically
- Device status advances to Registered, then Activated
- Verify live data is flowing via the asset's Sensors tab
✅ Result: The gateway is live, transmitting sensor data, and fully visible in the platform.
Workflow 2 — Pushing a Configuration Update to a Gateway
- Navigate to Devices and open the target device
- Review the current Connector Type and Connector Version in the Device Connector Info panel
- Initiate a configuration update job with the new configuration file
- Monitor the job status in the Job Details section — it will progress from pending to completed
- Once complete, verify the new sensor data is flowing correctly via the asset's Sensors tab
✅ Result: The gateway's connector configuration is updated remotely with no physical access required. The new data points are live immediately.
Workflow 3 — Investigating an Offline Gateway
- In the Device List, identify devices with Unavailable status
- Check the Last Communicated timestamp — how long has the device been offline?
- Open the device detail and review the Device Connector Info panel for the last connected timestamp
- Check the Device Configuration panel to confirm the SIM Provider and Connection Type are as expected
- If the device was recently online, the issue may be a temporary network disruption — monitor for reconnection
- If the device has been offline for an extended period, dispatch a field technician to inspect the hardware and network connection
✅ Best Practices
- 🔑 Register gateways before deploying assets. Completing registration before the asset goes into service ensures live data flows from the first day of operation, with no gap in the telemetry history.
- 📋 Record serial numbers during installation. The gateway serial number is the primary identifier during registration. Capturing it at the time of installation — before the equipment is in a hard-to-reach location — saves time later.
- 🔄 Keep firmware current. Use OTA firmware updates to maintain gateways on the latest version. Outdated firmware can cause connectivity issues or limit the platform's ability to receive new sensor data types.
- 📍 Use device location data to verify field deployments. The Device Location panel confirms that a gateway is physically where it is supposed to be — useful for multi-site deployments.
- 🔌 Match the connector type to the asset's controller. Modbus is the most common for industrial compressors and machinery. Confirm the correct protocol before applying a connector configuration update.
💡 Tips & Shortcuts
| Tip | How |
|---|---|
| Find a specific gateway | Search by gateway name or serial number in the Device List |
| Check fleet connectivity at a glance | The Device Statistics chart shows Available vs. Unavailable counts without opening individual devices |
| Identify unregistered hardware | Filter or scan for devices in Provisioned status — these are installed but not yet registered |
| Track OTA job progress | Open the device detail page and check the Job Details section for real-time job status |
| Verify after a configuration update | Always confirm new sensor data is flowing in the asset's Sensors tab after any connector configuration change |