IoT connectivity
IoT connectivity defines how physical devices communicate with Trackle Spaces. It is a property of the template: every asset of that type uses the same protocol.
On the template page you will find the IoT connectivity section (separate from Telemetry, where you configure variables). Choose the type and complete the protocol-specific settings; live values arrive only after each asset is linked with its External ID.
Supported types
| Type | When to use it |
|---|---|
| Trackle | Devices with the native Trackle module/SDK. |
| MQTT | Devices that publish/subscribe to MQTT topics. Includes the Generic, Seneca, Siemens Logo and Teltonika RutOS profiles. |
| HTTP | Devices that periodically call the Trackle Spaces HTTP APIs. |
Trackle
For devices with the native Trackle module/SDK.
- On the template, under IoT connectivity, select Trackle.
- Enter the Trackle API credentials (Product ID, Client ID, Client Secret) used by Spaces to authenticate against the Trackle APIs.
- In the Trackle console, configure the Trackle Spaces integration (Product → Integrations → Trackle Spaces) with the webhook URL shown on the template.
- On each asset, set the External ID (often the device serial, or a provisioning metadata field).
MQTT
The asset External ID is used for authentication and dedicated topics. The Space token (see API Token) is the device password.
After choosing MQTT, pick a profile. The profile does not change broker, username or password: it changes how Spaces interprets inbound payloads and how it builds write (downlink) messages. It also changes which options you see on telemetry fields.
Profiles
| Profile | When to use it | Downlink |
|---|---|---|
| Generic | Any MQTT client. You define the write topic and payload shape. | Topic suffix and payload template on the template; each writable field can override them. |
| Seneca | Seneca gateways/devices. | Topic and payload are fixed ({ "value": … }). Remote commands (reboot, VPN, …) are available on the asset page. |
| Siemens Logo | Siemens LOGO! PLCs over MQTT. | Fixed payload in the LOGO state format ({{key}} is the tag name). |
| Teltonika RutOS | Teltonika routers/gateways (Modbus over MQTT). | No template-level write template: each writable field has its own write JSON (often pre-filled by discovery). |
For Seneca, Siemens Logo and Teltonika the UI states that downlink topic and payload are defined by the profile: the template Topic suffix and Payload template fields stay hidden.
Generic profile — template downlink
Besides the profile, you can configure two optional options used when a writable variable is sent to the device. They apply to every field that does not have its own write template:
| Field | Effect |
|---|---|
Topic suffix (topicSuffix) | Appended to the downlink subscribe topic. Can use the {{key}} placeholder (field key). If empty, the standard topic is used (…/<key>). |
Payload template (payloadTemplate) | Shape of the published message. Placeholders: {{key}}, {{value}}, {{json_value}}, {{random}}. If empty, only the raw value is published. |
A template on the individual field (see Telemetry) takes priority over these two values.
Seneca profile — remote commands
Typical credentials used by the device:
- Tenant: Space name
- External ID: usually the device MAC
- Token: Space authentication token
From Data exchange on the asset detail page you can send (with confirmation):
| Command | Code |
|---|---|
| Reboot | RESET |
| Configuration set / get | CONF_SET / CONF_GET |
| Firmware update | FW_UPDATE |
| VPN PPP on | VPN_PPP_ON |
| VPN on / off | VPN_ON / VPN_OFF |
| VPN custom on / off | VPN_CUSTOM_ON / VPN_CUSTOM_OFF |
| Clean logs | DL_CLEAN_LOGS |
These commands are not telemetry variables: they use a dedicated topic (act) and payload { "act": <code> }. Writing a field (setpoint, outputs, …) uses { "value": <value> } instead.
What the device configures
The template IoT connectivity section also shows connection instructions (TLS broker, username, password/token, publish and subscribe topics). Use those credentials on the device; set the External ID on the asset.
HTTP
The device sends data with a POST to the Trackle Spaces public API, authenticating with the Space token and the asset External ID (as header or query parameter).
Template settings
| Field | Effect |
|---|---|
| Offline timeout | If the device does not call the API within the interval, the asset is marked offline. Set 0 to disable; if enabled, minimum 30 seconds. |
The same section shows the endpoint URL, request examples and accepted payload formats. Field structure (keys, types, units) is defined under Telemetry instead.