7. Frequently Asked Questions

Here are some answers to frequently-asked questions from users of dojot platform.

Got a question that isn’t answered here? Please, open an issue on dojot’s Github repository.

Table of Contents

7.1. General

7.1.1. What is dojot? Why should I use it? Why open source it?

It’s a brazilian IoT platform launched as open source software with aims to ease the development of solutions and the IoT ecosystem with local resources geared towards brazilians needs.

The dojot acts as a facilitating platform with:

  • Open APIs which makes the access to the platform resources easy.

  • Capacity to store large volumes of data in different formats.

  • Connectors to different types of devices.

  • Graphical user interface with flow builder to quickly prototype IoT solutions.

  • Real time event processing with customizable rules.

7.1.2. Where can I get it?

All components are available in dojot’s GitHub repositories: https://github.com/dojot.

7.1.3. Which repository is the main one?

There are 3 main ones:

See how to use docker-compose and ansible-dojot repositories in Installation Guide.

7.1.4. So, I found this pesky bug. How can I inform you about it?

We ask you to open an issue in dojot’s Github repository.

If you are able to analyze and fix this bug, please do so. Create a pull-request with a quick description of what you’ve done.

7.2. Usage

7.2.1. How do I start it? Is it CLI-based or it has a graphical user interface?

Dojot can be accessed by a web-based interface and by REST APIs. Considering that you installed docker and docker-compose and cloned the docker-compose repository, starting it up is done by just one command:

$ docker-compose up -d

And that’s it.

The web interface is available at http://localhost:8000. The user is admin, password admin.

REST APIs are explained in the Applications section.

7.2.2. Ok, I started it and I logged in. Now what?

Nice! Now you can add your templates and devices, described in Devices, build some flows and subscribing to device events, both described in Data Flows.

7.2.3. How can I update my deploy to dojot’s latest version?

You need to follow some steps:

1 Update the docker-compose repository to the latest version.

$ cd <path-to-your-clone-of-docker-compose>
$ git checkout master && git pull

If you need another version, you could checkout a tag instead:

$ git tag

$ git checkout v0.7.1

7.3. Devices

7.3.1. What are devices for dojot?

In dojot, a device is a digital representation of an actual device or gateway with one or more sensors or of a virtual one with sensors/attributes inferred from other devices.

Consider, for instance, an actual device with thermal and humidity sensors; it can be represented inside dojot as a device with two attributes (one for each sensor). We call this kind of device as regular device or by its communication protocol, for instance, MQTT device or CoAP device.

We can also create devices which don’t directly correspond to their physical counterparts, for instance, we can create one with a higher level of temperature information (is becoming hotter or is becoming colder) whose values are inferred from temperature sensors of other devices. This kind of device is called virtual device.

7.3.2. What is the relationship between this device and my actual device?

It is as simple as it seems: the regular device for dojot is a mirror (digital twin) of your actual device. You can choose which attributes are available for applications and other components by adding each one of them at the device creation interface.

7.3.3. What are virtual devices? How are they different from the other one?

Regular devices are created to serve as a mirror (digital twin) for the actual devices and sensors. A virtual device is an abstraction that models things that are not feasible in the real world. For instance, let’s say that a user has few smoke detectors in a laboratory, each one with different attributes.

Wouldn’t it be nice if we had one device called Laboratory that has one attribute isOnFire? Therefore, the applications could rely only on this attribute to take an action.

Another difference is how virtual devices are populated. Regular ones will be filled with information sent by devices or gateways to the platform and virtual ones will be filled by flows or by applications.

7.3.4. And what are templates?

Templates, simply put, are “blueprints for devices” which serve as basis to create a new device. A single device is built using a set of templates - its attributes will be inherited from each template (their names must not be exactly the same, though). If one template is changed, then all associated devices will also be changed.

7.3.5. How can I send MQTT data to dojot so that it appears on the dashboard?

First of all, you create a digital representation for your actual device. Then, you configure it to send data to dojot so that it matches its digital representation.

Let’s take as example a weather station which measures temperature and humidity, and publishes them periodically through MQTT. First, you create a device of type MQTT with two attributes (temperature and humidity). Then you set your actual device to push the data to dojot.


Since version v0.5.2, you can choose the between two MQTT brokers: Mosca or VerneMQ. By default, VerneMQ is used, but you can use Mosca too. Check the Installation Guide for more information.

In order to send data to dojot via MQTT (using Mosca or VerneMQ), there are some things to keep in mind:

  • When using Mosca, the topic should look like /<tenant>/<device-id>/attrs (e.g.: /admin/efac/attrs). Depending on how IoT agent MQTT was started (more strict), the client ID must also be set to <tenant>:<device-id>, such as admin:efac.

  • When using VerneMQ, the topic should look like <tenant>:<device-id>/attrs (e.g.: admin:efac/attrs). You must also set the username for the client as <tenant>:<device-id>, such as admin:efac, and it should match the same part in the topic. You can also set the client ID too (not required).

  • MQTT payload must be a JSON with each key being an attribute of the dojot device, such as:

{ "temperature" : 10.5, "pressure" : 770 }

You can use certificates with MQTT, check Using MQTT with security (TLS) for more information.

7.3.6. On the dashboard some attributes are shown as tables and others as charts. How are they chosen/set?

The type of an attribute determines how the data is shown on the dashboard as follows:

  • Geo: geo map.

  • Boolean, Text and JSON: table.

  • Integer and Float: line chart.

7.3.7. I’m interested in integrating my super cool device with dojot. How can I do it?

If your device is able to send messages using MQTT (with JSON payload), CoAP or HTTP, there is a good chance that your device can be integrated with minor or no modifications whatsoever.

7.3.9. How can I send some commands to my device through dojot?

For now, you can send HTTP requests to dojot containing a few instructions about which device should be configured and the actuation payload itself. More details on that can be found Sending messages.

7.3.10. I didn’t find the protocol supported by my device in the type list, is there anything I can do?

There are some possibilities. The first one is to develop a proxy to translate your protocol to one supported by dojot. The second one is to develop a IotAgent, a connector, similar to the existing ones for MQTT, CoAP and HTTP. Take a look at https://github.com/dojot/iotagent-nodejs.

7.3.11. How can I retrieve historical data for a particular device?

You can do this by sending a request to /history endpoint, such as:

curl -X GET \
  -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsIn...' \

which will retrieve the last 3 entries of temperature attribute from the device 3bb9:

    "device_id": "3bb9",
    "ts": "2018-03-22T13:47:07.050000Z",
    "value": 29.76,
    "attr": "temperature"
    "device_id": "3bb9",
    "ts": "2018-03-22T13:46:42.455000Z",
    "value": 23.76,
    "attr": "temperature"
    "device_id": "3bb9",
    "ts": "2018-03-22T13:46:21.535000Z",
    "value": 25.76,
    "attr": "temperature"

For more details on data retrieval from the history, check the tutorial in Checking historical data.

In addition, there are more operators that could be used to filter entries. Look for the History API in Components and APIs documentation to check out all possible operators and other filters.

7.4. Data Flows

7.4.1. What is data flow?

It’s a sequence of functional blocks to process incoming device messages. With a flow you can dynamically analyze each new message in order to apply validations, infer information and trigger actions or notifications.

7.4.3. Why should I use it?

It allows one of the coolest things of IoT in an easy and intuitive way, which is to analyze data for extracting information and then take actions.

7.4.4. What can it do, exactly?

You can do things such as:

  • Create views from a particular device, by renaming, aggregating and changing values, etc).

  • Infer information based on switch, edge-detection and geo-fence rules.

  • Notify through many ways, like HTTP.

The data flows component is in constantly development with new features being added every new release.

There are mechanisms to add new processing blocks to new flows. Check the How can I add a new node type to its menu? question for more information on that.

7.4.5. So, how can I use it?

For more details on how to use flows, check the tutorial in Using flow builder.

7.4.6. Can I apply the same flow to multiple devices?

You can use a template as input to indicate that the flow should be applied to all devices associated to that template. It’s worth to point out that the flow is processed individually for each new input message, i.e. for each input device.

7.4.7. Can I correlate data from different devices in the same flow?

As the data flow is processed individually for each message, you need to create a virtual device to aggregate all attributes, then use this virtual device as the input of the flow.

You can also create a node (or use an already existing one) that deals with contexts.

7.4.8. What about a HTTP POST request, how can I send it?


One important note: make sure that dojot can access your server.

7.4.9. I want to rename the attributes of a device, what should I do?

First of all, you need to create a virtual device with the new attributes, then you build a data flow to rename them. This can be done connecting a ‘change’ node after the input device to map the input attributes to the corresponding ones into an output, and finally connecting the ‘change’ to the virtual device and assigning to it the output.


7.4.10. I want to aggregate the attributes of multiple devices, what should I do?

First of all, you need to create a virtual device to aggregate all attributes, then you build a data flow to map the attributes of each device to the virtual one. This can be done connecting a ‘change’ node after each input device to put the input values into an output, and finally connecting all changes to the virtual device and assigning to it the output.


7.4.11. How can I add a new node type to its menu?

There is a tutorial on how to add new nodes and two examples of node too, check the flowbroker library for more details.

7.5. Applications

7.5.2. How can I use them?

There is a very quick and useful tutorial in the Using API interface.

7.5.3. I’m interested in integrating my application with dojot. How can I do it?

This should be pretty straightforward. There are three ways that your application could be integrated with dojot:

  • Retrieving historical data: you might want to periodically read all historical data related to a device. This can be done by using the history API

  • Retrieving real time data: you might want to read device-related real time data. This can be done by using Kafka WS, a websocket based implementation. To better understand how to use Kafka WS check Kafka WS.

  • Using flowbroker to pre-process data: for more flexible ways of data manipulation, you can use flows. They can process/transform data so they can be properly sent to your application via HTTP request, or stored in a virtual device (which can be used to generate notifications as previously described).

All these endpoints should bear an access token, see more Getting access token.

Check the documentation API for History and Kafka WS in Components and APIs. And to a tutorial on how to use the flow, check Using flow builder.