The choice of equipment is determined by the fact that the Thingsboard server is able to receive data via the MQTT protocol, which is widely used to transfer data on the Internet of Things. But popular GPS trackers don't support it. Well, it's okay, in this project we don’t need GPS anyway.

To monitor fuel in a fuel storage, we recommend two options:

1. Eurosens Dominator RS fuel level sensors are installed in each tank, connected to the Eurosens Modem data transmission device via RS485 interface. The modem polls the sensors and transmits volume information to the server via cellular communication (GPRS). Eurosens Modem also supports up to 4 security sensors - door opening, flooding, smoke, vibration and other discrete states. Their states are transmitted to the server as “1” or “0”. Security sensors have a 433 MHz radio interface, EV1527 codec, they are wireless, are very inexpensive and you can find them on Aliexpress.

As mentioned above, the Thingsboard Community Edition server software is free - you can download and install it on your own, providing customers with access to it, or each customer can install their own version of the server.

The installation procedure is described here

https://thingsboard.io/docs/user-guide/ … n-options/

After installation, you can login as System Administrator with credentials : [email protected] / sysadmin

After creating an account, click the Manage tenant admins icon and create an Tenant user. Select activation method - display the link (Display activation link) and click Add

For example, consider monitoring one asset, which is a fuel storage site with 2 tanks installed. Each tank contains one Dominator Bt fuel level sensor, data from which are transmitted to the server via a tablet and the Eurosens Tank Manager program.

In this case, we will have only one asset (site) and 2 devices (Tank №1 and Tank №2).
Let's start by creating the first device and checking that data is coming to it. Go to the Devices menu and click the “+” icon. Set the device name (Tank №1), device type (sensor), in the Description field you can add other information about the device.

In the same way we create the second sensor with its unique MAC-address identifier.

Open the dashboard, which does not yet have a single element (widget). Select the Maps widget, the Latest values type - Openstreetmap. Click on it to select.

You will need to select the data to display on the map. We want to display all our assets on the map. So far, this is one site with fuel tanks, but there will be several of them in the future. This means that the system will have to display all objects. For this, the concept of Alias is used. Let's create the first alias.

We save the changes and see our object on the added widget

Let's create another one dashboard. We want it to open when clicking on the asset icon on the map. And it will display fuel volume information – actual and historic data.
To do this, click on the layers icon at the top left (Manage dashboards states). And create a new state of the dashboard. In the Name field, enter $ {entityName}, in the State id field, create the name of the new dashboard layer - Fuel storage site, i.e. detailed view of the fuel storage area. We do not set the Root state tick - it designates the dashboard layer that is launched by default at startup.

After creating a new dashboard layer, go to the properties of the map widget. In the Actions tab, select the action (Action source), which switches to a new layer - On marker click. We give the action a name - for example, opensite. Select the type of action - navigate to new dashboard state and indicate which dashboard to go to – recently created Fuel storage site. Check the Set entity from widget with the checkbox and save the changes. Now, when you click on the icon on the map, a new widget opens, which is still empty.

After setting the alias, we specify which parameters to display on the chart. All sensors send the fuel parameter (fuel volume in the tank) and fuel temperature t. We type these parameters, confirming the input of each with the Enter key.

The labels, display of each of the parameters can be changed, as well as the color of the graph.

Now we have a fuel volume and temperature plot.

Now let's set up event handling. We need notification of low fuel level in any tank.
Events are defined in the Rule Chains section - rule chains. One of the chains is marked as Root and is the algorithm start point.

For more details on the powerful means of defining events in Thingsboard, read the tutorial. We suggest simply importing ready-made Rule Chains. Download Low fuel and low fuel email chains.

Open Low fuel rule chain in built-in editor.

Now we need to connect the Low fuel chain to the Root rule chain.
Having opened the Root rule chain, we see the following default workflow of Thingsboard engine.

On the left in the menu, select the Rule chain block and drag it to the algorithm field. We choose a name for the chain - it must match the name of the chain that we want to start. This block is a link to it.

Next, we connect the output of the Message type Switch to the input of the new block.

Select the transmitted data - Post telemetry.It means data from the sensors is transmitted to our chain.

The chain is connected. Now, a check for low fuel balance will be launched as a part of Thingsboard workflow, and, if a new warning is present, will launch the chain for sending an email notification.

Same widget you can place on the main dashboard (with the map).

We do the same with devices (Devices) and dashboards. After assigning them to the user, you can log in under the created user and see the results.

User can only view data but doesn’t have rights to modify dashboards or assets.

We've shown you only the most basic thingsboard features. We recommend that you watch the video on the developer channel and repeat the examples indicated there.

https://www.youtube.com/watch?v=0io1YnQjIwA
https://www.youtube.com/watch?v=mqWEGs1Z2BQ
https://www.youtube.com/watch?v=TyUKx5rNJSs

The system supports embedded programming using Javascript, so you can modify the platform, create your own dashboards and data processing algorithms.