Sample Azure IoT Hub (Thingy9.1)

[ActiTAG]

Hello,

I have the same problem as this topic: https://devzone.nordicsemi.com/f/nordic-q-a/77267/nrf9160-azure-iot-hub-on-thingy91-mqtt-connect-error

I'm using nrf Connect v3.7.1, LTE link monitor v1.1.10. I made the last firmware update 2021-10-20. Sample in the ncs v1.7.1.

Maybe I forgot a step?

Here are the steps I did:

- prj.conf : add the CONFIG_AZURE_IOT_HUB_DEVICE_ID & CONFIG_AZURE_IOT_HUB_HOSTNAME & CONFIG_AZURE_IOT_HUB_DPS=y & CONFIG_AZURE_IOT_HUB_DPS_ID_SCOPE

- certificates.h: change name file and add the ca cert, client key and cert. I add it also with LTE link monitor to be sure.

If you have any useful tips or information, thank you in advance for your help!

Voici mes logs et traces :

trace-2021-11-16T15-37-04.024Z.bin

[Sigurd Hellesvik]

Hi Acti,

Error -111 means that the Azure cloud is refusing your connection.

Have you followed the steps found at our Azure IoT Hub documentation?

Regards,
Sigurd Hellesvik

[ActiTAG]

Hi ! Yes I follow all the step and check it once again but the result is the same. I have a python script on my computer using the Azure SDK that made provisioning and data sending to my IoT Hub. I have the same CA, I create the certificate for the Thingy and upload it with the same sec_tag in the prj.conf. I don't know where to look, I double check all point...

[Sigurd Hellesvik]

Hi

Just to clarify: do you want to use Iot Hub alone, or IoT Hub with DPS?

How are you handling the certificates on the cloud side?

Regards,
Sigurd Hellesvik

[ActiTAG]

I want to use it with DPS, I made an enrollment group with my ca. is there other certificate give to the DPS ? The IoT Hub doesn't expect ca no ?

[ActiTAG]

When I use debugger I see that the MQTT connection failed : 

the client id = <device name> and username = <ID Scope>/registrations/<device name>/api-version=2019-03-31 
Did I forget to set something or maybe add something to Azure?

[Sigurd Hellesvik]

Hi Acti,

I am not able to open your trace. Are you able to open the trace file you added in our Trace Collector (From nRF Connect for Desktop)?

You should have three certificates for the nRF9160: private+key generated from the Tutorial: Using Microsoft-supplied scripts to create test certificates, and a CA, which is the Baltimore CyberTrust Root, right?

Then on the Azure Cloud DPS side, you create a enrollment group which has the  root CA cert generated from the scripts.

To take a step beack, are you able to make Azure IoT Hub work without DPS?

Regards,
Sigurd Hellesvik