Qubitro has a built-in rule engine that provides a clear and flexible business integration solution that simplifies the development process and improves usability.
The rule will trigger when the message is published and the event is triggered, and the rules meeting the triggering conditions will execute automatically.
In the rule processing flow, data is filtered by rules, processed, and finally passed to action processing.

Rule Composition

Qubitro offers built-in rule definitions in addition to custom definitions. The following rules can be created alone or combined with additional conditions.

Available topics

Device Connected
Triggers when the device connected
Device Disconnected
Triggers when device disconnected
More topics are available internally and will be rolled out in the upcoming updates.

Default fields

The following events and values are passed to the destination.
MQTT Message ID
Device ID
Message Content
More fields are available internally and will be rolled out in the upcoming updates.

Rule operators

Comparison Operators

Equal to
Greater than
Less than
Greater than or equal to
Less than or equal to
Not equal to
Mathematical (abs, cos, sqrt etc.), type judgment (is_float, is_int etc.), type conversion (str, float, map etc.) and string functions (lower, upper, trim etc.) are available internally and will be rolled out in the upcoming sprints.

Creating Rules

  • Select device
  • Click the Rules tab under the device
  • Click the New Rule button
  • Give a name to Rule
Device data entities automatically will be available under the Select Entity list.
  • Select condition option
If you select a topic (e.g. Device Connected), you don't need to take any further action.
If you select a device entity, select operator and value input will appear.
  • The last step is choosing the rule type and providing the required information.
Choose the rule type and follow the instructions and see the examples.

Rule Types

Qubitro offers different types of rule destinations.


Last modified 1yr ago