Push to Senseye
Senseye has an internal time series database, often called the internal hub or iHub, that customers may store data in for the purposes of predictive maintenance. A variety of methods are available for pushing data to be stored by Senseye, enabling choice in data integration method.
Depending on the push method chosen, you may identify sensors by either an internal Senseye ID (in the form of a UUID), or an external reference, which will be referred to as mapping IDs from here on out.
For all new integrations we strongly recommend using mapping IDs as this enables Senseye to automatically provision new sensors for you. When data is sent to a new mapping ID Senseye will automatically create a new sensor associated with this mapping ID and make it available for import into the hierarchy.
If internal Senseye IDs are used, then prior to pushing data for a new sensor it is necessary to create the required internal hub sensor and record it's internal ID. The steps for creating sensors can be found here.
Info
Mapping IDs are stored against the sensor as an external ID of type SENSOR. Please note that any mapping IDs used must be unique across your organization for the purposes of sending data to Senseye (this may include sites in other locations).
We therefore recommend creating a sensible naming convention for your use case.
If you have any queries about these methods, or using our internal time series database in general, please contact support.