t6 IoT App

devices_other Objectssettings_input_component Flowsdashboard Dashboardsexplore Data Exploration 
beta
widgets Snippetscall_split Decision Rules Sources
Current user avatar

Connect physical Objects
to timeseries database

t6 is open-source, freely available and code released as GPL v3 licence - install your own t6 instance or use from Saas latest version here. Also, sample nodeMCU and Arduino scripts are available in t6iot Arduino library so that you can plug your own.

Fork t6 on Github

Objects (any device, sensors, chipsets, devices...) collect data from Sensors and POST them to t6 using the encrypted + signed payload.

Explore t6 documentation

Do any actions you need, once facts match conditions (Email, Mqtt, webhook notification...) — rule based events.

Explore t6 documentation

How does t6 works?

done_all

Free for personal and commercial use

Open-source licence GNU General Public

done_all

Manage your Devices/Objects

Keep an eye on all single Object you own

done_all

Fully responsive UI

t6 will be displayed on desktop, laptop, tablet or mobile phone. Looks great on each screen.

done_all

Google Play mobile application

Mobile application is using the same UI as Desktop.

t6: Connect physical Objects to timeseries database
done_all

Store your virtual Objects and devices

t6 is ready to manage a collection of Objects including your custom attributes, Object location and Security parameters.

done_all

Symmetric signature and cryptography

Data coming from your Object can be signed + encrypted so that we can trust your data.

done_all

Over The Air (OTA) Arduino installation

Control Source on your devices from OTA build and deploy process.

done_all

Trigger actions from Rules

Custom decision rules allows to trigger various actio based on data events, su cha as email, mqtt message, or any custom webhook.

More features to connect your devices:

t6 Features

Digital Asset Management

Data Flows

Datapoints

Measure and store Datapoint values to a timeseries.

Objects localization

Find your Objects on a map and trigger actions based on geofencing.

Over The Air code synchronization

Update your arduino sensors from Wifi on LAN using Over The Air (OTA) protocol.

Https transport protocol

Payload signature

Force (option) any payload to be signed from the Objects to prevent data tampering.

AES256 cbc encryption

Exploratory Data Analysis

Dashboards and Snippets

Rule engine

JWT tokens

Arduino library

IoT application and Use cases

Smart City

t6 ease IoT sensors & actuators deployment within the city. Data are stored on t6 and trigger actions to prevent traffic congestion, road lighting, car park management, safety and so on.

Smart Home

Turn on/off light depending on the time of the day or any other conditions.

Smart Energy

Control thermostats on the rooms; monitor power consumption and so on ...

Smart Fleet

Deploy Over the Air (OTA). t6 is ready to deliver to any of your Objects using a simple Api. The code is spread to all compatible Objects.

Smart Data

t6 embed customizabel dashboards and can trigger action based on multi-criteria events to alert you for any relevant information.

Sign In to t6

Sign Up to t6

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
Sign Up 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

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

code

Physical 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.
code

Technical 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

code

Resources 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.
    More details
     
  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.
    More details
     
  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.
    More details
     
  4. widgets

    Snippets

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

    Rules, to Alert and Notify

    Decision-Rule is the event-based engine that trigger Actions following matching Conditions. Engine is watching for fact matching conditions on payloads coming from datapoint POST, and handle Action(s) according to rules.
    More details
     
  6. volume_down

    Mqtt, to communicate

    More details
     
code

General Structure and scenario

t6 General structure
code

Technical 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

Users

-

-
-