'mqttTopicPrefix'

[JackW]

Please explain the structure of the 'mqttTopicPrefix', including the theory of operation.  For example how and when is the 'mqttTopicPrefix' generated and assigned?  Is it unique to each provisioned IoT device?  Wouldn't the device ID itself (IMEI) be sufficient to identify each device?

We need to provision our nRF9160 end user devices  on our own AWS VPC, becuase nRF Cloud won't allow us to implement our unique features, but we want to stick wtih Nordic's topic structure as much as possible, becuase we're leveraging Asset Tracker 2 code in our firmware.

So we're trying to understand how Nordic implements their MQTT messaging so we can implement a similar structure in our AWS VPC, using the AWS MQTT broker.

Thanks

Jack

[Patrick Barnes]

Please see https://docs.nordicsemi.com/bundle/nrf-cloud/page/APIs/MQTT/MQTTOverview.html and related links therein for more info. This will probably address all your questions.

[JackW]

Thanks for the quick reply.

For further clarification, is the 'mqttTopic'Prefix' the same for all devices provisioned on my nRF Cloud instance?  In other words, does the topic prefix serve as an identifier for my nRF Cloud account?

[Patrick Barnes]

Yes. It will always be `prod/<TEAM_ID>/...`, where team id is your nRF Cloud team account identifier.

[JackW]

Got it.  Thx