Differences

This shows you the differences between two versions of the page.

--- en:mervis-scada:82-iot-api [2019/05/17 14:03]
m.chlupac
+++ en:mervis-scada:82-iot-api [2019/05/17 14:11]
m.chlupac [IoT API]
@@ Line 1: / Line 1: @@
 ====== IoT API ======
+You can send measured data to Mervis via several APIs. The IoT API is the most flexible one - you can define custom Levels and Tags to be used for later data processing and Mervis SCADA project generation.
 ===== Simple Example =====
@@ Line 11: / Line 13: @@
    "period": "PT5M",
    "variable": [{
-     "id": "xxxxxxxzzzzzzz",
+     "id": "temperature_1",
      "name": "Temperature",
      "dataType": "float64",
@@ Line 20: / Line 22: @@
      ],
      "level1_txt": "Area 52",
-     "level2_txt": "AHU 89",
+     "level2_txt": "Building A",
-     "level3_txt": "Building A",
+     "level3_txt": "AHU 89",
      "level4_txt": "Floor 7",
      "level5_txt": "Room 12"
     }, {
-     "id": "xxxxxxxzzzzzzz",
+     "id": "relative_humidity_25",
      "name": "RelativeHumidity",
      "dataType": "float64",
@@ Line 34: / Line 36: @@
      ],
      "level1_txt": "Area 52",
-     "level2_txt": "AHU 89",
+     "level2_txt": "Building A",
-     "level3_txt": "Building A",
+     "level3_txt": "AHU 89",
      "level4_txt": "Floor 7",
      "level5_txt": "Room 12"
@@ Line 82: / Line 84: @@
       }
      ],
-     "level1_idx": 3,                              //you can either use Level index to previously defined Levels or
+     "level1_idx": 3,                              //you can either use Level index to previously defined Levels
-     "level2_idx": 1,
+     "level2_idx": 2,
-     "levelX_idx": 2,
+     "levelX_idx": 1,
-     "level1_txt": "Area 52",                      //directly define the Level name
+     "level1_txt": "Area 52",                      //or directly define the Level name
      "level2_txt": "AHU 89",
      "levelX_txt": "Building A",
      "tags": [{                                    //arbitrary array of tags