Message type unknown - Synchronizing with RDMS

[Former Member]

Hi All,

I have just started with SAP - IOT and have run into my first problem .

I am trying to send a message from the device on the HTTP API using the Sample Client ( https://iotmmspXXXtrial.hanatrial.ondemand.com/com.sap.iotservices.mms/#/dataservice/http). But whenever I click on Post button I receive a message saying that the message type X is not available for the device with ID Y .

I have configured the device type , message type and device as shown in the SAP Help document and in the IOT Starter Kit but somehow cannot get past beyond this message .

Can someone help me please .

I am on HANA trial and the message type flow is from the device .

Thanks,

Himanshu

[anton_levin · Accepted solution]

Hi Himanschu,

can you please give more details? Do you replace the default device ID in the URL (first input field in the sample client), what is your payload (how does it look like)?

Regards,

Anton

[Former Member · Accepted solution]

Hi Anton,

Yes . I have replaced the default device ID with that of my device .

Here is what it looks like :

https://iotmmsXXXtrial.hanatrial.ondemand.com/com.sap.iotservices.mms/v1/api/http/data/49259800-fac3...

The message payload looks like this :

{"mode":"async","messageType":"msg1","messages":[{"val" : 10}]}

Message type msg1 is something I have defined and have aligned it with my concerned device type .

However , I still get this message :

[202] {"msg":"Message type [msg1] is unknown for device [49259800-fac3-42c7-9af8-49a3dca32dfb]. Synchronizing with RDMS. Processing delayed"}

If I change the mode from async to sync , I get another message :

[202] {"msg":"https://iotmmspXXXtrial.hanatrial.ondemand.com/com.sap.iotservices.mms/v1/api/http/ack/49259800-fac3...","retryAfterHeaderValue":"60"} 

When I paste the URL https://iotmmspXXXtrial.hanatrial.ondemand.com/com.sap.iotservices.mms/v1/api/http/ack/49259800-fac3... in my browser window , I get the below message :

Access to the requested resource is not authorized (HTTP 401).

Thanks,

Himanshu

[anton_levin · Accepted solution]

msg1 is a message name, in payload you have to specify message ID

[Former Member · Accepted solution]

Awesome . Works fine now .

Thanks a lot Anton