Troubleshooting

This section lists some common errors and possible solutions to them.

Connection

Error code -22

If you see this error code, verify the client ID, the endpoint, and the certificates.

getaddrinfo, error -11

<err> aws_iot: getaddrinfo, error -11
<err> aws_iot: client_broker_init, error: -10

If you see this error, verify that your SIM did not run out of data.

Cellular connection

Since 5G support is currently being deployed by mobile phone network operators, there is a high chance of connection issues in your location.

Try multiple SIM cards from different vendors if you experience connectivity issues.

GPS

Error: GPS_EVT_OPERATION_BLOCKED

This error occurs if the network provider does not grant Power Saving Mode (PSM) and the GPS takes a long time to acquire a fix. For more details, see the DevZone post related to the GPS and LTE issue.

Try switching to a SIM card that grants PSM.

Alternatively, use assisted GPS (A-GPS) to speed up the time to fix.

One form of A-GPS is using SUPL and it can be optionally enabled in the firmware using the SUPL client. The nRF Asset Tracker firmware projects for AWS and for Azure optionally support building the firmware images with SUPL enabled.

Note

A-GPS data is downloaded after every restart of the device and the data is around 30 KB in size.

GPS timeout configuration

Since the firmware does not currently support A-GPS, depending on the device location, it can take a long time to acquire a GPS fix. Therefore, select a timeout of at least 1000 seconds in the web application.