Skip to main content

ThingsBoard

[!NOTE] For backups/migration order and portability risks, see docs/internal/operations/backups.md.

[!NOTE] For the OAuth bootstrap and the ThingsBoard - Zitadel integration flow, see docs/internal/services/platform/thingsboard-zitadel.md.

[!NOTE] For runtime config generation and secrets handling, see docs/internal/operations/environments.md.

This page is a practical UI-oriented guide for configuring and operating ThingsBoard in this ecosystem.

Asset and Device Profiles​

Profiles define shared configuration for groups of assets or devices.

Asset Profiles​

  • Manual creation: Go to Asset Profiles and click +. Define the name and the message queue.
  • Import: In the same section, use the import icon (down arrow). Import files live under thingsboard/ in the repository.
  • Official documentation: Asset Profiles

Device Profiles​

  • Manual creation: Go to Device Profiles and click +. Configure transport (MQTT, HTTP, LwM2M) and data processing.
  • Import: Use the import button. Required files are under thingsboard/.
  • Official documentation: Device Profiles

Devices and Assets Management​

Create and assign to a customer​

  1. Go to Devices or Assets.
  2. Click + to add a new one.
  3. After creating it, select the item and use Assign to Customer.
  4. Pick a customer from the list. This allows customer users to see and manage the item.

Relate devices to assets​

Relations allow you to build hierarchies (e.g. a Sensor belongs to a Tank).

  1. Open the asset or device details.
  2. Go to the Relations tab.
  3. Click add relation.
  4. Select the type (e.g. Contains, Manages) and search for the target entity.

Rules and Automation​

Rule Chains​

  • Import: Recommended method. Go to Rule Chains, click +, then Import. Files are in thingsboard/.
  • Configuration: After importing, set it as "Root" if it's the main chain, or connect it to the Root Rule Chain.
  • Official documentation: Rule Engine

Alarms​

Alarms are usually configured in Device Profiles under the Alarms tab, or via nodes inside Rule Chains.

Notifications​

Notification Center​

Aitha Things can send internal notifications, email, SMS, or Slack.

  1. Define Notification Recipients.
  2. Create a Notification Template.
  3. Configure a Notification Rule to trigger sending based on an event (e.g. Alarm created).

System Configuration​

OAuth2​

To enable login via external providers (Google, Azure, etc.):

  1. Go to System Settings -> OAuth2.
  2. Add a new domain and configure the Client ID and Client Secret provided by your provider.
  3. For Zitadel in this ecosystem, also use the bootstrap & sync technical guide to separate what remains manual vs what can be automated by the portal.

Email (SMTP)​

Required for notifications and password recovery.

  1. Logged in as Sysadmin, go to System Settings -> Mail Settings.
  2. Enter your SMTP host, port, and credentials.

Dashboards and Hierarchy​

Dashboards​

  • Import: Go to Dashboards -> + -> Import. Files are in thingsboard/.
  • Assignment: After importing, assign it to the right customers so their users can access it.
  • Official documentation: Dashboards

Creating tenants, customers, and users​

  1. Tenant: The system administrator creates the Tenant (top-level entity).
  2. Tenant Admin: User with full control over tenant resources.
  3. Customer: Entity within the tenant that groups devices and end-users.
  4. Customer Users: End-users who only see resources assigned to their customer.