Device reference

MQTT topics and payloads for Paqett devices

The MQTT topics a Paqett device publishes and subscribes to over mutual TLS: status, hello, commands and OTA, with payloads, QoS and retain flags.

Updated 19 November 2026

A device connects to mqtt.paqett.com:8883 with its client certificate. The broker takes the device id from the certificate's common name and uses it as the MQTT username and client id, whatever the client sends. The device may then publish and subscribe under devices/<device id>/ and nowhere else.

Connecting

SettingValue
Host, portmqtt.paqett.com, 8883
TLSVerify the broker with ca_pem from provisioning (hostname check on); present cert_pem and the device's key
Client idThe device id. The broker sets it from the certificate either way.
Username, passwordNone needed
Last willdevices/<device id>/status, payload {"online":false}, retained, QoS 1

Topics

All topics are under devices/<device id>/.

TopicDirectionQoS, retainPayload
statusdevice, and the broker as the will1, retained{"online":true} on connect; {"online":false} when the connection drops
hellodevice, on every connect1hardware_id, model, firmware, reset_reason, uptime_ms, rssi, ip
telemetrydevice1Readings, in your device's own format
cmd/<name>platform1A command
cmd_ackdevice1cmd, ok, and anything the command returns
otaplatform1, retainedA firmware update offer, or empty when there is none. See OTA updates.
ota_statusdevice1How an update is going. See OTA updates.

On every connect

  1. Publish {"online":true} to status, retained, so anything that subscribes later sees the device as online.
  2. Subscribe to cmd/# and ota.
  3. Publish a hello.

The order matters for OTA: a device subscribed to ota before it says hello receives any waiting offer, and the platform re-sends an unfinished offer with a fresh download link when it sees the hello.

hello

{
  "hardware_id": "esp32c6-40ac1b2c3d4e",
  "model": "esp32c6-devkit",
  "firmware": "0.3.0",
  "reset_reason": "poweron",
  "uptime_ms": 5120,
  "rssi": -61,
  "ip": "192.168.1.42"
}

The platform records the device's presence and last hello, and takes its firmware version from firmware. That is also how it decides whether an OTA update took: the next hello after an update reports the version the device came back on.

Commands

The platform publishes a command on cmd/<name>; the device answers on cmd_ack. cmd/ping is the one every device answers:

{"cmd":"ping","ok":true}

A command the device does not know is answered too, so the platform is never left waiting:

{"cmd":"reboot-into-dfu","ok":false,"error":"unknown_command"}

Disconnecting cleanly

Before a planned disconnect (a reboot into new firmware, say), publish {"online":false} to status yourself, retained. The broker only sends the will when a connection drops without a clean disconnect.