We will walk through the main usage scenarios of the Thriot Central website by registering a new user, creating a device, recording telemetry data and downloading reports.

The demo version of Central website can be found here: http://central.thriot.io/ .


Registering new user and logging in

Register a new user by clicking the Register link at the top right corner of the page:


You will receive an email (since EmailActivation setting is on in the demo environment)


After clicking the link in the email you will be redirected to the main page where you can proceed with login. You will find the following screen after successfully logging in:


Creating new company, service, network, device

Create a new company by clicking the “Add Company” button. After the company is successfully created it will be listed above the “Add Company” button. Clicking on the Manage link you will be navigated to the Company management:


Create a Service under the company, then create a Network under the service then create a Device the network. After creating the device you will see something like the following screenshot:


As you’ve walked the journey creating company(s), service(s), network(s) and device(s) you could discover that there are options to

  • Assign further users to the company to help administering it
  • Delete, edit entities
  • Setup telemetry data sink for companies, services, networks (will be discussed below)
  • Shows reports (will be discussed later)
  • Show api access urls.

By general the left side of the browser window can be used to administer the structure of the IoT solution while the right side can be used to edit/manage/setup deeper details of he current entity.

Setting up telemetry data sinks

In this example we will setup telemetry data sinks at network level which means that all devices under this network will use these telemetry data sinks. The selected telemetry data sinks are handled by Thriot there is no need to further customize them.

The chosen sinks are:

  • Locally hosted Azure table storage for data
  • Locally hosted Azure table storage for timeseries


After clicking the Save button these data sinks will be setup for you.

Note that in this case all data will go to the Azure storage account behind Thiot created for telemetry data. You have the freedom to setup you own storage account and store data in you Azure subscription.

Generating some telemetry data

To generate some telemetry data you can use any of the .NET or Linux client libraries or can even use Curl to post JSON payload directly to the endpoints. Since there are many-many examples on this website or in the integration tests on how to post telemetry data using client libraries this time the curl version will be demonstrated:

curl.exe -i -X POST -H "X-DEVICEID: 0bcd12249b24409d81095e5cd86d5170" -H "X-APIKEY: *********************************" 
         -H "Content-Type: application/json" -d "{\"Temperature\": 23, \"Humidity\": 54}" http://api.thriot.io/platform/v1/telemetry

Explanation of the command line switches:

  -i: output response headers to stdout
  -X POST: use POST Http verb
  -H: Add the specified header to the request. (X-DEVICEID, X-APIKEY are device specific values, while the Content-type specified JSON)
  -d: contains the content to be posted. Take care of escaping JSON strings. May use different escaping method on Linux

 Visualizing telemetry data

At device level or network level the last uploaded data (current data) and time series data can be retrieved in JSON and CSV format, moreover graphs can be down as show below: