Settings
Settings give a device a usable operating context. A setting can have a default and constraints that keep values inside the range the device supports. Settings may be used when an operation is invoked or when a rule evaluates a condition. When a setting changes, verify the value on the device or in the next read that depends on it. A locally stored setting is not proof that the hardware accepted it.Rules
Rules evaluate conditions using available settings, telemetry, connection or change context, and application-provided values. A matching rule can:- invoke a component operation;
- set a device setting;
- save a read result for a later record;
- show an informational, warning, or error alert;
- delay or sequence further actions; or
- start a named workflow.
Workflows
Workflows are explicit multi-step sequences. Common steps include ensuring a connection, invoking an operation, polling for a result, writing a payload in chunks, and handling completion or failure. The workflow proceeds in order unless a step explicitly declares concurrent work. Each step should have a clear success signal and a bounded failure path so a field user is not left guessing what happened.A practical design pattern
1
Read the current state
Start with a safe read so the workflow has an observable baseline.
2
Apply the smallest change
Set one setting or invoke one operation with a known payload.
3
Poll or observe
Wait for the expected response, notification, or status transition.
4
Save or alert
Store a result when it is part of field work, or show a clear alert when the workflow cannot complete.