Skip to content
This repository has been archived by the owner on May 2, 2024. It is now read-only.

scheduled timer events

Sautner edited this page Mar 5, 2016 · 2 revisions

Right click on your tree and select to create a scheduler entity that will run at a set interval server side. Schedulers will run at a regular interval and can be used to send the value of a source point to a sensor, server or other targets.

When the schedule executes, the current value of a source data point will be copied over to the target data point. This is a powerful mechanise since you can change the value of the source point by recording new data to it. For example, if you create a source data point that you can record a 1 or 0 to, and set a scheduler to run every 12 hours the target point can be configured to send a message to a listening device. That device can turn a switch on or off depending the value being recorded to the source point.

Things get exciting when a collection of sensors feed data into parent points, which trigger calculations that result in a value being stored in the source point for the schedule, and then written to the target on a regular basis.

schedules

Examples

Email me the current value of an key performance indicator 8 hours

  • Source Point: The result of other data processing, written to every minute

  • Target Point: A point with a subscription configured to send an email on any new data.

  • Interval: Set to every 8 hours

  • Turn a light on and off using two schedulers

  • Two data points, one that always have the value of 0 (zero) and another with a value of 1 (one)

  • A Scheduler set with a source of the zero point, and a target point of a switch

  • Another scheduler set with the source of the one point, set with the same target.

  • The schedulers are set to run 12 hours apart from each other.

  • The shared target point sends push notifications using a subscription to the sensor