An overview on interfaces for data exchange
So you want to export data from Datacake? Great! Because it's easier than you might think right now.
We'll now introduce you to the options you have for exporting your sensors' measurement data, whether individually, as a group, or all the sensors in a workspace.
Basically, there are several ways of exporting data. However, in summary, these options fall into the following two categories.
Real-Time Data Forward
Historical Data Poll or Read Out
For each device you create on Datacake, a topic automatically exists on our MQTT broker. This even applies to every database field that your device has. This way you can subscribe to single readings, whole devices, or a large group of devices via an external MQTT client.
Automatically generates an MQTT message on incoming measurement value.
Token-based authentication with dynamic rights management.
Subscription per product (group of devices), single device, or database field.
Bi-directional communication for a response from external systems or device communication.
Read more about our internal MQTT Integration here.
Internal MQTTEach workspace supports the storage of one or more web addresses, so-called outgoing webhooks. Depending on the action of the devices in your workspace, these web addresses (webhook URLs) are then called.
The actions can represent the following.
Incoming measured values.
Execution of the payload decoder (with debug output).
Triggered downlink via user or rule engine.
Read more about our Outgoing Webhook Integration.
Outgoing WebhooksDatacake offers Node-RED extensions for real-time forwarding of selected sensor data. Read more about this feature here.
Node RED to DatacakeIn addition to the real-time forwarding of measurement data, there are also interfaces that enable the readout of historical data. These interfaces often also provide an interface for reading out user data and controlling actions (such as creating devices, etc.).
Last updated
Was this helpful?
Was this helpful?
