MQTT
Sensors publish to a broker we run.
What it carries
Telemetry in. detections.
Control out. Nothing. This protocol reports and is never commanded.
On this protocol you connect sensors.
Connect one
- Turn the protocol on. Settings → Integrations → MQTT → enable.
- Declare the device. Settings → Assets → ADD, find the product, pick this protocol. You get back a username, a password and a topic, shown once. Put those three on the device.
The address format
This is the form that parses:
| Transport | Form | What it means | Example |
|---|---|---|---|
| MQTT | mqtt:BROKER:PORT/TOPIC | A broker and a topic. For an inbound device the broker is ours, so you do not supply it. | mqtt:127.0.0.1:1883/ingest/TOKEN/# |
When it is working
The sensor appears in Settings → Assets with a live health state, and the Integrations row counts it. On the console, its returns start driving tracks within a few seconds.
If nothing arrives
| Symptom | Where to look |
|---|---|
| Nothing arrives, and the row looks healthy | The device is publishing to the wrong topic. Only the topic issued with the credential is routed; anything else is dropped without an error. |
| It connects, then drops | Two things are bound to the same port, or the device and the host disagree about which end dials. See the endpoint forms above. |
The protocol itself
This one has no public specification to link to.
Where to go next
- All integrations for the protocols this build speaks.
- Onboarding an asset for the add flow in full.
- Supported hardware for the products that use it.