Questions for Thingy 91

RE: Questions for Thingy 91

Joakim — Fri, 11 Oct 2019 09:58:58 GMT

Hi Jeffery, did you manage to get your Thingy:91 up and running? You should not post your PIN code online!

RE: Questions for Thingy 91

Joakim — Sat, 05 Oct 2019 22:37:01 GMT

Certificates can now be recovered following this guide: devzone.nordicsemi.com/.../nrf-cloud-certificate-update

RE: Questions for Thingy 91

Heidi — Mon, 23 Sep 2019 12:12:07 GMT

Hi, there is a fix now. Please make a new private ticket with this request and I will provide a solution.

RE: Questions for Thingy 91

Jeffery — Mon, 23 Sep 2019 01:29:00 GMT

Hi Heidi

OK. Please update the information to me if the bug was fixed.

Thanks.

RE: Questions for Thingy 91

Heidi — Fri, 20 Sep 2019 07:38:06 GMT

Hi again.

This error (getting error -111 with generated certificates) is known and they are working on a fix internally.

I will update you as soon as I can.

Best regards,

Heidi

RE: Questions for Thingy 91

Jeffery — Fri, 20 Sep 2019 01:44:51 GMT

Or, could you mind generating certificates.h for my Thingy91?

I had a rush schedule to demo Thingy91 to my customer. Thanks.

RE: Questions for Thingy 91

Jeffery — Fri, 20 Sep 2019 01:41:22 GMT

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?

devzone.nordicsemi.com/.../certificates.h

RE: Questions for Thingy 91

Heidi — Thu, 19 Sep 2019 14:23:28 GMT

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

RE: Questions for Thingy 91

Thierry_Sirris — Thu, 19 Sep 2019 14:11:27 GMT

Heidi

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

Thierry

RE: Questions for Thingy 91

Thierry_Sirris — Thu, 19 Sep 2019 14:07:07 GMT

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,

RE: Questions for Thingy 91

Jeffery — Thu, 19 Sep 2019 09:17:25 GMT

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.

RE: Questions for Thingy 91

Heidi — Thu, 19 Sep 2019 09:01:43 GMT

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.

RE: Questions for Thingy 91

Jeffery — Thu, 19 Sep 2019 02:31:21 GMT

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

RE: Questions for Thingy 91

Jeffery — Thu, 19 Sep 2019 02:13:48 GMT

Hi Heidi

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

RE: Questions for Thingy 91

Jeffery — Thu, 19 Sep 2019 02:11:17 GMT

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?

RE: Questions for Thingy 91

Heidi — Wed, 18 Sep 2019 13:00:59 GMT

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>"

RE: Questions for Thingy 91

Jeffery — Wed, 18 Sep 2019 10:36:51 GMT

Hi Heidi

I got error as below. I had asked Dirik. This request command only works in Linux or Mac.

However, my notebook is Windows 7.

Since the certificate data of my Thingy91 was lost and have no way to request new certificates, could you mind

creating certificates data for me? Thanks.

The IMEI of my Thingy91 is "352656100438087".

RE: Questions for Thingy 91

Heidi — Tue, 17 Sep 2019 11:28:38 GMT

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>"

RE: Questions for Thingy 91

Jeffery — Tue, 17 Sep 2019 09:43:20 GMT

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

RE: Questions for Thingy 91

Hoang — Fri, 06 Sep 2019 12:37:37 GMT

Thanks so much, Heidi,

BR,

Hoang Nguyen

RE: Questions for Thingy 91

Heidi — Fri, 06 Sep 2019 12:36:14 GMT

The board controller for the nRF52840 on the Thingy:91 is a pull request found here: 1011. It's not so much a board controller than a USB - UART bridge. The source code is under review but functionally it should be okay.

There is no example code using NFC and BLE for the Thingy yet, unfortunately. However, the libraries are out on the NCS github, so you can develop your own.

RE: Questions for Thingy 91

Hoang — Thu, 05 Sep 2019 11:40:31 GMT

Hi Heidi,

[quote userid="82276" url="~/f/nordic-q-a/51775/questions-for-thingy-91/208192"]and the code for the nRF52840 can be found here[/quote]

Does it contain config and dts files, not the code for nRF52840 ?

I am looking for the code for NFC and BLE on the thingy:91 also, but I think it hasn't come yet.

Thanks,

BR,

Hoang Nguyen

RE: Questions for Thingy 91

Heidi — Thu, 05 Sep 2019 11:34:18 GMT

Hi!

1. You most likely haven't gotten any GPS fixes.

[quote user="hng"][/quote]

thingy:91: outside? far away from the buildings. You can connect THINGY:91 to the serial port to see the report

It took me around 1mn to get the fix ( after find 5-6 satellites). Or you can use external antenna

I recommend following this advice.

2. The asset tracker source code can be found in the nRF Connect SDK under applications, and the code for the nRF52840 can be found here

3. Yes, SW1 must be on for the battery to charge. More information on this can be found here.

RE: Questions for Thingy 91

Hoang — Thu, 05 Sep 2019 07:58:20 GMT

[quote userid="2878" url="~/f/nordic-q-a/51775/questions-for-thingy-91"][/quote]

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.

thingy:91: outside? far away from the buildings. You can connect THINGY:91 to the serial port to see the report

It took me around 1mn to get the fix ( after find 5-6 satellites). Or you can use external antenna

[quote userid="2878" url="~/f/nordic-q-a/51775/questions-for-thingy-91"]2. For Thingy91, where can I get asset tracker source code of NRF9160,[/quote]

cd to ncs/nrf
git fetch origin pull/943/head:joakim
git checkout joakim
west update

here the link

[quote userid="2878" url="~/f/nordic-q-a/51775/questions-for-thingy-91"]and board controller source code of NRF52840? [/quote]

you can find it: nrf9160_pca20035ns

[quote userid="2878" url="~/f/nordic-q-a/51775/questions-for-thingy-91"]3. For recharging battery by USB power, shall I keep SW1 of Thingy91 ON?[/quote]

Yes, I think so

Hope it can help you

Best Regards,

Hoang Nguyen