Most Sierra Wireless AirLink gateways and routers come with GPS and can report their location to ALMS. In some cases, customers’ devices either do not have a GPS module, they have not attached a GPS antenna, or the device is installed indoors in a location where the antenna cannot see the sky and receive the GPS signal. In these situations, customers may wish to import a fixed location for these devices into ALMS so the devices can be shown on a map, or leverage other ALMS location features.
Any ALMS user familiar with using AirVantage APIs with ALMS can use the APIs to update the location of their devices in ALMS. This page provides an overview of the process.
There are six prerequisites for starting this process.
Download and install Postman
This is the recommended tool for running the API calls, and the files provided have been tested with this product. You are free to use any similar application.
Disable Location Services on the Gateway Configuration
If you do not have an antenna installed on the gateway, be sure to disable Location Services in your device configuration. Any GPS coordinates that are sent from the gateway will overwrite the value you have uploaded. If Location Services are enabled, the gateway will send 0,0 if it cannot get an actual location fix.
Instructions
Populate import-location.csv with your ALMS access token, account UI, the serial numbers and locations of the gateways that require a location.
Set the iteration to equal the number of rows to import (“1” for 1 gateway, “2” for 2 gateways, “100” for 100 gateways etc.).
Run the collection.
Troubleshooting
Location Formats: The GPS coordinates must be in a lat/long file format following the degree decimals convention. Longitude must be between -180 and 180 and latitude between -90 and 90.
Errors in the API Call:Cannot read property 0 of undefined — the system query API failed. This is a very simple API that is called first for each system; the error either means the system (serial number specified in the csv) doesn’t exist in your account or you have a bad access token.