cat tracker app v9.0.13 whitescreen

[Rudolph Aschmoneit]

Hey all!

Today I tested the Asset Tracker App V2 (NCS v1.6.0) with the AWS implementation of the Cat Tracker App.

The rollout was totally fine at the end, and also the App worked well in the beginning: I could register, I could log in, I saw my Thingy device, all the details (modemfirmware, etc), at first there was no historical data, but after a few minutes I also see the charts for all of the tracked values. But after another few minutes, out of nowhere the detail view of the cat (url xxxxxx.cloudfront.net/cat/imei) became a white screen. When reloading it after a few mili seconds, also only a white screen is displayed. 

I have rolled out everything in aws region eu-central-1

The other urls (e.g. xxxxxx.cloudfront.net/cats, url xxxxxx.cloudfront.net/cats-on-map, xxxxxx.cloudfront.net/about) and also the help works fine.
This happens with

Chrome Version 91.0.4472.114, Firefox 88.0.1 and Safari Version 14.1.1 on a MacOs Big Sur 11.4 

Any suggestions where to start to repair the app or database connection or a hint what the error could be or how I could find it would be totally awesome!

Thanks a lot in Advance & have a nice weekend!

Best regards
Rudolph

[Markus Tacker (he/him)]

You found one of the open bugs in the app, which I have observed: https://github.com/NordicSemiconductor/asset-tracker-cloud-app-js/issues/319

Your logs also shows that the app does not handle unexpected values properly and needs to be improved.

Could you provide your device's shadow?

[Rudolph Aschmoneit]

Hey, thanks for your reply.

Cause I am a totally AWS newbie I am a little bit unsure if I get your question right, give you the logs from nrf LTE Link Monitor or if there is some place in the aws console where I can see the device shadow? And you want that?

What I get from the nrf LTE Link Monitor:

CLOUD_WRAP_EVT_DATA_RECEIVED[0m
2021-07-06T12:04:07.095Z DEBUG modem << Decoded message:
                                        {
                                        }
2021-07-06T12:04:07.096Z DEBUG modem << [00:00:34.623,901] [1;33m<wrn> cloud_module: Device configuration empty![0m

...
...
...

2021-07-06T12:04:07.118Z DEBUG modem << [00:00:34.687,164] [0m<dbg> modules_common.module_get_next_msg: data module: Dequeued CLOUD_EVT_CONFIG_EMPTY[0m
2021-07-06T12:04:07.259Z DEBUG modem << Encoded message:
                                    {
                                        "state":{
                                            "reported":{
                                                "cfg":{
                                                    "act":true,
                                                    "gpst":60,
                                                    "actwt":120,
                                                    "mvres":120,
                                                    "mvt":3600,
                                                    "acct":10
                                                    }
                                                }
                                            }
                                    }


...
...
...

2021-07-06T12:05:18.431Z DEBUG modem << [00:01:45.990,112] [0m<dbg> modules_common.module_get_next_msg: data module: Dequeued DATA_EVT_DATA_READY[0m
2021-07-06T12:05:18.538Z DEBUG modem << Encoded message:
2021-07-06T12:05:18.539Z DEBUG modem << {
2021-07-06T12:05:18.540Z DEBUG modem <<     "state":{
2021-07-06T12:05:18.541Z DEBUG modem <<         "reported":{
2021-07-06T12:05:18.542Z DEBUG modem <<                 "dev":{
2021-07-06T12:05:18.543Z DEBUG modem <<                     "v":{
2021-07-06T12:05:18.545Z DEBUG modem <<                         "band":20,
2021-07-06T12:05:18.546Z DEBUG modem <<                         "nw":"LTE-M GPS",
2021-07-06T12:05:18.547Z DEBUG modem <<                         "iccid":"XXXXXXXXXXXXXXXXXX",
2021-07-06T12:05:18.548Z DEBUG modem <<                         "modV":"mfw_nrf9160_1.3.0",
2021-07-06T12:05:18.571Z DEBUG modem <<                         "brdV":"thingy91_nrf9160",
2021-07-06T12:05:18.573Z DEBUG modem <<                         "appV":"0.0.0-development"
2021-07-06T12:05:18.574Z DEBUG modem <<                         },
2021-07-06T12:05:18.575Z DEBUG modem <<                      "ts":1625573046608
2021-07-06T12:05:18.576Z DEBUG modem <<                     },
2021-07-06T12:05:18.578Z DEBUG modem <<                 "roam":{
2021-07-06T12:05:18.580Z DEBUG modem <<                     "v":{
2021-07-06T12:05:18.581Z DEBUG modem <<                         "rsrp":22,
2021-07-06T12:05:18.583Z DEBUG modem <<                         "area":XXXXX,
2021-07-06T12:05:18.583Z DEBUG modem <<                         "mccmnc":XXXXX,
2021-07-06T12:05:18.585Z DEBUG modem <<                         "cell":XXXXXXXXX,
2021-07-06T12:05:18.586Z DEBUG modem <<                         "ip":"XXX.XXX.XXX.XXX"
2021-07-06T12:05:18.588Z DEBUG modem <<                         },
2021-07-06T12:05:18.589Z DEBUG modem <<                     "ts":1625573046729
2021-07-06T12:05:18.590Z DEBUG modem <<                     },
2021-07-06T12:05:18.591Z DEBUG modem <<                 "env":{
2021-07-06T12:05:18.594Z DEBUG modem <<                     "v":{
2021-07-06T12:05:18.596Z DEBUG modem <<                         "temp":32.310000000000002,
2021-07-06T12:05:18.597Z DEBUG modem <<                         "hum":37.494999999999997
2021-07-06T12:05:18.598Z DEBUG modem <<                         },
2021-07-06T12:05:18.599Z DEBUG modem <<                     "ts":1625573046512
2021-07-06T12:05:18.600Z DEBUG modem <<                     },
2021-07-06T12:05:18.602Z DEBUG modem <<                 "bat":{
2021-07-06T12:05:18.603Z DEBUG modem <<                     "v":4351,
2021-07-06T12:05:18.604Z DEBUG modem <<                     "ts":1625573046863
2021-07-06T12:05:18.605Z DEBUG modem <<                     }
2021-07-06T12:05:18.605Z DEBUG modem <<                 }
2021-07-06T12:05:18.606Z DEBUG modem <<             }
2021-07-06T12:05:18.607Z DEBUG modem << }

[Markus Tacker (he/him)]

You can see the entire shadow in the AWS IoT browser console: IoT core > Manage > Things > Thing > Device Shadows.

However you can export it from your console as well:

aws iot-data get-thing-shadow --thing-name <thing name> shadow.json

The shadow.json then contains the thing shadow.

[Rudolph Aschmoneit]

Ok, sorry for the missunderstanding and thanks for your help. Also sorry for the late reply, I had a sickness last week. 

My Device Shadow is:
 

{
  "state": {
    "reported": {
      "cfg": {
        "act": true,
        "gpst": 60,
        "actwt": 120,
        "mvres": 120,
        "mvt": 3600,
        "acct": 10
      },
      "dev": {
        "v": {
          "band": 20,
          "nw": "LTE-M GPS",
          "iccid": "XXXXXXXXXXXXXXXXXX",
          "modV": "mfw_nrf9160_1.3.0",
          "brdV": "thingy91_nrf9160",
          "appV": "0.0.0-development"
        },
        "ts": 1625573240555
      },
      "roam": {
        "v": {
          "rsrp": 41,
          "area": XXXXXX,
          "mccmnc": XXXXXX,
          "cell": XXXXXXXX,
          "ip": "XXX.XXX.XXX.XXX"
        },
        "ts": 1625581751394
      },
      "env": {
        "v": {
          "temp": 30.54,
          "hum": 49.016
        },
        "ts": 1625581751318
      },
      "bat": {
        "v": 4167,
        "ts": 1625581751508
      },
      "gps": {
        "v": "$GPGGA,111712.57,51XX.XXXX7,N,012XX.XXXX6,E,1,05,1.87,158.73,M,,M,,*79\r\n",
        "ts": 1625570232007
      }
    }
  }
}

or do you need the data a little bit less anonymized)?

[Markus Tacker (he/him)]

The problem here is that the device is reporting GPS in the wrong format, that is happening because recently the configuration for the firmware changed. There is now more configuration needed, because the nRF Connect for Cloud backend has been made default: https://nordicsemiconductor.github.io/asset-tracker-cloud-docs/v1.6.x/docs/aws/GettingStarted/FirmwareConfiguration.html

To send GPS in the format support by the web application, disable sending it as NMEA strings:

# CONFIG_GPS_MODULE_NMEA=y

[Rudolph Aschmoneit]

Oh, This one line slipped through. I have changed the Firmware now. But also after several hours in active mode I can't see any changes in the GPS Domain of the AWS IoT device shadow, so do you suggest to roll out everything on the aws side from start? Thanks a lot.

[Markus Tacker (he/him)]

Can you check the device logs? You should see what it is sending to the cloud.

[Rudolph Aschmoneit]

Hey, sorry for late reply, illness was still going on. Problem was, that the device was not sending GPS (because of indoor) and so there was no update in the device shadow. Now I was trying it outdoors, device sending GPS, device shadow was updated, cat tracker Application works fine!

Thanks very, very much for all your help and sorry for being a bit lame here

[Markus Tacker (he/him)]

No problem! Great to hear that it's now working as expected...