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

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

FlareHalo — Sat, 05 Jul 2025 01:16:45 GMT

I had this problem also. After rerouting data to an alternative location, I realized that the payload is very large. The receiving endpoint was truncating the payload making it incomplete.

My only workaround was to effectively proxy the payload via my own service before sending to the final endpoint.

Maybe check if your service accepts very long payloads...

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

Juha-Pekka Kesonen — Thu, 15 May 2025 06:37:51 GMT

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.

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

Clinto — Thu, 15 May 2025 02:00:53 GMT

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?

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

Juha-Pekka Kesonen — Wed, 14 May 2025 13:09:54 GMT

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?

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

Clinto — Wed, 14 May 2025 00:32:11 GMT

any further developments of why the message service routing doesn't work?

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

Clinto — Mon, 12 May 2025 12:56:34 GMT

All message content is not being sent out via Message Routing Service except the test function that is available of the Message Routing Service setup page.

Consistently all messages are empty.

an example message from the message store than comes through empty:

{
        "topic": "prod/xxxxxxxx-xxxx-4f2f-xxxx-5a299abxxxxx/m/d/xx-xxxxxxxxx541592/d2c",
        "deviceId": "xx-xxxxxxxxx541592",
        "receivedAt": "2025-05-09T04:49:20.964Z",
        "message": {
            "appId": "BATTERY",
            "messageType": "DATA",
            "ts": 1746766158744,
            "data": 100
        },
        "tenantId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx98e1"
    },

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

Markku Lehto — Mon, 12 May 2025 08:14:51 GMT

Hi Clinto,

thank you for your patience. I will direct this to internal development team. One more thing to ask, could you give an example of message content that was not sent out via Message Routing Service? So you saw it in message store, but it was sent through Message Routing Service as an empty message. Also, related to this, are you seeing this consistently, so that none of your messages have content, or just some of the messages are empty?

Best regards,

Markku Lehto

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

Clinto — Fri, 09 May 2025 10:06:48 GMT

Thank you for the guidance.

I have confirmed by both methods you described, that messages with data is being received by nrf cloud.

Using the HTTP API I can see a long list of messages with data that have the correct data and also in the portal.

It just never gets passed on the the Message Routing Service for some reason.

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

Markku Lehto — Fri, 09 May 2025 08:01:15 GMT

Hi Clinto,

Before we continue troubleshooting, please confirm from the message store if you can see the message and the content. Are they empty as well?

API, for reference:

https://api.nrfcloud.com/v1/#tag/Messages/operation/ListMessages

Or check from the portal (Device management -> Devices). Choose your device and then you can watch messages as they are delivered to nRF Cloud. Do you see the content there?

Best regards,

Markku Lehto

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

Clinto — Fri, 09 May 2025 05:09:22 GMT

Just wondering if you can provide any further information as to why device messages are not being forwarded by the Message Routing Service?

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

Clinto — Thu, 08 May 2025 04:05:20 GMT

Sure - The screenshot is the log of received http requests at the destination end. Effectively, these are the messages that have been sent by the nrf cloud message routing service.

I am using the Cellular: nRF Cloud multi-service sample to send data from the device to the cloud. nrf cloud is communicating with the device perfectly.

I am not sure what you mean by "type of the message batch (in payload fields)". The data being sent from the device to NRF cloud is as follows:

"Received":{
4 items
appId:"HEARTBEAT"
messageType:"DATA"
ts:1746636363130
data:1
}

"Received":{
4 items
appId:"BATTERY"
messageType:"DATA"
ts:1746636378131
data:100
}

I assume the Message Routing service should be sending a payload like the following example:

{
  "type": "device.messages",
  "timestamp": "2024-09-05T21:59:47.323Z",
  "messages": [
    {
      "teamId": "26fc871f-1272-45ef-9db2-0145a6b0dfcd",
      "deviceId": "nrf-278345628733",
      "messageId": "9b66d97e-9747-4690-a464-073748736603",
      "receivedAt": "2024-09-05T21:59:44.714Z",
      "topic": "dev/26fc871f-1272-45ef-9db2-0145a6b0dfcd/m/d/nrf-278345628733/d2c",
      "message": {
        "appId": "TEMP",
        "messageType": "DATA",
        "data": "14"
      }
    },
    {
      "teamId": "26fc871f-1272-45ef-9db2-0145a6b0dfcd",
      "deviceId": "nrf-278345628733",
      "messageId": "23f5bbc1-2dd8-455e-962a-cad780d469f9",
      "receivedAt": "2024-09-05T21:59:45.306Z",
      "topic": "dev/26fc871f-1272-45ef-9db2-0145a6b0dfcd/m/d/nrf-278345628733/d2c",
      "message": {
        "appId": "GPS",
        "messageType": "DATA",
        "data": "$GPGGA,195032.465,4531.255,N,12240.318,W,1,12,1.0,0.0,M,0.0,M,,*79"
      }
    }
  ]
}

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

dejans — Wed, 07 May 2025 15:24:41 GMT

Hi,

Can you elaborate what exactly is shown in your screenshot?
Where was the screenshot taken from?
Which scheme did you use?
What is the type of the message batch (in payload fields) that you used when empty payload was received at the destination?

Best regards,
Dejan