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.

1. Navigate to Entities ⇾ Devices.
2. Click + Add device and select Add new device.
3. Enter a Name (must be unique within the tenant).
4. Optionally set a Device profile (defaults to default), Label, or Description.
5. If this device will proxy data for other devices, enable Is gateway (see Gateway Devices).
6. Click Add.

A connectivity check dialog opens automatically right after creation — continue below to verify the device and send its first data point.

Verify that the device can communicate with ThingsBoard:

1. Open the device details page and click Check connectivity (or use the dialog that opened automatically after creation).
2. Select the protocol (MQTT, HTTP, or CoAP) and your operating system.
3. 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.

Having trouble? See Troubleshooting below.

Generate dashboard with AI builds a ready-to-use dashboard for this device in a single click — no prompt needed. AI reviews the device’s available telemetry and attributes and automatically selects the widgets that best fit that data — value cards, trend charts, gauges, an alarms table, and more.

You can trigger it from two places:

• The connectivity check dialog — opens automatically after creating a device, or reopen it anytime via Check Connectivity.
• The device details panel, among its action buttons (see Device Details).

1. Click Generate dashboard with AI.
2. Wait about a minute while AI reads the device’s data and analyzes its telemetry and attributes.
3. The dashboard opens automatically, named after the device (e.g., SN-001 Dashboard), populated with widgets matching its data — including an alarms widget if the device has active alarms.

Prefer to build it yourself? Create a blank dashboard and add widgets bound to this device through an entity alias.

1. Click the pencil icon next to the device in the list.
2. Update the name, profile, label, firmware, or software version.
3. Click Apply changes.

Click the trash icon next to the device and confirm, or open the device details page and click Delete device.

1. Open the device details page.
2. Click Manage credentials.
3. Select the credential type and fill in the required fields.
4. Click Save.

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 during device creation or in the device edit form.

Clicking a device opens its details panel. The header exposes the following actions:

Action	Description
Open details page	Opens the device on its own full page instead of a side panel.
Manage credentials	Change how the device authenticates — see Manage Credentials.
Manage owner and groups	Change the device’s owner and group membership (PE/Cloud only).
Check connectivity	Reopen the connectivity check dialog — see Check Connectivity.
Generate dashboard with AI	Build a dashboard for this device — see Generate Dashboard with AI.
Copy device Id	Copies the device’s unique identifier, e.g. for use with the REST API.
Copy access token	Copies the device’s access token credential.
Delete device	Deletes the device — see Delete Device.

Below the actions, a set of tabs provides access to the device’s data and configuration:

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

1. Open the device details page.
2. Click Assign device to customer.
3. Select the customer and click Assign.

Only users associated with that customer can access the device and its data.

Open the device details page and click Make device public to expose device data publicly, or Make device private to revoke public access.

Symptom	Cause	Fix
Device stays Inactive after running the connectivity command	Access token is wrong, expired, or belongs to another device	Copy the token again from Manage Credentials and re-run the command
Device stays Inactive after running the connectivity command	The command’s protocol doesn’t match the device	Confirm the device’s Device profile uses the same transport (MQTT, HTTP, or CoAP) as the command
Command fails to connect or times out	Wrong host/port, or the port is blocked	Confirm the host in the generated command matches your ThingsBoard instance, and that outbound traffic on that port isn’t blocked by a firewall or proxy
Command succeeds but no telemetry appears	Payload isn’t valid JSON, or uses an unexpected key	Check the terminal output for an HTTP error status or broker rejection, and validate the payload
Generate dashboard with AI shows “No telemetry data found”	The device hasn’t sent any data yet	Send at least one telemetry data point (see Check Connectivity), then try again

• 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)
• Integrations — ingest data from third-party platforms and protocols instead of connecting devices directly
• Command & Control — send RPC commands to devices and receive their responses
• REST API — query, create, and manage devices programmatically

Once a device is created and sending data, a natural next step is to visualize it on a dashboard — manually or with Configure Dashboard with AI — or set up alarm rules to get notified when its telemetry crosses a threshold.