Configure conditions and actions
Purpose
Section titled “Purpose”Condition nodes determine when an action is eligible. Action nodes describe explicit event or command intent.
Before you start
Section titled “Before you start”Use parameters from applied device configurations and supported nodes. Commands need allowed device settings and grants.
- Connect a source to the condition’s required input.
- Configure comparisons, boolean logic, timing, or supported device-state checks.
- Connect the condition to an explicit action.
- For command actions, choose each setting and value, and check allowed values and grants.
- Save, validate, and simulate positive, negative, and missing-data cases before activation.
Expected result
Section titled “Expected result”The workflow evaluates the configured inputs and records decisions. An unknown or missing input is distinct from a false condition or a numeric zero.
Troubleshooting
Section titled “Troubleshooting”Check required connections, binding identifiers, state freshness, and action suppression evidence. A command intent does not prove delivery or observed state. Geofence nodes retain their copied geometry until you update the workflow.