History Export Schema
PreviousCheck Gateway CPU UsageNextAppendix A: JSON Minimum Viable Schema Configuration in the Tridium Jace
Last updated
Last updated
In the event that MQTT communications between the gateway and DCH is interrupted for extended periods, a history upload can be accommodated by DCH using JSON messages containing histories stored by the gateway.
The number timestamps saved in a point’s history will vary depending on the needs of client. History exports
NOTE: There is an important step at the end of this section 12.1 to disable the history json schema object for Tridium Jaces. Do not forget to disable it, or the history export will periodically run.
The message format required is given here and copied in below:
{
"$schema": "http://csiro.au/dch/bms-json/schema-draft-07.json",
"point": {
"pointName": "CS.EC.OFF.AHU 02.HW VALVE",
"currentValue": 0,
"parentName": "AHU02",
"historyData": [
[
"2020-02-26T13:03:18.998+11:00",
3.142
],
[
"2020-02-26T13:08:18.998+11:00",
2.71
]
]
}
}
Within the historyData field are the timestamped historic values for the given point. As with the regular interval upload of point data, DCH requires one message per point.
When communications between the gateway and the DCH broker are restored, a history export can be manually triggered to upload stored data to DCH. Due to the volume of data possible, it is recommended to restrict the upload to the missing portion of data where possible, rather than a full history upload.