Scheme ExtendedDataStreamValueV001
In this format, both metadata and data are sent in a shared message - the distinction between "DataproviderInfo" and "DataStreamValue" as in LM100 format is not available.
Example (temperature sensor)
- {
- "dataProvider": {
- "devEui": "01234567890abcde",
- "lmId": "12345"
- }
- "dataStream": {
- "measurement": "temperature",
- "unit": "centigrade"
- }
- "dataPoint": {
- Timestamp": 1720093923000,
- "value": {
- "value": 38,
- "min": 37.5,
- "max": 38.5
- }
- }
- }
Scheme
The description of the scheme in the form of aJSONSchemacan also be found in the attached files underExtendedDataStreamValue-0.0.1.schema.json
​
dataProvider
{ } | devEui
string | Unique sensor ID assigned by the manufacturer | lmId
string | linemetrics sensor ID |
|
dataStream
{ } | measurement
string | Type of sensor value (e.g. temperature) | unit
string | Sensor value unit (e.g. centigrade) |
|
dataPoint
{ } | timestamp
number | Time stamp of recording the value (Unix timestamp in milliseconds) | value
{ } | value
number | Sensor value | min
number | Min. Sensor value | max
number | Max. Sensor value |
|
|
Related Articles
Scheme LM1.0.0
2 different types of messages are sent: DataProviderInfo Contains basic information about a sensor such as manufacturer/name as well as its inputs or measured values. This message is only sent the first time after activating the sensor, subsequently ...
Webhook
Payload Example {"data": {"dataProvider": {"devEui": "12345abcdef","lmId": "12345"},"dataStream": {"measurement": "temperature"},"dataPoint": {"timestamp": 1704897825000,"value": {"value": 123,"min": 123,"max": 123}}}} Scheme data protection { } ...
Mqtt
The MQTT integration allows sensor data to be received via the Linemetrics MQTT broker (access data is passed when integration is created). Formats The following formats are available when using the MQTT integration: Json ...