| ID | product.edge.rule_runtime.actuator_client |
|---|---|
| Description | Drives local actuators from rule outcomes. |
| Key | actuator_client |
| Type | component |
| Team | Edge Platform |
| Owner | edge-platform@iotgateway.example |
| Status | active |
| Technologies | Rust, Protobuf |
| Attributes | language: Rust, mode: idempotent, protocol: Modbus/GPIO |
| Tags |
The Actuator Client is where a decision becomes a physical action. When the Rule Evaluator fires an outcome — close a valve, trip a relay, set a setpoint — this component translates it into the right local bus command and confirms it took effect.
The host's hands
This is the only part of the rule runtime allowed to touch hardware. Rules declare what should happen; the actuator client owns how it happens on the specific Modbus / GPIO surface of this gateway.
The outcome’s logical actuator id is mapped to a concrete bus address from the gateway’s actuator manifest.
The command is issued over the local protocol (Modbus, GPIO, vendor serial) and the result is read back to confirm the actuator reached the requested state.
The applied action — with rule id and timestamp — is recorded so the cloud has an audit trail of every physical change made on the edge.
Rule-driven and cloud-driven actions share the same dispatch path:
1 outgoing link
| Target object | Label | Link type | Relation | Raw id | Required | Description | |
|---|---|---|---|---|---|---|---|
| executes outcomes from | — | links | product.edge.rule_runtime.evaluator | — | — |