Problem displaying location data on the Asset Tracker Web app

[kew_flex]

Hi, I'm having trouble displaying the location data on the Asset Tracker Web app. I am able to connect the device and under "Asset Information" can see the devices information including cell area, cell ID and MCC code. As seen in the screenshot the error "column 'source' does not exist." Is this to do with the historical data table not having enough columns to store the location data or something similar?

Another error is the 409 error on the get request. Im not quite sure what this means so some help on this would be great as well. 

A pointer in the right direction would be helpful. 

[Markus Tacker (he/him)]

Which version of the nRF Asset Tracker are you using?

The 409 for the location API means that the resolution is in progress. Check the execution of the singleCell State Machine in the AWS console to see the details of the resolution.

[kew_flex]

I am using v41.0.0. I have updated my nrf service token and redeployed and it seems to have fixed something. I am now getting the following console error: 

I am located in ap-southeast-2 region (Sydney area) and I understand that the asset tracker does not work in every region, could the be the reason for the Geolocation for cell not found error? 

[kew_flex]

Hope this is helpful

[Markus Tacker (he/him)]

Further below on the page are the event logs. Click on link to the Log Group for the one that failed and inspect the logs of the lambda function. There you should be able to learn more about why this resolution failed.

[kew_flex]

This is the logs of the execution. The failed event has no log as you can see. Below is the log from the last step function that is called (Cache Result (not resolved)) 

However, this is the log from the step function resolve using nrf cloud API 

How can I fix the key pair? A link to a guide/steps would be great

Thanks

[Markus Tacker (he/him)]

Thanks, this happens if you haven't provided the location service key, as documented here: https://nordicsemiconductor.github.io/asset-tracker-cloud-docs/saga/docs/aws/GettingStarted/nRFCloudLocationServices.html

[kew_flex]

I thought I had done this. Just to confirm, this is the location of my location service key

I got my team ID from the 3 drop down bars->Team and located at the top. I used 

./cli.sh configure thirdParty nrfcloud teamId your team ID 

to configure the team ID. 

I then copied the service key from above and used 

./cli.sh configure thirdParty nrfcloud serviceKey CopiedKeyFromAbove

to configure the key.

Is this the wrong way to do this? If so, what's the correct way. Sorry Ive never done anything like this before

Edit: I also have configured the proxy server settings to include 1 device

[Markus Tacker (he/him)]

It's best if you copy the key to a file called `serviceKey.txt` and then run the configuration like this:

cat serviceKey.txt | ./cli.sh configure thirdParty nrfcloud serviceKey

[kew_flex]

Okay I have done that, then followed the instructions again from that point including redeploying the web app. The problem is the exact same as before. I am very unsure as to what else I could be doing incorrectly to continue this error. 

Is there a way for me to check the key is being set properly?

[Markus Tacker (he/him)]

It will take a while (15-30 Minutes) for the Lambda to restart and pick up the changed service key.

By now you can start a new execution of the step function execution with the same payload and see if it works:

 

[kew_flex]

Okay I have waited over the weekend and getting the same error. I see your state machine graph is different to mine, are we using different versions? 

I also just wanted to check the input to the SM. The input to the very start is 

{
"area": 18141,
"cell": 587385,
"mccmnc": 53005,
"nw": "ltem"
}

Is this even the correct details the SM should recieve?

[Markus Tacker (he/him)]

Yes, these infos can be resolved using the https://api.nrfcloud.com/v1/location/ground-fix as body

{
  "lte": [
    {
      "mcc": 530,
      "mnc": "05",
      "eci": 587385,
      "tac": 18141
    }
  ]
}

to

{
  "lat": -36.87313199,
  "lon": 174.7577405,
  "uncertainty": 510,
  "fulfilledWith": "SCELL"
}

Can you check the execution logs, if the error still persists?

If that is the case, can you show make a screenshot of the result of calling the cli with the keyfile (please regenerate the key after that and configure it again so you do not share a working key).