Skip to main content

Integrations · Inturai

Inturai

Sensing pods, from their cloud or ours.

What this gives you

What arrivesdetections
What you can sendnothing. This one reports.
What it carriespods

Connect one

  1. Turn the protocol on. Settings → Integrations → Inturai → enable.
  2. Paste the credential the vendor gave you: API token. It is stored as a reference, so it never appears in an exported manifest.
  3. Point the device at us and power it on. It announces itself, and appears at the top of Settings → Assets → ADD under heard, not yet added. Press it to adopt. You are not typing a serial number.

The address format

Inturai runs over MQTT, HTTPS polling. These are the forms that parse:

TransportFormWhat it meansExample
MQTTmqtt:BROKER:PORT/TOPICA 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/#
HTTPS pollinghttps:BASE_URL@POLL_MSA vendor API with no webhook and no stream, read on a cadence.https:api.vendor.com@2000

When it is working

The pod 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

SymptomWhere to look
Nothing arrives, and the row looks healthyThe 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 dropsTwo things are bound to the same port, or the device and the host disagree about which end dials. See the endpoint forms above.
Rejected on connectThe credential is wrong or has been rotated by the vendor. Reissue it and update the field.
It never appears as heardDiscovery is off on this link. It is off by default, so nothing is adopted until you say so.

The protocol itself

This one has no public specification to link to.

Where to go next