Customizing Asset Tracker V2 to use nRF Cloud and custom endpoint

[SeaBass]

Hello,

I would like to use the Asset Tracker V2 application with a custom endpoint that is not nRF Cloud, AWS or Azure. Location services, FOTA would go through nRF Cloud. But sensor data needs to be sent to another cloud endpoint also over MQTT.

Is this possible and if yes, what is the best way to go about this?

[dejans]

Hi,

Could you provide more information on how you intend to use Asset tracker v2 application?

Do you have any considerations for the custom endpoint?

How much data do you intend to send and how often?

What type of data do you consider sending to your custom endpoint?

Best regards,
Dejan

[SeaBass]

We would want to sent sensor data (ANT+ and BLE) and location data to an IBM cloud every one minute. Data would be encapsulated in a JSON packet and sent over HTTP or MQTT (preferably the latter). But we would want to retain the connectivity to the nRF Cloud for Fota and location services.

Thanks,

Sebastian

[dejans]

Hi,

In general, this should be possible. Asset Tracker v2 application is designed to use one cloud provider by default, but there is nothing preventing you from adding another cloud provider. In this case, you would need to implement a path for the data from the sensors to json encoding and set up the connection to IBM cloud for sending the data. However, recommended option in terms of power and data consumption would be to have a connection to only one cloud provider and implement cloud-to-cloud communication if you need data transfer between clouds. For example, you could use nRF9160 to connect to IBM Cloud and use location service requests between clouds.

Best regards,
Dejan

[SeaBass]

Thanks.

So to send data to another provider would the apporach be to add another thread that implements an MQTT Client and socket connection?

Sebastian

[dejans]

Hi,

How do you plan to connect BLE devices? Is there nRF91 acting as a gateway?

Best regards,
Dejan