@Brian

Why is the pointWrite a duration rather than an epoch expiration time?

If I write to the pointWrite from a web browser and it is push down to my device it doesn't make any sense to have a duration that expired in transit only to begin it's duration when it arrives at the location.

Am I missing something here?

Thanks,

Ryan Mattison

Am I missing something here?

You can always derive duration from absolute time, and vise versa. But its implemented that way for two reasons:

1. Its more robust versus relying on devices actually having the correct time setup (which happens all the time)
2. More importantly its maps to how its naturally used where someone wants to override a setpoint for 1hr, etc

   doesn't make any sense to have a duration that expired in transit

If for human overrides, not process control. So its almost always measured in hours, not seconds