Description
Currently, when an automation is triggered by a Machine Attribute Change, only the changed attribute value is stored in the automation context.
This means that if the automation logic requires other machine attributes, we need to add an extra task to fetch them (e.g., “Update Data”).
However, during the automation execution, other machine attributes might change, leading to inconsistencies between the trigger event and the actual machine state read later.
Suggested Improvement
When an automation is triggered by a Machine Attribute Change, all machine attributes should be captured at trigger time and stored as variable in the automation context.
This would ensure:
-
Consistent data snapshot at the exact trigger moment
-
Reduced number of tasks (−1 task per automation)
-
Simplified automation design and improved readability
Impact
This change would reduce the number of tasks and improve reliability for any automation triggered by a machine attribute change.
In our case, it would remove one redundant task per automation and make event-driven logic more robust.