Connect Wi-Fi and IoT devices

#Endpoint and ports

Use the endpoint from your workspace details (<your-endpoint> below). The client ID must equal the thing name.

#Topics a device uses

#Telemetry

Publish JSON. Every numeric field becomes a metric you can chart and use in rules; nested objects are flattened ({"power": {"v": 230}} becomes power.v). Add ts (ISO 8601) if the reading was taken earlier than it is sent.

{ "temperature": -19.4, "humidity": 61.2, "door_open": 0, "ts": "2026-11-11T09:30:00Z" }

#Events

For things that happen rather than readings, publish to the events topic with a type:

{ "type": "door_alarm", "duration_s": 95 }

Events appear on the device's Timeline and can trigger rules.

#Commands

Subscribe to your command topic. When a command arrives, do the work, then reply on the response topic with {"status": "ok"} or {"status": "failed", "reason": "…"}. The command moves from queued → sent → acked (or failed). See Send commands.

#Device examples

• ESP32 (Arduino or ESP-IDF): use the MQTT client with TLS; load the root CA, device certificate and key from flash. Keep the clock right (SNTP) so certificate checks pass.
• Linux devices: any MQTT library works (Paho for Python, C or Java; mosquitto_pub for quick tests).

mosquitto_pub -h <your-endpoint> -p 8883 --cafile root-ca.pem --cert dev.pem --key dev.key \
  -i store-hyd-01-freezer-1 -t tic/things/store-hyd-01-freezer-1/telemetry -m '{"temperature": -19.4}' -q 1