How does t6 works?
Sign In to t6
Sign Up to t6
Terms of Service and License Agreement
Api first documentation
t6 API first: Live, eat, and breathe the API-first lifestyle of t6.
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.
Physical Objects require a virtual Object in t6 and then, they could add Data to Flows.
Resources available on t6
- 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.devices_other
- 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.settings_input_component
- Dashboards to graph, draw, and monitor:Dashboard include one or multiple Snippets. Dashboards allows to visualize your data as graphs and data values.dashboard
- Rules, to Alert and Notifycall_split
- Mqtt, to communicatevolume_down
General Structure and scenario
Api first in a Rest api ; including security (JWT tokens) and quotas.Explore the full Api documentationchevron_right