MQTT Rule Engine
Qubitro provides various rules for MQTT Rule Engine.

Introduction

Qubitro has a built-in rule engine that provides a transparent and flexible business integration solution that simplifies the development process and improves usability.
The rule will trigger when the message is published, 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

Event
Description
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.
Event
Description
id
MQTT Message ID
clientid
Device ID
payload
Message Content
More fields are available internally and will be rolled out in the upcoming updates.

Rule operators

Comparison Operators

Description
Operator
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.

Rule Types

Qubitro offers different types of rule destinations.

Webhooks

Support and Feedback

If you have further questions or suggestions, feel free to join
👇
-> Qubitro Community Forum -> Community Discord via this invitation link.
Last modified 28d ago