t6 IoT App

devices_other Objectssettings_input_component Flowsdashboard Dashboardswidgets Snippetscall_split Decision Rulesvolume_down Mqtt Topics
Current user avatar

How does t6 works?

Objects

Add Object

Flows

Add Flow

Snippets

Add Snippet

Dashboards

Add Dashboard

Rules

Add Rules

Mqtts

Add Mqtt

Sign In to t6

Sign Up to t6

My Profile

Manage Notifications

Manage your Email notification & subscriptions.
Skip this step (I will do it later).

Forgot Password

Enter your Email address below and we'll send you password reset instructions securely.
emailUsername should be your email address
Create an account or Sign In.

Set Password

Set you new password to connect your t6 account.
Password must contains lower cases, upper cases, digits, special characters; and must be longer than 8 characters.
lockPassword is not strong enough
lockPassword does not match
 or Sign In.

Settings

t6 API

Terms of Service and License Agreement

Api first documentation: Live, eat, and breathe the API-first lifestyle of t6.

codePhysical World
Physical World are composed by your sensors and actuators. Physical Objects require a virtual Object in t6 and then, they could add Data to Flows. Sample nodeMCU and Arduino scripts are available in the sensors repositories.
An additional script can be runned periodically (crontab rule necessary) and performe the required action from the settings:
$> nodejs sensor.js --run "{{sensor_id}}" > /dev/null 2>&1
This kind of Virtual sensors are capable of getting direct data from a linux bash command (e.g. Getting HDD temperature: '/usr/sbin/hddtemp -u C -n -q /dev/sda')
Physical Objects require a "virtual" Object declared on t6 before adding DataPoints to Flows. Meaning a Flow container help the Api to find your data and graph them on the Snippets.
codeResources available on t6
  1. devices_other

    Objects, sensors and actuators

    Objects are virtual items dedicated to push data to flows. Objects are defined for each Users.
    Objects in t6 are the virtual nodes of your physical devices. They are sending values from their embedded sensors to the Flows. Common cardinality is 1:1; but you can setup multiple Flows for the same Object (a DHT11 sensor handle 'temperature' and 'humidity' for instance). Additionally, you can set a Flow to be feed from multiple Objects.
     
  2. settings_input_component

    Flows & DataPoints

    Flows are datastore to save time/values (DataPoints). Each Object can POST data to multiple Flows. Flows are defined for each Users and are having permissions.
    Communication becomes easy in the platform with Timestamped values. Flows allows to retrieve and classify data.
    Objects are sending their Data to Flow-containers using the API.
     
  3. dashboard

    Dashboards to graph, draw, and monitor

    Dashboard includes one or many Snippets to visualize your data. You can create as many dashboards as you like.
     
  4. widgets

    Snippets

    Snippets refers to small component containing a dashboard. Multiple variety are available and the librairy aim to growth regularly.
     
  5. call_split

    Rules, to Alert and Notify

     
  6. volume_down

    Mqtt, to communicate

     
codeGeneral Structure and scenario
t6 General structure
codeTechnical documentation
Api first in a Rest api ; including security (JWT tokens) and quotas. It contains dedicated endpoint to easily manipulate your resources: Objects, Flows, Dashboards, Snippets & Rules.

Explore the full Api documentationchevron_right

-

-
-