Meta Fields - Advanced Device Types options
If you are in Site Admin (Legacy) > Devices > Types and select a device, you will find some advanced options (Meta Fields) that are available to certain devices' brands and models. For example, using meta fields you can set up specific OneWire SensorID for devices that support multiple temperature reading options.
How to use it
1. Enable the desired option in Site Admin (Legacy) > Devices > Types > (your selected device)
2. Save the Device Type.
3. You can select this device type in your vehicles in your application. You can read more about using new device types here.
Meta fields descriptions
| Option | Description | Setup guide |
| Allow replacing OneWire Sensor ID | Allows replacing existing and unused OneWire ID with another one. | setup |
| Convert_to_GCJ02 | Adjust lat/lon coordinates to China location offsets (GCJ02). | N/A |
| Keep valid position on heart beat | Applicable for Concox devices. Keeps repeating last position when the device sends Heartbeat messages. | N/A |
| Save emulated first message of day | Determines how records are handled for new tracks. When this property is 'False' (default): Always save the first occurrence of a record in a new track regardless if it's changed or not. When this property is 'True': All latest known values will be saved for the first message (received wise, not necessarily message time wise) in track regardless if the records where included in the device message or not. This option is NOT recommended if the device sends unordered data. |
N/A |
| Time Zone | Use this option if the device sends data with localized TimeStamp and not UTC. | N/A |
| HDOP Valid Threshold |
Available in some models of Queclink devices. The value must be at least 1, and to make a position valid, bigger or equal compare to what the device sends for GPS Accuracy. For example, if the device sends GPS Accuracy = 1, then HDOP Valid Threshold should be at least 1 in order to validate a position | N/A |