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-Irene Harvey Sollie]

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

[Jeffery]

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

[Heidi-Irene Harvey Sollie]

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/