nRF Cloud custom MQTT topics

RE: nRF Cloud custom MQTT topics

Oskar — Fri, 03 Mar 2023 10:19:08 GMT

Okay, I see!

Thank you for your time, I will do some experiments and see how it goes.

RE: nRF Cloud custom MQTT topics

dejans — Fri, 03 Mar 2023 10:06:56 GMT

Hi,

The amount of data you would want to send to nRF Cloud is quite big, and it is currently not supported.

Messages sent to any topic would need to be prefixed with ${mqttTopicPrefix}/m. Therefore, you would need to adjust your topic to ${mqttTopicPrefix}/m/:device_id/:data_format_version/measurements, and probably send data in chunks less than about 350 KB.

There is currently no official support for binary data, and there are no guarantees how this would work in your case. If you want to go this way, you would need to experiment.

Best regards,
Dejan

RE: nRF Cloud custom MQTT topics

Oskar — Thu, 02 Mar 2023 07:21:37 GMT

So I can use any custom topic with the nRF Cloud and it is considered a device message?

I don't think this is quite clear from the documentation as it states: Topics that begin with $aws are AWS reserved topics. All other topics are custom-defined by nRF Cloud.

From how I interpret your response I can set up my devices to transmit to, for example, 04267166-5df8-541d-8dd9-44492dd4af9d/2/measurements and that would work fine, with the possibility of data loss as mentioned in the documentation.

Is this correct?

And on the topic of data loss, I assume the data is only lost from storage and all messages should be received by any subscriber to the MQTT topic(given a correctly configured MQTT QoS)?

RE: nRF Cloud custom MQTT topics

dejans — Wed, 01 Mar 2023 16:24:00 GMT

Hi,

Device messages can be sent either by REST API or MQTT API. Please be aware of potential data loss that can happen in situations mentioned in sending device messages. If your intention is to store data in nRF Cloud, then you should use MQTT Message topics.

Best regards,
Dejan