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
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.
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.
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.
Snippets refers to small component containing a dashboard. Multiple variety are available and the librairy aim to growth regularly.
Rules, to Alert and Notify
Mqtt, to communicate
codeGeneral Structure and scenario
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.