Appearance
MQTT ingest
Devices publish telemetry on the broker. The platform subscribes and stores the reading. There is no separate HTTP ingest call for MQTT.
Topics
| Purpose | Topic |
|---|---|
| Telemetry | devices/<device-token>/telemetry |
| Telemetry, older prefix | v1/devices/<device-token>/telemetry |
| Client attributes | devices/<device-token>/attributes/client |
| Shared attributes | devices/<device-token>/attributes/shared |
| Shared attribute request | devices/<device-token>/attributes/shared/request |
| Shared attribute response | devices/<device-token>/attributes/shared/response |
The username is the device token. The public broker is mqtt.autoconnecto.in on port 8883 with TLS, and port 1883 without TLS.
The payload is a JSON object of keys, for example { "temperature": 21.5 }. The platform answers by storing the reading. A rule-engine drop is the user-chosen way a reading is not stored.
MQTT over WebSocket on /mqtt is not a public connect path. Use port 1883 or 8883.