Device Profiles
Device profiles let you centrally define and manage common settings for a group of similar devices — transport protocol, rule chain, alarm rules, firmware, and provisioning strategy. Instead of configuring each device individually, you define the profile once and assign it to as many devices as needed.
Managing Profiles
Section titled “Managing Profiles”Create a Profile
Section titled “Create a Profile”- Navigate to Profiles → Device profiles.
- Click + and select Create new device profile.
- Enter a Name (the only required field).
- Optionally configure the rule chain, queue, transport type, and alarm rules.
- Click Add.
Edit a Profile
Section titled “Edit a Profile”- Click the profile name or the pencil icon.
- Update the desired settings across any tab.
- Click Apply changes.
Delete a Profile
Section titled “Delete a Profile”Click the trash icon next to the profile and confirm deletion.
Profile Details
Section titled “Profile Details”Clicking a profile opens a details panel with the following tabs:
| Tab | Contents |
|---|---|
| Details | Profile name, default dashboard, rule chain, firmware and software version |
| Transport Configuration | Protocol-specific settings: authentication, payload format, topic filters |
| Calculated Fields | Formulas for computing derived metrics from device telemetry or attributes |
| Alarm Rules | Conditions, severity levels, and actions applied to all devices in this profile |
| Device Provisioning | Auto-registration methods, token generation, and provisioning strategies |
| Audit Log | History of user actions performed on this profile |
| Version Control | Git-based export and restore for backup and collaboration |
Transport Configuration
Section titled “Transport Configuration”The transport type determines how devices in this profile communicate with ThingsBoard. See How to Connect Your Device for protocol-specific connection guides.
Key Settings
Section titled “Key Settings”Default Rule Chain
Section titled “Default Rule Chain”Assign a dedicated rule chain to isolate processing logic for this device type — telemetry handling, lifecycle events, and state tracking — without overloading the default rule chain.
By default, all messages use the main queue. Assign a custom queue to isolate high-priority devices (e.g., fire alarms) from high-volume ones (e.g., water meters), or to apply different submit and processing strategies.
Alarm Rules
Section titled “Alarm Rules”Define conditions that apply to all devices in this profile — for example, trigger a Critical alarm when temperature exceeds 40 °C. Rules defined here are shared across every device using the profile. See Alarm Rules.
Provisioning
Section titled “Provisioning”Control how new devices are created and authenticated when they first connect. See Provisioning.