‎2019 Jun 11 11:58 PM - edited ‎2024 Feb 04 2:45 AM
Hello Members!
I have a Thing in Leonardo IoT that is connected to a Device and Sensor in SCP IoT CF. When I push MQTT messages into SCP IoT, I get a data ingestion error log entry in Leonardo IoT of "FAILED_AT_THING_MODEL" "Failed.No metadata found for the source id {MyThingIDHere}/iot.XXXXtest.sap.g020f:M_G020F/IG_MPI0"
Mapping of the sensors appears ok, though my messages do not include anything for the MachineAlarmPST property.
I've been unable to find reference to this specific error and how to resolve it. Thing/Device was pushed into Leonardo IoT and SCP IoT from PdMS.


Request clarification before answering.
For information, I have exactly the same issue. I see my measures in the cockpit, but in leonardo IoT, I do not receive the measures and have the same data ingestion error log.

For info, I do not send with the timestamp property, it is added automatically.
I send with the REST API, with this piece of python code for the format of the json (I tried many different formats as well, without success):
data = json.dumps({
"sensorAlternateId": sensorAlternateId,
"capabilityAlternateId": capabilityAlternateId,
"measures": [{
"Humidity1": 30,
"Humidity2": 26
}]
})
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Dries,
I tried again right now, with the same format of measures as yesterday and this morning, and now it works. I created an incident on the support launchpad yesterday, so I am guessing it is a problem on the platform that was just fixed by the technical team.
Thank you very much for your time.
Jonathan
Hi Jonathan,
I guess you checked it, but just to be sure.
you send it in this way:
{ "capabilityAlternateId": "AltID_mapping_to_IG_MPI0", "sensorAlternateId": "SensorAltID", "measures": [["1","2","3",""]], "timestamp": ""}
But did you try to send the measures without the double quotes and without the timestamp property?
Kind regards,
Dries
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've tested as you suggested and it made no difference.
The Fiori Launchpad of Leonardo IoT was down almost all day today, and as of now is back up. My sensor data now passes correctly to PdMS with no other changes, suggesting it was not on my end.
Thanks for taking a look, Dries.
Hello Jonathan,
I did the same setup.
Also with a mismatch and the null value for the property.
Everything works fine. The only thing where I see a difference is the "unit of measure" in the property set. When I create a new property in the set there is no "MSK" unit of measure available. Could you check if using another unit of measure can fix the problem. The metadata error can be caused by this. Further I see no differences.
Kind regards,
Dries
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dries,
The unit of measure is auto-populated from PdMS, even though it's not available in the Leonardo IoT list. I've tried removing the UoM altogether in Leonardo IoT and this makes no difference. The MQTT messages don't contain the UoM.
I just re-confirmed and got the same metadata error.
-Jonathan
1) Data arrives in the SCP IoT Service Cockpit. I am able to see the data in the Data Visualization tab of the Device

2) Example payload for topic measures/devicealtid
{ "capabilityAlternateId": "AltID_mapping_to_IG_MPI0", "sensorAlternateId": "SensorAltID", "measures": [["1","2","3",""]], "timestamp": ""}
3) See images. Note that these were created automatically by SAP PdMS, and as such are in the REST not the oData Thing Modeler.


You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Jonathan,
Could you please give some more information?
A few questions:
Kind regards,
Dries
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 15 | |
| 9 | |
| 8 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.