Hello all, Lakshmi here, from India. Backend developer in logistics, 21 years in the trade, which makes me feel old typing it.
We run our own MQTT broker and a Postgres database for container and truck telemetry: position, door state, reefer temperature. The broker has turned into a part-time job for two people. I’m looking at moving the device side to Hermetry and keeping our analytics where they are, so my questions will be about getting data in reliably and getting it back out in bulk.
Welcome Lakshmi. For a regular extract into your own store, the History API called by your scheduler is the usual route. If you want every reading in real time instead, a forwarding block in the root flow sends them on as they arrive. Exporting data compares the options.
Trucks lose signal a lot. If a device buffers and sends its readings an hour late, do they land at the time they were taken?
Yes, if the device sends its own time. A message like {"ts": 1759572000000, "values": {...}} is stored at ts, in milliseconds since 1970 UTC. A flat object is stored at the time it arrived. Two things to watch: a record more than 10 minutes in the future is refused as bad_ts, so keep the clocks synced, and an admin can set an oldest accepted age. Details on Timestamps, late and duplicate readings.
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.
Mitdiskutieren
Melde dich an, um Fragen zu stellen und zu beantworten, hilfreiche Beiträge mit „Gefällt mir“ zu markieren und die Antwort zu kennzeichnen, die dein Problem gelöst hat. Jeder Beitrag bringt Punkte und Stufen.