1. Home
  2. LoRa Cloud Geolocation

LoRa Cloud Services have Relocated


Semtech’s LoRa Edge™ technology is now fully supported through our proven network of cloud service providers. Our ultra-low power platform, which integrates the long-range LoRa® transceiver, multi-constellation GNSS scanner, and passive Wi-Fi AP MAC address scanner, has successfully established robust support through industry-leading cloud partners.

Building on existing market momentum, our GNSS solver technology is already licensed to premier cloud partners including the AWS Iot Core Device Location (AICDL) service and Traxmate Cloud for LoRaWAN. These established partnerships deliver enhanced capabilities to our customers, including:

  • Advanced indoor tracking precision

  • Flexible business engagement models

  • Seamless compatibility with existing LoRa Edge deployments

  • Extended service options through multiple providers

Our Join-Server functionality concept has been successfully adopted and is offered by major LoRa Network Server (LNS) partners, providing customers with consolidated service options. The cryptographic key creation and retrieval within the Semtech Join-Server was phased out on July 31, 2025 along with our Join-Server service.

Customers can continue to leverage the LR11xx transceiver’s cryptographic engine for security key management, either during manufacturing or via application code as described in the LR1110 and LR1120 user manuals; however, default cryptographic keys will no longer be programmed by Semtech during the transceiver manufacturing process.

For continuing support, please contact your Semtech sales representative or register a support request through Semtech website.

FAQ-LoRa Cloud Modem and Geolocation Server

  1. Does the LoRa Cloud Modem and Geolocation Server continue to function?

    No. The LoRa Cloud Modem and Geolocation Server has been discontinued.

  2. If my devices were using the LoRa Cloud Modem and Geolocation Server, will I need to migrate to a different Modem and Geolocation Server provider?

    Yes. Today there are two options, Traxmate and AWS IoT Core Device Location.

  3. If my services were calling the LoRa Cloud Modem and Geolocation Server, what changes, if any, are required to ensure continued service?

    You will need to move your service to one of the options available; AWS IoT Core Device Location or Traxmate.

  4. If my services are calling the LoRa Cloud Modem and Geolocation API, what changes do I need to make my application code to adopt Traxmate as my solution partner?

    On your device code: No changes are necessary

    In your cloud app:
1) Contact Traxmate and get an API key (https://traxmate.io/about/contact/)
2) Change the target URL from mgs.loracloud.com to lw.traxmate.io
3) Change the Authorization key for the API from the LoRa Cloud key to the key provided in Step 1

  5. If my services are calling the AWS IoT Core Device Location or embedded location within AWS IoT Core for LoRaWAN service today, what changes, if any, are required to ensure continuity of service?

    None, these services were not impacted by the LoRa Cloud sunset.

  6. I am a user of LoRa Cloud Locator, can I continue to use the service?

    LoRa Cloud Locator has been retired. Please use one of the replacement services at Traxmate or AWS IoT Core Device Location.

  7. What kind of location accuracy and sensitivity performance can one expect when using the LoRa Edge™ technology and a cloud-based geolocation solver?

    For a description of geolocaion performance, please see LoRa Edge Advanced GNSS Scan Performance Overview, AN1200.70.

  8. What is the power consumption of geolocation using the LoRa Edge™ technology?

    For basic information on power consumption, please see the data sheet for the chip you are using. For a description of the power consumption in a standard application such as a tracker, please see the power profiling in the LoRa Edge™ Reference Tracker User’s Manual, AN1200.83.

Created by Richard Fuller, last modified by Richard Fuller on Jul 15, 2025

FAQ-LoRa Cloud Join Server

  1. Will the LoRa Cloud Join Server continue to work after the transition?

    No, the LoRa Cloud Join Server has been discontinued. Devices currently using the LoRa Cloud Join Server must migrate to either the built-in Join Server provided by LoRaWAN network partners or another third-party provider.

  2. If my devices are using the LoRa Cloud Join Server, will I need to migrate to a different Join Server provider?

    Yes. You can use the built-in Join Server that is native to your LoRaWAN network partner’s services or another third-party provider.

  3. If my devices are using the LoRa Cloud Join Server today, what changes, if any, are required to ensure continuity of service?

    If the JoinEUI cannot be set to your current value on the new Join Server, you will need to change the JoinEUI on your device and explicitly set the AppKey on the device and change from CRYPTO mode from "LR11XX_WITH_CREDENTIALS" to "LR11XX".

  4. If I use my own DevEUI, JoinEUI and AppKey/NwkKey in my device, will I be impacted by the Join Server sunset?

    No. You are independent from the LoRa Cloud Join Server and do not rely on its services.

  5. If I use CRYPTO mode "SOFT" or "LR11XX" today on my device, will I be impacted by the Join Server sunset?

    No. You are independent from the LoRa Cloud Join Server and do not rely on its services.

  6. Will I be able to extract device AppKey or NwkKey for my LR11xx?

    No. The ability to access this information is no longer supported.

  7. If I need an AppKey/NwkKey for use on another Join Server, what do I need to do?

    Since the LoRa Cloud Join Server is no longer available, you will need to generate your own random AppKey/NwkKey values for use on another Join Server.