NRF Cloud Message Routing Service not sending payload in device data message

Hi,

I have set up a destination in the the NRF Cloud Message Routing Service

The destination has been verified and I can successfully send the test message from NRF Cloud and receive the message and payload at the destination. All good there.

However, when my devices send data to NRF Cloud, NRF Cloud forwards the message to the configured destination without a payload. I can seen the message being received at the destination by no JSON.

Example of received test message and device data (empty)

When I send a simulated nrf cloud payload - As shown in the Message Routing Service documentation - the destination accepts the message without error.

NRF Clouds also shows there have been 0 message failures

How can I check what data is being sent to the destination? 

Is there any reason why empty payloads are being sent?

Parents Reply Children
  • Hi, I tried to reproduce the empty message with multi service sample but wasn't able to, can you give any more information on the setup and can you see the message logged on the serial terminal when sending the failing message?

  • There is not problem sending data between the device and nrfcloud using the multiservice sample.

    nrfcloud is confirmed to be receiving data from the device and storing the content in the message list (described above)

    test connections sent from nrfcloud Message Routing Service endpoint to the destination work fine - http message received and json payload ok

    The problem is when the device sends a new message to nrfcloud - the Message Routing Service attempts to forward the message to the destination but without the json payload/data (its empty). 

     

    None of the messages are failing as all messages are being sent between all endpoint. The problem is DATA messages are being sent between nrfcloud and the destination with no data.

    Does this help clarify the problem?

  • Is it only some data that isn't being routed, or is none of the data sent by the device routed correctly? What kind of server are you using for your destination? Does it support chunked Transfer-Encoding? Could you provide some more logs of received messages in the destination. 

Related