Messages data model
Summary
Live Objects platform relies on message processing to provide services such as data storage, event detection, and device management. Messages are ingested via HTTPS APIs and MQTT(S), and can be viewed or delivered through the web portal and webhooks. Understanding the platform’s message models is essential to build business use cases.
In Live Objects, a data message carries data sent by devices over supported network connectors (HTTPS, MQTT(S), LoRa®, SMS, …). These messages are stored and may be processed by other services. The data message format is the platform’s standard internal representation for storage, search, processing, and routing; even if devices publish connector-specific payloads, Live Objects normalizes them before storage.
-
Under certain conditions, the data message can be enriched by Live Objects; see Message enrichment section.
-
Devices can also publish encoded data messages that the platform can decode; see Message decoding section.
This chapter provides an overview of the supported models:
-
stored data message format (standard output),
Refer to the dedicated sections for detailed schemas and field semantics.
|
By default, and without message routing, messages are stored in the standard format. When you need to deliver them to a business application or trigger notifications, use the message routing service. In that case, the delivered payload is extended with routing metadata (e.g., rule context, target, delivery info). The detailed routed message format is described in the Message routing chapter and is not covered here. |