Questions for Thingy 91

[Jeffery]

Dears

I listed my questions below. Thanks.

1. About GPS searching and fixing, I tried Thingy91 outdoors.

- When Thingy91 connected to LTE, did LED shall blue color?

-  Then, I pressed the button more than 10s, LED became purple color. As user guide said,

   LED will turn green color if GPS fixing. However, I wait half an hour, LED still kept purple color.

   NRF Cloud didn't get GPS data. 

2. For Thingy91, where can I get asset tracker source code of NRF9160,

    and board controller source code of NRF52840? 

3. For recharging battery by USB power, shall I keep SW1 of Thingy91 ON? 

Thanks.    

[Jeffery]

Hi Heidi

At the first time I tried Thingy91, it can be connect to NRF CLOUD with iBASIS or local SIM card.

However, after I tried several examples inlcuding asset tracker and AT client, I found it failed to connect to NRF CLOUD.

At UART log, it shows below and rebooted.

Connected to LTE network
[00:00:02.090,209] [0m<dbg> nrf_cloud_transport.nct_connect: IPv4 Address 0xa4445f03[0m
cloud_connect failed: -111
LTE link disconnect

It seems certificates for NRF CLOUD was lost. Using AT client to send "AT%CMNG=1", it didn't get certificates list.

Previously, I got same problems at DK and used below link to get new certificates successfully.

 https://devzone.nordicsemi.com/f/nordic-q-a/49650/asset_tracker-does-not-work-with-firmware-v1-0-0/199421#199421

But, today, as I sent below httpie request. It became error message returned.  

http POST api.nrfcloud.com/.../<device ID>/certificates Authorization:"Bearer <API key>"

Then, I saw Markus's message. You changed NRF CLOUD API. Now, httpie request must add ownership code(PIN code).

So, I tried new httpie request.

echo -n <PIN code> | http api.nrfcloud.com/.../certificates Authorization:"Bearer <your API key>"

But, it still fail to get certificates.

The IMEI of my Thingy91 is "352656100438087". Can you sent me the certificates for this Thingy91? Thanks.

Besides, I found certificates data was very easy to be lost for unknown reason.

Did others report this phenomenon?

Jeffery

[Heidi]

Hi, what error code do you get when attempting to run the last command?

echo -n <PIN code> | http api.nrfcloud.com/.../certificates Authorization:"Bearer <your API key>"

[Heidi]

Hi! I will try as well, but I will need your PIN.

In the meantime Didrik has a workaround for Windows if you want to try yourself:

echo | set /p=<PIN> | http POST https://api.nrfcloud.com/v1/devices/<nrf_IMEI>/certificates Authorization:"Bearer <your API key>"

[Jeffery]

Hi Heidi

2. I also tried Didrik's workaround. It was found two public client certificates as below. Shall two

    certificates be included in certificates.h?

 

[Jeffery]

Hi Heidi

Besides, shall I deleted this Thingy91 at NRF CLOUD  to work the new certificates/

[Jeffery]

Hi Heidi

My steps for getting new certificates"

1. Used Didrik's workaround for Windows 7 (echo | set /p=<PIN> | http POST ....) 

2. Edit certificates.h for asset tracker example.

3. At prj.conf, set CONFIG_NRF_CLOUD_PROVISION_CERTIFICATES=y.

4. Compiled asset tracker example by SES v4.20a

5. Programmed merged.hex file to Thingy91.

For step 2, since there are two public client certificates generated, I had tried three options: only A, only B and A with B at certificates.h.

However, the results were same. It still cannot connect to NRF CLOUD.

Log message:

cloud_connect failed: -111
LTE link disconnect
Shutdown modem

[Heidi]

Hi again!

Yes, the public certificates belong together. One is the CA public key and the other is the device public key. And you do not have to delete your device from nRF Cloud.

As for your error, I am getting the same one here at the office so I have raised the issue internally and I'll get back to you with an answer or a workaround as soon as possible.

[Jeffery]

Hi Heidi

When run "(echo | set /p=<PIN> | http POST ....) ", I found even I key in a wrong PIN or wrong IMEI.

The certificates data was also generated. Is it normal?

As for error -111, if you have any further information, please let me know.

Thanks.

 

[Thierry_Sirris]

Hi Heidi

I have the same issue as Jeffery with my Thingy:91.

cloud_connect failed: -111 

Everything was fine past week with nrfCloud connection but I have this issue since I turned it on this week. I also tried with different SIM cards to be sure I'm not out of data.

How can this happen ? I heard about a bug which seems to delete the certificates.

Is it possible to send me back the certificates and give me the procedure to re-install them ? As it seems I'm not even able to send AT commands to the device as the device reboots every time just after the cloud_connect failed: -111 message.

I'm going to send you my IMEI and PIN in a separate message.

Thanks,

[Thierry_Sirris]

Heidi

My IMEI is 352656100441651. Can I write my PIN code here too ?

Thierry

[Heidi]

Hi, this is a known issue that they're working on internally.

Unfortunately, I'm not able to generate working certificates here at the office either, so the only solution is to wait until the nRF Connect for Cloud API has been fixed.

You can read the replies in this ticket for more information.

Best regards,

Heidi

[Jeffery]

Hi Heidi

Please see attached certificates.h.

    As you said , first  one is CA public key, I copied this key to #define NRF_CLOUD_CA_CERTIFICATE. Second one is device public key. I copied this key to #define NRF_CLOUD_CLIENT_PUBLIC_CERTIFICATE.

   But, it still got error -111. Anything wrong?

certificates.h