Variables and integrations
The variables defined in a template remain "empty" until an asset of that template is connected to a real physical device (see Connecting a physical device). The integration chosen at the template level determines the protocol through which values arrive.
Trackle integration
For devices using the native Trackle module/SDK, the configuration only requires the Trackle platform's own parameters. Connecting an asset to a Trackle device happens through its External ID, which can be its serial number or a metadata field set during the device's provisioning.
MQTT integration
For devices communicating via MQTT, the template defines a payload template: a schema describing how to interpret the messages published by the device in order to extract variable values. The asset's External ID is used for authentication and to build MQTT topics dedicated to that asset.
HTTP integration
For devices that periodically call the Trackle Spaces HTTP APIs, the template defines an offline timeout: if the device doesn't call the API within this interval, the asset is marked offline. Here too, the External ID identifies which asset is updating the data.
Seneca integration
For Seneca-compatible devices, the connection uses three credentials visible in the template configuration and on the asset's detail page:
- Tenant: your Space name;
- External ID: the asset's unique identifier in the field;
- Token: the authentication key generated for the Space.
From the detail page of an asset with Seneca integration you can also send remote commands to the device (reset, firmware update, VPN management, etc.), with confirmation.
Writable variables
If a variable is marked as writable, from an asset's parameters page (see Asset detail page) you can send a new value that will be written to the connected physical device through the configured integration. This is useful for commands (e.g. turning something on/off, setting a setpoint).