thingsboard-skill_skill

This skill helps you manage ThingsBoard resources like devices, dashboards and telemetry via REST API for streamlined IoT administration.
  • Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill thingsboard-skill

  • _meta.json285 B
  • credentials.json470 B
  • SKILL.md8.2 KB

Overview

This skill manages ThingsBoard IoT platform resources through the ThingsBoard REST API. It provides commands and examples to authenticate, list and inspect devices, read telemetry and attributes, manage dashboards and assets, and handle tenant and customer users. Use it to automate backups, audits, or integrations with scripts and CI pipelines.

How this skill works

The skill issues REST requests (curl examples) against ThingsBoard endpoints, using JWT tokens for authentication. It demonstrates common workflows: login to get a token, list entities with pagination, fetch telemetry and attribute scopes, modify dashboard public access, and operate on users and assets. Examples show how to build timestamps for time-series queries and how to parse responses with jq.

When to use it

  • Automate inventory and backup of ThingsBoard devices and dashboards
  • Integrate telemetry extraction into monitoring or analytics pipelines
  • Audit users, tenants, customers, and asset configurations
  • Create scripts to export or clean historical telemetry data
  • Set up public dashboards or revoke public access programmatically

Best practices

  • Keep TB credentials and tokens out of source control; use environment variables or a secure vault
  • Re-authenticate when you receive 401 errors; tokens expire (default ~2 hours)
  • Use pagination (pageSize & page) for large listings and respect server rate limits
  • Use HTTPS in production to protect tokens and data in transit
  • Use entity id fields (id.id) extracted from responses when calling entity-specific endpoints

Example use cases

  • Full scripted workflow: login, list devices, get a device ID, fetch latest telemetry and last-hour timeseries
  • Bulk operations: list tenant dashboards and make specific dashboards public or revoke public access
  • Telemetry extraction for analytics: query timeseries with startTs/endTs in milliseconds and save results to a database
  • Administration: list tenant users and customers for audits or automated user provisioning
  • Asset management: list assets and fetch individual asset details for synchronization with external CMDBs

FAQ

POST to /api/auth/login with JSON {"username","password"} and extract the token from the response. Store it in an environment variable for downstream calls.

What timestamp format do timeseries endpoints require?

Use milliseconds since epoch for startTs and endTs. Common shell pattern: $(($(date +%s)*1000)).

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational