The Tartabit IoT Bridge is an easy to use integration service that quickly connects LPWAN IoT devices to enterprise applications. This section provides conceptual information about the platform and how to go about building your solution quickly.
Applications are built by developing triggers that enable endpoints to communicate to applications via services.
Your first step is usually to start by creating a service. Services are used to configure connections to enterprise applications or to devices. An example would be a service to connect to InfluxDB, such a service requires the hostname of the InfluxDB server, the authentication credentials, as well as the database to use. Similarly, a service like the HTTP service can be used to receive information from device clouds and requires configuring the webhook secret to uniquely identify the traffic from your device cloud.
Endpoints are used to identify the devices in the field. These endpoints serve as anchors to provide stateful functionality to the service. There are two types of endpoints that you may encounter:
Triggers are the work-horse of the platform. Triggers are configured to execute when events that match its defined filters are received. The trigger executes a script that can decode and manipulate the data from the event, and then call functions to trigger actions that send the data to other services. Typically workflow can be defined as either "device to cloud" or "cloud to device", depending on the use case.
All triggers begin with an event. When events are generated, they are routed to the relevant triggers enabling the trigger execution to begin. Events contain meta-data from within the IoT Bridge, as well as any relevant data that relates to the event. For example a "data change" event would contain a timestamp, device identifier, and the value that has changed.
Actions are the mechanism for triggers to send data to a service. Actions can be used to send data to an Azure IoT Hub, or insert a row of data into a database. Actions can also affect devices, by initiating a firmware update, or changing a setpoint.
Below is a diagram that shows how data moves from devices to applications in the IoT Bridge.
One of the more complex decisions to make in any IoT solution is how to identify and track the asset that you are trying to connect. You can choose to track an asset by one of its network identifiers (IMEI, ICCID, MAC address), or by something unique to your product like a serial number of VIN of a vehicle. There are pros and cons to each approach, typically the telematics device doing the tracking can be replaced in the event of a maintenance problem, but the asset itself remains the same, so in these cases, tracking by a product ID makes sense. Sometimes the device is essential to the operation, so tracking by the IMEI or ICCID makes more sense. You need to consider these options when configuring your application.
The Tartabit IoT Bridge measures the number of events that are generated within your account and all sub-accounts. The standard contract allocates your account a number of events per day that can be executed before execution will cease. Please refer to the documentation for the specific services that you are using for details about what is considered a billable event.
In the event that your account is suspended for exceeding your allocated daily events, your account will automatically un-suspend at midnight UTC the next day and processing will resume as normal.