Connect the first device without losing data meaning

Choose a stable device identifier that survives firmware changes and support hand-offs. Define every first-pass variable with its type, engineering unit, valid range, sampling interval, and timestamp source.

{
  "temperature": {
    "value": 27.4,
    "timestamp": 1721456400000,
    "context": { "unit": "degC", "quality": "good" }
  }
}

HTTPS is a clear first path for devices that wake, send a bounded payload, and disconnect. MQTT suits long-lived sessions, constrained links, and publish/subscribe workflows. Confirm the deployment-specific endpoint and credential in the authenticated project record.

• Use encrypted transport and validate the server certificate.
• Buffer locally when a missing reading would affect the operating decision.
• Preserve timestamps and sequence when backfilling after an outage.
• Design retries so they cannot create duplicate actions or misleading data.

Do not begin with a full production payload. Send a known value, inspect it in the platform, and increase scope only after identity, value, unit, and time match the source.

1. 01Provision the device or gateway with its assigned non-production credential.
2. 02Send one known value and record the source reading.
3. 03Verify device identity, variable, unit, timestamp, and quality in the portal.
4. 04Disconnect and reconnect the network, then inspect gaps, order, and duplicates.
5. 05Record the accepted hardware, firmware, and configuration versions.