Paqett docs
Connect a device. Keep it updated.
A Paqett device makes its own key, enrols itself for an X.509 client certificate, talks MQTT over mutual TLS and takes firmware updates over the same session. These docs cover the device side, starting with the ESP32.
device api.paqett.com mqtt.paqett.com:8883
│ EC P-256 key + CSR │ │
├─ POST /v1/devices/provision ▶ cert, CN = device id │
├─ TLS: verify broker, present own cert ─────────────────▶ │
├─ status (retained), hello ─────────────────────────────▶ │
◀─ ota offer (retained) ── signed HTTPS image ── confirm or roll back Guides
Step by step, from a bare board to a working device.
- ESP32 MQTT over mutual TLS with an X.509 client certificate Give an ESP32 its own P-256 key, build a CSR with mbedTLS, enrol for an X.509 client certificate and connect esp-mqtt to MQTT over mutual TLS.
- ESP32 OTA updates over MQTT, with automatic rollback Update ESP32 firmware over MQTT with a signed HTTPS download into the spare OTA slot, a SHA-256 check, a trial boot and automatic rollback on failure.
Device reference
The contract between a device and the platform.
- How IP devices connect to Paqett How a device with its own IP connection enrols for an X.509 client certificate, talks MQTT over mutual TLS to Paqett and takes OTA firmware updates.
- Provisioning API: enrol a device for an X.509 certificate POST /v1/devices/provision turns a device's CSR into an X.509 client certificate for MQTT over mutual TLS. Fields, responses, errors and re-keying.
- 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.
- OTA updates: offers, downloads, status and rollback The OTA contract for Paqett IP devices: the retained MQTT offer, the signed HTTPS image URL, the device's rules, ota_status reports, jobs and releases.