nRF9160: LTE Sensor Gateway

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Mon, 05 Aug 2019 09:17:01 GMT

Similar to inclusiveStart and exclusiveEnd: <rest_of_url>&pageNextToken=<token>

RE: nRF9160: LTE Sensor Gateway

Marshed — Mon, 05 Aug 2019 08:12:19 GMT

how do you use the token?

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Fri, 02 Aug 2019 13:42:34 GMT

In the response, there is a token for the next page of results, so that you can get more data.

However, I would also take another look at the design of your application to see if you really need to get all the data at once, or if you can get it in smaller chunks as the data becomes available.

RE: nRF9160: LTE Sensor Gateway

Marshed — Fri, 02 Aug 2019 13:09:38 GMT

here i can see that the maximum is 100, what if i want more than 100 what should i do?

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Fri, 02 Aug 2019 12:57:12 GMT

The

Authorization:"Bearer <API key>"

part of the httpie command is not part of the url, but specifies the content of the "Authorization" field in the HTTP header. For how to set this in MATLAB, you should refer to the MATLAB documentation.

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Fri, 02 Aug 2019 12:51:13 GMT

The API call only returns 10 messages by default, however, you can ask for more.

Take a look at http://petstore.swagger.io/?url=https://docs.api.nrfcloud.com/api/api-rest.yaml#/Messages/fetchMessages for more information.

RE: nRF9160: LTE Sensor Gateway

Marshed — Fri, 02 Aug 2019 12:07:28 GMT

the other question is why does this return the last 10 messages only?

RE: nRF9160: LTE Sensor Gateway

Marshed — Fri, 02 Aug 2019 10:01:57 GMT

I am trying to run the same command on MATLAB and i am getting the status 401 again, can you assist?

url = 'https://api.nrfcloud.com/v1/messages?inclusiveStart=2019-08-02T00%3A00%3A00.000Z^&exclusiveEnd=2019-08-03T00%3A00%3A00.000Z Authorization:"Bearer cf3741f41d4717c94700e541aa642e0a263919f9"';

data = webread(url);

RE: nRF9160: LTE Sensor Gateway

Marshed — Fri, 02 Aug 2019 08:21:33 GMT

api.nrfcloud.com/.../messages Authorization:"Bearer cf3741f41d4717c94700e541aa642e0a263919f9"

it works thanks

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Fri, 02 Aug 2019 07:30:09 GMT

Can you send me the full command and the full output?

RE: nRF9160: LTE Sensor Gateway

Marshed — Thu, 01 Aug 2019 15:00:59 GMT

Hey

the reply is still the same

IncompleteSignatureException error

can you assist?

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Thu, 01 Aug 2019 14:37:04 GMT

The messages call requires 2 parameters, inclusiveStart and exclusiveEnd. Both of these are a part of the url, so the url would be similar to this:

https://api.nrfcloud.com/v1/messages?inclusiveStart=2019-01-01T00%3A00%3A00.000Z&exclusiveEnd=2019-08-01T00%3A00%3A00.000Z

However, Windows CMD parses the & (right before exclusiveEnd), so it must be escaped for the url to be read correctly, so your command would be similar to this:

http https://api.nrfcloud.com/v1/messages?inclusiveStart=2019-01-01T00%3A00%3A00.000Z^&exclusiveEnd=2019-08-01T00%3A00%3A00.000Z Authorization:"Bearer <your API token"

Note the ^ before the &

RE: nRF9160: LTE Sensor Gateway

Marshed — Thu, 01 Aug 2019 13:00:47 GMT

Thanks this works fine,

back to REST API, I have been trying to retrieve some messages sent to the cloud using

http api.nrfcloud.com/.../messages exclusiveEnd=2019-08-01T00%3A00%3A00.000Z Authorization:"Bearer cf3741f41d4717c94700e541aa642e0a263919f9"

but I have been getting IncompleteSignatureException error

can you assist

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Wed, 31 Jul 2019 11:59:57 GMT

https://www.computerhope.com/issues/ch000549.htm

RE: nRF9160: LTE Sensor Gateway

Marshed — Wed, 31 Jul 2019 11:54:00 GMT

how can I add openssl in my path environment variable?

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Wed, 31 Jul 2019 11:33:59 GMT

Close, but not quite.

If you look at the script it then parses the private key into the der format and outputs the result in an array in a new C file.

The error from the Python script indicates that it was not able to run openssl. Is openssl in your PATH environment variable? If not, try to add it.

If you are able to run the Python script where you generated the certificates, that should also work (if this is in another folder you would have to copy the output files into the private_info folder).

RE: nRF9160: LTE Sensor Gateway

Marshed — Wed, 31 Jul 2019 07:44:31 GMT

I did that but it gave me this error

so instead I ran these commands on openssl

ecparam -noout -name prime256v1 -genkey -out bolt-001-private.pem

req -new -x509 -key bolt-001-private.pem -out bolt-001-cert.pem -days 1000000 -subj /CN=bolt-001

to create my certificates

was this not a good workaround?

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Wed, 31 Jul 2019 07:32:21 GMT

Did you create your certificates?

In src\private_info there is a python script to create these keys. To do this we used the command below while in the private_info folder. DEVICE_NAME was replaced with the name of our device.

python create_keys.py -d DEVICE_NAME -e

RE: nRF9160: LTE Sensor Gateway

Marshed — Tue, 30 Jul 2019 13:59:48 GMT

this works fine now, but I see in Rest API Docs the code is written in JavaScrip, how to run this on cmd?

RE: nRF9160: LTE Sensor Gateway

Marshed — Tue, 30 Jul 2019 13:41:41 GMT

I have tried to use the link to connect the nRF9160 to Google Cloud, but whenever I compile the code i get this error

undefined reference to `zepfull_private_der' in the gcloud.c

any solutions?

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Wed, 24 Jul 2019 09:23:03 GMT

Hi.

The httpie commands worked for me, are you sure you spelled everything correctly?

Did you follow these instructions to install httpie?

Best regards,

Didrik

RE: nRF9160: LTE Sensor Gateway

Marshed — Tue, 23 Jul 2019 13:25:01 GMT

I have seen the API documentation for nRF Cloud, however there is no instructions on how to use GraphQL, and more importantly I have been getting errors when using REST API.

for example this command

http api.nrfcloud.com/.../account \
  Authorization:"Bearer 67c32a28037d6eddf08d87624f8256fd1999e721"

gives me a missing authentication token. 

can you assist?

RE: nRF9160: LTE Sensor Gateway

Didrik Rokhaug — Mon, 22 Jul 2019 12:38:34 GMT

Hi.

Have you seen the API documentation for nRF Cloud? You can find it if you log in to the cloud, and select "Device API" in the menu on the left side.

According to the API documentation, the messages are persisted indefinitely and can be retrieved using REST and GraphQL.

As it is possible to fetch the stored messages, it should be possible to access the data from other places. It is also possible to send the data directly to your own cloud service.

This link describes how to connect the nRF9160 to Google Cloud, and the nrf_cloud library can be used as a starting point for connecting to your own AWS instance.

Best regards,

Didrik