Asset_tracker_v2 with own Cloud End Point (not AWS, AZURE, GCP)

[Rudolph Aschmoneit]

Hey,

I am trying to get the Asset_tracker_v2 running on my Thingy:91, but with my own Cloud connection (It is a Thingsboard CE hosted on an ubuntu Server in Open Telekom Cloud)

So I think i "just" need to write an own libary something like the aws_iot.c/aws_iot.h, but with the specifics of my own cloud solution.

(I I probably also need to write my own version of aws_iot_codec.c and aws_iot_integration later)

But for now, I thougth It would be nice using the cloud_client sample and using my own cloud_lib implementation, when I getting everything running I could use this in the asset_tracker_v2 application in a second step.

Are those Ideas totally nonsens? AnD how I get new libarys in the Kconfig and or the CMakeTree?

Or should I do more something like it is mentioned here: https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/software-and-protocols/posts/how-to-connect-nrf91-to-google-cloud 

it seems more like a only zephy mqtt based approach, and relatively standalone, not fitting in the nrf-cloud libary wrapper. But maybe I am getting some things wrong

Thanks a lot in Advance for any help and/or becoming more clarity

Best Regards

Rudolph

[Hakon]

Hello,

your solution sounds reasonable. You can also consider using the AWS IoT sample and change the broker to your own. That might be preferable to using the cloud_client sample.

[Rudolph Aschmoneit]

Ok thanks for your anwser, I will try this!