RUTX50 invalid JSON format

[JorisTurck]

Hi,

I want to send the GPS data from the RUTX50 via Data to Server. This works, but I get an invalid JSON format. At the end of the message it says : “”

{"GPS":{"latitude":xx.yyyyyy,"longitude":x.yyyyyy,"altitude":xx.yyyyyy,"date":"16/09/2025 09:58:52"}}: ""

I tried different settings. In both JSON format and custom format, the : “” appears at the end of the payload.

Because the data in the JSON object is incorrect, it cannot be read properly in our application. Does anyone have any idea how this can be resolved?

[anon65719490]

Hello,

Thank you for reaching out. Your request is currently under review and analysis. Once the evaluation is complete, I will get back to you with an update and further information, findings, or suggestions.

Thank you for your patience.

Best regards,

[anon65719490]

I wasn’t able to replicate the behavior of receiving : “” at the end of the payload when using custom format in Data configuration and either JSON or custom under the Collection configuration tab.

Here are my settings:

And here’s how the sent payload is received on my side:

{"GPS": {"latitude": X.702260, "longitude": Y.258666, "altitude": Z.100000, "date": "16/09/2025 16:38:18"}}

Based on this, I would assume there might be some misconfiguration in the message format on your side. Could you please double-check your format settings, and if the issue persists, share a screenshot of your data to server configuration?

Best regards,

[JorisTurck]

Hi,

Thank you for your response.

Unfortunately, the problem remains on my side.

Here is my configuration:

What I get in Postman Mock server:

It seems to think that there is a value at the end and that the entire payload is a key.

What I get in Node-RED:

[JorisTurck]

Additional information: I tested a second RUTX50 and it gave the same result.

Both on Firmware version: RUTX_R_00.07.16.3

[anon65719490]

Hello,

Apologies for the delay.

I just wanted to ask whether the issue with improper GPS data payload is still relevant or was resolved. From the Postman Mock Server’s payload, it appears that the received data is formatted correctly.

Best regards,

[JorisTurck]

I contacted support via email, and the issue has now been resolved.
The solution was to add Content-Type: application/json under the HTTP header settings in the server configuration.