Table of Contents |
---|
...
Example
Code Block | ||
---|---|---|
| ||
[{ "processing_level": 0, "sensor_id": "Temperature", "timestamp": "20162019-0108-01T19:02:59.975+0100", 06T13:02:59.975Z", "value": 7 },{ "processing_level": 0, "sensor_id": "Temperature", "timestamp": "2019-08-06T13:03:58.478Z", "value": 11 }, { "processing_level": 0, "sensor_id": "Temperature", "timestamp": "2019-08-06T13:04:59.975Z", "value": 56 },{ "processing_level": 0, "sensor_id": "Temperature", "timestamp": "2019-08-06T13:05:58.478Z", "value": 2250 }] |
Attribute definitions
Attribute name | Data type | Comments |
---|---|---|
sensor_id | String | |
processing_level | String | indicates if there was a problem during the processing on the data. the value will be tagged. 0 mean no problem |
timestamp | String | ISO 8601 (with Timezone Information) in case of an empty string would the server would generate a now() timestamp |
value | Number, String, Boolean |
...
- this sensor is used to display the gateway status
- the gateway should try after a successful connect to the MQTT Broker this message. Only by successfully receiving the acknoledgement it can be assured that next messages can be published. (access security might appear)
- use events with state: "CONNECTED"
- on a regular shutdown of the gateway we recommend publishing a state: "OFFLINE" event
- in order to show a unexpected disconnect we recommend using the MQTT feature lastWillTestament (using an offline payload)
- the timezone information of the timestamp of the CONNECTED message is used to
System Messages
Topic: <orgShortName>/sys_msg/<serial>
...