Duration Since Change Aggregation Addition

Feature Request
1

Has there been any consideration for adding Duration Since Change aggregation? In my application, that is a driving factor for creating new events, or renewing previously acknowledged events.

2

I’ll file a feature request for this aggregation method.

That said …

In my application, that is a driving factor for creating new events, or renewing previously acknowledged events.

Would you be able to get the behavior you’re seeking in a workflow doing something like the following …

  1. Device State Trigger, firing a workflow every time devices report state.
  2. On Change Node configured to take the true path on “Any change”, and also storing the previous value on the payload.
  3. Down the true path of the On Change Node, compare the timestamp of the current payload to the timestamp of the previous value.
  4. If the difference exceeds your threshold, create / renew an event.

Let me know if that works for your use case or if you have any questions.

3

Got side-tracked. Going to give this a go this weekend. If the Device State Trigger services an entire fleet, how can it determine the Last Changed for a given device. I don’t see a scalable way to do that without saving the change time as a device tag or time series attribute.

4

You can use the On Change Identifier to scope the behavior per individual device. The example in the documentation actually fits your use case perfectly.