How to report data with timestamp - Revision history

Scott68.chang at 06:31, 3 November 2017

2017-11-03T06:31:59Z

2017-11-03T06:22:52Z

2017-11-03T05:23:52Z

2017-11-02T09:18:34Z

2017-11-02T08:51:47Z

2017-11-02T08:48:09Z

2017-11-02T08:47:21Z

2017-10-26T07:04:44Z

2017-10-26T07:04:07Z

2017-10-26T07:03:36Z

@@ Line 143: / Line 143: @@
 		MSG_CLASSIFY_T *myTempGroup = IoT_AddGroup(myCapability, "Temperature");
 		MSG_ATTRIBUTE_T *attrVolt1 = NULL, *attrVolt2 = NULL, *attrTemp1 = NULL, *attrTemp2 = NULL;
-		MSG_CLASSIFY_T *pOPTSNode= NULL;
+		MSG_CLASSIFY_T *pOPTSNode= NULL, *pNode = NULL;
 		MSG_ATTRIBUTE_T* attr = IoT_AddGroupAttribute(myVoltGroup, "bu");
 		if(attr)
@@ Line 164: / Line 164: @@
 		//attr = IoT_AddOPTSNode(myCapability); //supported at MessageGenerator V1.0.4
-		pOPTSNode = MSG_FindClassify(myCapability, "opTS");
+		if(myCapability->type == class_type_root)
 		if(!pOPTSNode)
-			pOPTSNode= MSG_AddJSONClassify(myCapability, "opTS", NULL, false);
+			pOPTSNode= MSG_AddJSONClassify(pNode, "opTS", NULL, false);
 		attr = MSG_FindJSONAttribute(pOPTSNode, "$date");
@@ Line 229: / Line 233: @@
+				}
+			]
+		}
+	}
+}
 </syntaxhighlight>

@@ Line 104: / Line 104: @@
+			}
 		],
-		"bn": "HWM"
+		"bn": "HWM",
-	},
+		"opTS":{"$date":1508998354000}
-	"opTS":{"$date":1508998354000}
+}
 </syntaxhighlight>Report Data Sample with Timestamp
@@ Line 130: / Line 130: @@
+			}
 		],
-		"bn": "HWM"
+		"bn": "HWM",
-	},
+		"opTS":{"$date":1508998354000}
-	"opTS":{"$date":1508998354000}
+}
 </syntaxhighlight>
 === Sample Code ===

@@ Line 177: / Line 177: @@
 			buffer = IoT_PrintCapability(myCapability);
 			printf("IoT Format:\r\n%s\r\n", buffer);
 			free(buffer);
+		}

@@ Line 142: / Line 142: @@
 		MSG_CLASSIFY_T *myTempGroup = IoT_AddGroup(myCapability, "Temperature");
 		MSG_ATTRIBUTE_T *attrVolt1 = NULL, *attrVolt2 = NULL, *attrTemp1 = NULL, *attrTemp2 = NULL;
+		MSG_CLASSIFY_T *pOPTSNode= NULL;
 		MSG_ATTRIBUTE_T* attr = IoT_AddGroupAttribute(myVoltGroup, "bu");
 		if(attr)
@@ Line 163: / Line 163: @@
 		//attr = IoT_AddOPTSNode(myCapability); //supported at MessageGenerator V1.0.4
-		attr = MSG_FindIoTSensor(myCapability, "opTS");
+		pOPTSNode = MSG_FindClassify(myCapability, "opTS");
- 		if(!attr)
+		if(!pOPTSNode)
-			attr = MSG_AddJSONAttribute(myCapability, "opTS");
+			pOPTSNode= MSG_AddJSONClassify(myCapability, "opTS", NULL, false);
 		if(attr)
-			IoT_SetDateValue(attr, "1509611813000", IoT_READONLY);
+			IoT_SetFloatValue(attr, 1509611813000, IoT_READONLY, NULL);
 		if(MSG_IsAttributeExist(myCapability, "Test/Voltage/5V", true))
@@ Line 175: / Line 179: @@
 			free(buffer);
+		}
-</syntaxhighlight>
+</syntaxhighlight>output json:<syntaxhighlight lang="JAVA">{
 	"Test": {
 		"Voltage": {
@@ Line 222: / Line 221: @@
+			]
+		}
+	}
+}
 </syntaxhighlight>

@@ Line 175: / Line 175: @@
 			free(buffer);
+		}
 </syntaxhighlight>

← Older revision		Revision as of 07:04, 26 October 2017
Line 72:		Line 72:

	Capability Sample with Timestamp		Capability Sample with Timestamp
−

	<syntaxhighlight lang="JAVA">{		<syntaxhighlight lang="JAVA">{

@@ Line 43: / Line 43: @@
 </syntaxhighlight>Report Data Sample:
-<syntaxhighlight lang="JSON">{
+<syntaxhighlight lang="JAVA">{
 	"HWM": {
 		"e": [
@@ Line 74: / Line 74: @@
-<syntaxhighlight lang="JSON">{
+<syntaxhighlight lang="JAVA">{
 	"HWM": {
 		"e": [
@@ Line 110: / Line 110: @@
 </syntaxhighlight>Report Data Sample with Timestamp
-<syntaxhighlight lang="JSON">{
+<syntaxhighlight lang="JAVA">{
 	"HWM": {
 		"e": [

@@ Line 8: / Line 8: @@
-<source lang="JSON">{
+<syntaxhighlight lang="JAVA">{
 	"HWM": {
 		"e": [
@@ Line 41: / Line 41: @@
+	}
+}
-</source>Report Data Sample:
+</syntaxhighlight>Report Data Sample:
-<source lang="JSON"> {
+<syntaxhighlight lang="JSON">{
 	"HWM": {
 		"e": [
@@ Line 66: / Line 66: @@
+	}
+}
-</source> In this case, the report data carried&nbsp;timestamp as sensor data. But server process the timestamp as a single sensor data and cannot related to others snesor data. So user cannot query cpu1_volt with timestamp.
+</syntaxhighlight> In this case, the report data carried&nbsp;timestamp as sensor data. But server process the timestamp as a single sensor data and cannot related to others snesor data. So user cannot query cpu1_volt with timestamp.
 === Solution ===