Skip to content

IoT

The test-estate safety rule: stand the test estate up only beside a test instance, never a production deployment. Its systems are throwaway test services with published credentials: 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 iot

What it is

An IoT endpoint described by endpoint and protocol. FACE resolves iot to its MQTT connector. In the test estate it carries trailer tag events, door openings included. 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
Typeiot
Settingsendpoint, protocol; and, as properties of the connection, topics, username and use_tls
Credentialspassword

The test connection

Trailer tags

SettingTest value
endpointmqtts://iot.quillmere.invalid:8883
protocolmqtt
topics (property)quillmere/tags/+/event
username (property)face-reader
use_tls (property)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.

An iot connection meets the same security rule as MQTT: a tls://, ssl://, mqtts:// or wss:// endpoint, use_tls on, a username and the credential named password. FACE refuses it otherwise.

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.

  1. Run an MQTT 3.1.1 broker you control, with a TLS listener (port 8883) and password logins, and a face-reader user. Eclipse Mosquitto is one open-source option: give its listener a certfile, keyfile and cafile, and a password_file.

  2. Download messages.jsonl from the recording below and publish it. Each line is one message, in time order: its topic, qos, retain flag and JSON payload. With Mosquitto’s client and jq, over the same TLS listener (ca.crt is 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"
    done
  3. Add the connection in Settings › Integrations › Systems, with endpoint set to mqtts://<host>:8883 and the settings above. FACE subscribes to quillmere/tags/+/event for the collection window.

  4. To watch the events arrive, open Live sensors or Devices from the connection’s card on Ask.

What FACE finds

FACE resolves iot to its MQTT connector. It subscribes for a window and infers the event shape from the payloads.

DatasetKindDomainPrimary keyRowsFields
quillmere/tags/+/eventtopic_filtertelematicsnone487

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 entityFields hereAlso in
devicequillmere/tags/+/event.device_idbigquery, cctv, databricks, files, gps, kafka, mqtt, postgres, rfid, servicenow
shipmentquillmere/tags/+/event.shipment_idbigquery, d365, databricks, document, excel, files, github, guidewire, kafka, logisticsapi, mqtt, mysql, objectstore, postgres, redshift, salesforce, sap, servicenow, sharepoint, tms, whs, yms
trailerquillmere/tags/+/event.trailer_idcctv, databricks, document, excel, kafka, mqtt, postgres, servicenow, tms, yms

Evidence it holds for the planted anomalies:

  • ANOM-3, A reefer temperature excursion. streams/iot/messages.jsonl, look for "device_id":"TAG-102" (door_open mid-transit).

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/iot/, 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.