CODEWITHSUNDEEP
cumulocity
c8yUser
c8yUser

Reputation: 13

smartREST template: custom measurement not visible as Datapoint

I created a smartREST template for measurement via "device management -> smartREST templates". I send the reading via MQTT:

s/uc/mytemplateID
777,123,stringValue

The message arrives because I can see it through the API:

{  
   "time":"2018-07-03T15:36:13.237+01:00",
   "id":"47638",
   "self":"https://myDomain.mydomain/measurement/measurements/47638",
   "source":{  
      "id":"20018",
      "self":"https://myDomain.mydomain/inventory/managedObjects/20018"
   },
   "type":"myType",
   "myStrValue":"stringValue",
   "myNumberValue":123
}

But I can not see it as a data point. I also can not see it under: "device management -> All devices -> myDevice -> Measurements" If the cause is that the incoming message does not have the expected format, then the question is, how can I use MQTT to send custom measurments with the expected format?

Thank you

Upvotes: 1

Views: 372

Answers (1)

l2p
l2p

Reputation: 420

To be able to use Cumulocity standard features on your measurements, they must adhere to a certain standard. Transform your template to create measurements like this:

{ 
   "time":"2018-07-03T15:36:13.237+01:00",
   "id":"47638",
   "self":"https://myDomain.mydomain/measurement/measurements/47638",
   "source":{  
      "id":"20018",
      "self":"https://myDomain.mydomain/inventory/managedObjects/20018"
   },
   "type":"myType",
   "myFragment":{
      "mySeries":{
         "value":123,
         "unit":"aUnit"
      },
      "myOtherSeries":{
         "value":321,
         "unit":"anotherUnit"
      }
   }
}

Note that measurement values are always numeric, using string based values here may cause unwanted behavior again.

If you want to communicate string based status variables sending events or alarms is usually a better approach.

The template configuration to send such measurements should look like this: enter image description here

Upvotes: 3

Related Questions