MQTT
change-me is every test credential. They are still encrypted and still ask for a login, because FACE refuses a connection that is not (see Connector security). Use a scratch machine or a scratch cluster.Grade D · dataset: Stream (a timestamped recording) · type mqtt
What it is
An MQTT 3.1.1 broker. In the test estate it carries reefer temperature readings and unit state from the trailers. The connector reference is Telemetry.
Grade
D. Dataset and model: the quickstart dataset and its expected model ship. There is no vendor system to stand up for this type; load the dataset and fetch it.
See the grade table for all 32 types.
Settings and credentials
From the connection catalogue. Settings are ordinary fields on the connection record. Credentials are kept in a sealed bundle and never returned.
| Names | |
|---|---|
| Type | mqtt |
| Other spellings that resolve | mqtts, iothub, sensorbus, messagebus |
| Settings | broker_url, topics, qos, client_id, username, collect_seconds, max_messages, protocol_version, use_tls, insecure_skip_verify |
| Credentials | password |
The test connection
Reefer telemetry broker
| Setting | Test value |
|---|---|
broker_url | mqtts://mqtt.quillmere.invalid:8883 |
topics | quillmere/reefer/+/temperature,quillmere/reefer/+/unit |
qos | 1 |
client_id | face-collector |
username | face-reader |
collect_seconds | 60 |
max_messages | 5000 |
protocol_version | 3.1.1 |
use_tls | true |
Credentials: password. In the test estate, every credential is change-me. Credentials are write-only: they go into the sealed credential bundle and are never returned.
Stand up the test system
The safety rule at the top of this page comes first: a scratch machine or a scratch cluster, never a production or platform one.
Run an MQTT 3.1.1 broker you control, with a TLS listener (port 8883) and password logins, and a
face-readeruser. Eclipse Mosquitto is one open-source option: give its listener acertfile,keyfileandcafile, and apassword_file. FACE refuses a broker without TLS or without a login.Download
messages.jsonlfrom the recording below and publish it. Each line is one message, in time order: itstopic,qos,retainflag and JSONpayload. With Mosquitto’s client andjq, over the same TLS listener (ca.crtis the CA that signed the broker’s certificate, and<host>is the name on it):jq -r '"\(.topic)\t\(.qos)\t\(.retain)\t\(.payload | tojson)"' messages.jsonl | while IFS=$'\t' read -r topic qos retain payload; do if [ "$retain" = true ]; then r=-r; else r=; fi mosquitto_pub -h <host> -p 8883 --cafile ca.crt -u <publisher> -P change-me \ -t "$topic" -q "$qos" $r -m "$payload" doneAdd the connection in Settings › Integrations › Systems, with
broker_urlset tomqtts://<host>:8883,use_tlson and thepasswordcredential. Leaveinsecure_skip_verifyoff: FACE refuses a connection with it on. FACE subscribes toquillmere/reefer/+/temperaturefor the collection window.To watch the readings arrive, open Live sensors or Devices from the connection’s card on Ask.
What FACE finds
MQTT has no catalogue. FACE subscribes for collect_seconds and infers each topic’s shape from its payloads.
| Dataset | Kind | Domain | Primary key | Rows | Fields |
|---|---|---|---|---|---|
quillmere/reefer/+/temperature | topic_filter | cold_chain | none | 96 | 7 |
quillmere/reefer/+/unit | topic_filter | cold_chain | none | 4 | 4 |
expected.json in the download has the full model: every field with its logical type, the source’s native type and nullability.
How it joins the Quillmere universe
This source carries 3 of the universe’s shared keys. The same ID means the same thing in every source: a shipment here is the same shipment in the database, the event bus, the GPS track and the claim PDF.
| Universe entity | Fields here | Also in |
|---|---|---|
| device | quillmere/reefer/+/temperature.device, quillmere/reefer/+/unit.device | bigquery, cctv, databricks, files, gps, iot, kafka, postgres, rfid, servicenow |
| shipment | quillmere/reefer/+/temperature.shipment | bigquery, d365, databricks, document, excel, files, github, guidewire, iot, kafka, logisticsapi, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms |
| trailer | quillmere/reefer/+/temperature.trailer, quillmere/reefer/+/unit.trailer | cctv, databricks, document, excel, iot, kafka, postgres, servicenow, tms, yms |
Evidence it holds for the planted anomalies:
- ANOM-3, A reefer temperature excursion.
streams/mqtt/messages.jsonl, look for"temp_c":11.40.
See all connectors at once for the walkthrough across every source.
Download
Streams are dialled and held open, so their datasets are replay recordings under streams/mqtt/, not a zip. Download the files, and use them as described above.
The whole universe is universe.json. manifest.json lists every download with its size and SHA-256, and SHA256SUMS is the same list for sha256sum -c.