Skip to main content

Telemetry

While an inventory runs, the reader publishes what it reads as dataEVT: batches of tag records and barcode records. On a dedicated data endpoint, tag data arrives on <tenantId>/DATA/clients/data1event/<deviceSerialNumber>, from the DATA1 endpoint's second publish topic. (DATA2, with data2event, is currently not supported.) It is published at the QoS set on that topic, 0 or 1, is not retained, and is limited to 6144 bytes per message. The contract describes the stream as a statistical view of the tag population, not a guaranteed log of every read.

See Tag Data Stream.

In This Section​

Was this helpful?