Skip to content

chirpstack-integration.md

Latest commit

 

History

History
20 lines (16 loc) · 1.13 KB

chirpstack-integration.md

File metadata and controls

20 lines (16 loc) · 1.13 KB
Raw

ChirpStack 4 Integration

MQTT is the primary boundary. Subscribe using a least-privilege account, validate event versions, store the original bytes/JSON before normalization, and make processing idempotent. Topic templates are deployment configuration and must be verified locally.

The supplied fixture mirrors the requested snake_case sample, while official ChirpStack integration JSON uses Protobuf JSON conventions in many paths. The parser must eventually support the exact captured payload rather than assume casing. Capture tasks must determine:

  • topic and serialization (JSON versus Protobuf),
  • integration UplinkEvent versus gateway UplinkFrame,
  • field casing and Duration representation,
  • deduplication identifiers and redelivery semantics,
  • presence of fine_time_since_gps_epoch / fineTimeSinceGpsEpoch.

nsTime, gwTime, concentrator context, and Fine Timestamp must remain distinct. ChirpStack v4 integration events defines UplinkEvent; gateway events documents UplinkFrame metadata.