Data is transmitted to Geeny in the form of Message Types. Message Types are typically defined by data providers, who share data from their consumers’ data sources with Geeny, and consumed by application providers, who connect their IoT applications to Geeny and query the data over our API. While our data providers are free to construct their Message Types as they see fit for their use cases, we have written some guidelines and recommendations in order to harmonize the flow of data in and out of our platform.
We realize that different devices typically transmit different sets of data, even if they fall into the same device category. We wrote these guidelines in order to reduce the complexity and effort required for data providers to share data with Geeny and for application brokers to implement multiple data sources in their applications.
Please adhere to these guidelines for creating and using Message Types:
We have implemented the following common data formats as standard Message Types:
Click here to view this Message Type in the Data Explorer.
true
or false
true
Click here to view this Message Type in the Data Explorer.
{
"time": "2008-09-15T15:53:10.325+05:00"
}
Click here to view this Message Type in the Data Explorer.
{
"meters": 1.75
}
Click here to view this Message Type in the Data Explorer.
seconds.milliseconds
{
"duration": 45.345
}
Click here to view this Message Type in the Data Explorer.
{
"time": "2008-09-15T15:53:10.325+05:00",
"event": "EVENTNAME"
}
Click here to view this Message Type in the Data Explorer.
{
"bpm": 120.5
}
Click here to view this Message Type in the Data Explorer.
{
"frequency": 8.75
}
Click here to view this Message Type in the Data Explorer.
{
"lux" : 200.75
}
Click here to view this Message Type in the Data Explorer.
{
"long": 40.689263,
"lat": -74.044505
}
Click here to view this Message Type in the Data Explorer.
{
"grams": 62456.34
}
Click here to view this Message Type in the Data Explorer.
{
"temperature": 36.645
}
Click here to view this Message Type in the Data Explorer.
{
"from": "2008-09-15T15:53:10.325+05:00",
"to": "2008-09-16T08:21:27.985+05:00"
}