Databoom allows the remote control of MQTT devices. A MQTT command consists in the publication of a customized message on the default topic <project>/<device token>/commands or on a topic customized by the user.

The MQTT client must be appropriately configured so it can correctly interpretate the commands received on the topic and execute them.

Device configuration

For a correct configuration of a MQTT device refert to the article MQTT. A MQTT device is commandable if all the fields (ProjectsTopic where publish data and Topic where it's possible to recieve informations from Databoom) are filled.

Signal configuration

In MQTT device signals edit page it is possible to add orders with different templates and publishing topics. Each order can be distinguished by adding a description and an icon.

Enable scaling option applies signal rescaling, if set, to orders values.

The template allows to specify the data format to forward. To indicate the value position in the payload, use the keyword $VALUE$ that will be replaced by the value inserted from the widget. You can also refer more than a value, for example $VAL1$, $VAL2$, ...

Signal and device tokens can be referenced in template using keywords $SIGNAL_TOKEN$ and $DEVICE_TOKEN$.

It is also possible to specify whether to convert the value in hexadecimal with the corresponding checkbox.

Default topic is <project>/<device token>/commands, by checking the checkbox Custom topic it is possible to manually add a topic. The custom topic must contain the device part <project>/<device token>/<customized>

It is possible to add more topics to a single order.

Forwarding a command

It is possible to send commands from the Signals listSignal detail and Signals boxes widgets. Once commands visualization has been enabled in widget menu, orders buttons will be shown, if the device is appropriately configured.

Orders forwarding consists in data publication on the commands topic, is therefore not possible having a feedback on the actual value update. Depending on the type of device used as MQTT client, wait the proper time before reloading the widget and see the updated value.

Additional notes

  • MQTT broker uses a cache to store topics. It may take up to 15/20 minutes before a new topic to be visible;
  • If, after the configuration has been completed, the modal keeps on loading when a command is sent, it may be due firewall restrictions. Be sure the following ports are accessible:
    • 1883 MQTT
    • 8883 MQTT over TLS
    • 8001 MQTT over web socket
Have more questions? Submit a request


Please sign in to leave a comment.