Devices
Devices are the primary IoT entities in ThingsBoard. They represent physical or virtual things — sensors, controllers, gateways, emulators — that publish telemetry, report attributes, and respond to RPC commands.
Managing Devices
Section titled “Managing Devices”Create a Device
Section titled “Create a Device”- Navigate to Entities → Devices.
- Click + and select Add new device.
- Enter a Name (must be unique within the tenant).
- Optionally set a Device profile, Label, or Description.
- If this device will proxy data for other devices, enable Is gateway (see Gateway Devices).
- Click Add.
A connectivity check dialog opens automatically — use it to verify the connection or close it to continue later.
Edit a Device
Section titled “Edit a Device”- Click the pencil icon next to the device in the list.
- Update the name, profile, label, firmware, or software version.
- Click Apply changes.
Delete a Device
Section titled “Delete a Device”Click the trash icon next to the device and confirm, or open the device details page and click Delete device.
Manage Credentials
Section titled “Manage Credentials”- Open the device details page.
- Click Manage credentials.
- Select the credential type and fill in the required fields.
- Click Save.
Gateway Devices
Section titled “Gateway Devices”A gateway device proxies data for multiple downstream devices over a single connection using the Gateway API. Enable gateway mode when creating or editing a device.
| Setting | Description |
|---|---|
| Is gateway | Grants the device access to the gateway topic namespace for proxying downstream devices. |
| Overwrite activity time | When enabled, the gateway’s own connection activity keeps connected downstream devices in Active state. Useful when downstream devices are connected through the gateway but not actively sending telemetry — RPC commands and shared attribute updates can still be delivered to them. |
To enable gateway mode, toggle Is gateway in the device creation form (step 4 of Create a Device) or in the device edit form.
Device Details
Section titled “Device Details”Opening a device reveals a details panel with the following tabs:
| Tab | Contents |
|---|---|
| Attributes | Client, server, and shared key-value pairs (serial number, firmware version, thresholds) |
| Latest Telemetry | Real-time sensor readings; supports manual entry and deletion by time range |
| Calculated Fields | Values computed from telemetry or attributes using formulas |
| Alarm Rules | Conditions, thresholds, and triggers configured for alarm generation |
| Alarms | Active and historical alarms for this device |
| Events | Lifecycle events, logs, warnings, and errors |
| Relations | Directed connections to other entities (assets, dashboards, rule chains) |
| Audit Logs | History of user actions: creation, updates, deletions |
| Version Control | Git-based export and restore for backup and collaboration |
Common Operations
Section titled “Common Operations”Check Connectivity
Section titled “Check Connectivity”Verify that the device can communicate with ThingsBoard:
- Open the device details page and click Check connectivity.
- Select the protocol (MQTT, HTTP, or CoAP) and your operating system.
- Copy the generated command and run it in your terminal.
On success, the device status changes from Inactive → Active and telemetry appears under the Latest telemetry tab.
Assign to Customer
Section titled Assign to Customer- Open the device details page.
- Click Assign device to customer.
- Select the customer and click Assign.
Only users associated with that customer can access the device and its data.
Make Public / Private
Section titled Make Public / PrivateOpen the device details page and click Make device public to expose device data publicly, or Make device private to revoke public access.
Where Devices Are Used
Section titled “Where Devices Are Used”- Dashboards — visualize telemetry, attributes, and alarms via widgets
- Rule Engine — process incoming telemetry, trigger alarms, route messages
- Calculated Fields — compute derived values from device data
- Relations — model hierarchies (e.g., Gateway → Contains → Sensor)
- REST API — query, create, and manage devices programmatically