Qubitro has a built-in rule engine that provides a clear and flexible business integration solution which simplifies the development process and improves the 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.
Qubitro offers built-in rule definitions in addition to custom definitions. The following rules can be created alone or combined with additional conditions.
Triggers when the device connected
Triggers when device disconnected
More topics are available internally and will be rolled out in the upcoming updates.
The following events and values are passed to the destination.
MQTT Message ID
More fields are available internally and will be rolled out in the upcoming updates.
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.
Click the Rules tab under 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.
Qubitro offers both managed and custom Webhook options.
You may ask any question through the chat bot or share a feedback by visiting the Qubitro Feedback platform.