Overview

Reprinted articles: https://thingsboard.io/docs/

Introduction

See What is ThingsBoard?

../_images/f856b5dd0016c4c1b989331d1ba2fb7c19823cc4a14e33d6b11dce4a8c282a6a.svg

Features

Entities and relations

See Entities and relations .

Working with telemetry data

See Working with telemetry data.

../_images/eb34f8906c5c750b39ab050df2a419c621e8b76628a65be0599dfb36335305fa.svg

Working with IoT device attributes

See Working with IoT device attributes.

Attributes are treated key-value pairs. Flexibility and simplicity of the key-value format allow easy and seamless integration with almost any IoT device on the market.

Device specific attributes are separated into two main groups:

  • client-side attributes - attributes are reported and managed by the device application. For example current software/firmware version, hardware specification, etc.

  • shared attributes - attributes are reported and managed by the server-side application. Visible to the device application. For example customer subscription plan, target software/firmware version.

../_images/138c4286b0dfd52f6ca1b842e1d1930fa247bf6ab28aa6369cde4cd20a5ad318.svg

Using RPC capabilities

See Using RPC capabilities.

Thinsboard RPC feature can be divided into two types based on originator: device-originated and server-originated RPC calls. In order to use more familiar names, we will name device-originated RPC calls as a client-side RPC calls and server-originated RPC calls as server-side RPC calls.

Client-side RPC

../_images/f6c1cab2136504ab9f579dd0285989b2d92feb4a16c0f589f95e2243a0e10a0a.svg

Server-side RPC

Server-side RPC calls can be divided into one-way and two-way:

  • One-way server-side RPC request is sent to the device without delivery confirmation and obviously, does not provide any response from the device. RPC call may fail only if there is no active connection with the target device within a configurable timeout period.

    ../_images/cb0452fe943458769fa58056e667aba0daa48c023328511b42324d9d07da0fad.svg

  • Two-way server-side RPC request is sent to the device and expects to receive a response from the device within the certain timeout. The Server-side request is blocked until the target device replies to the request.

    ../_images/1998ca311f6142613e531914cd22b472dfeed3f74e0ca62d6bc3f8eb361005ef.svg

Claiming devices

Refer to Claiming devices.

TODO…

Over-the-air firmware and software updates

See OTA Updates.

Getting Started Guides

These guides provide quick overview of main ThingsBoard features. Designed to be completed in 15-30 minutes.

  • Hello world : Learn how to collect IoT device data using MQTT, HTTP or CoAP and visualize it on a simple dashboard. Provides variety of sample scripts that you can run on your PC or laptop to simulate the device.

  • End user IoT dashboards : Learn how to perform basic operations over Devices, Customers, and Dashboards.

  • Device data management : Learn how to perform basic operations over device attributes to implement practical device management use cases.