Datapoint Presets are available with SmartServer 2.8 and higher.

Datapoint localization are discussed in Connections and Datapoint Objects property table.

Datapoint localization transforms a datapoint value to a specific localized value and datatype, based on the localization rules.  A global setting selects SI or US units.  For example, when SI is selected, temperatures are reported and accepted in Celsius, and when US is selected, temperatures are reported and accepted in Fahrenheit.

This page contains the following sections:

Using Localization and Presets Together

You can use both localization and presets properties at the same time or by themselves.  When presets and localization are set for a datapoint, the presets map is configured based on the local value.  So when you get an update, the value needs to be localized first before mapping to a preset string.  Same with the other direction, when users input a preset string, the map value needs to be transformed using the reverse transformation rule to get the IAP value. 

The Localization Object

The localization object describes the localization transformation. 

• Localization is optional. If the source/destinations do not have localization, the localization object is set to an empty object or null.

• The localization object contains the transformation rules.

• The presets object is submitted with the connection object’s create or update actions and stored in the connection configuration objects.

• The localization object is not stored in the connection object’s status.

The following table describes the location object properties: