Actility is a LoRaWAN network software provider. Actility is a popular choice for large scale public networks. 

Telematics Guru now supports Oyster LoRaWAN data from Actility. For now, it is a uplink only integration. Future support will include:

  • OTA configuration changes via downlinks.
  • Additional product support (Guppy, SensorData, etc)

1. Get access to ThingPark Device Manager

Each network has a separate instance of device manager. This is commonly found at a URL such as

  1. Login to Device Manager.

2. Create the "Application Server"

This defines where the Actility network server should send the data.

  1. Go to Application Servers in the left hand menu.
  2. Click Create. Enter a name and choose the HTTP option: 
  3. Change the Content Type to JSON.
  4. Activate the Uplink/Downlink security. For now, you will need to contact DM support for an AS ID and LRC-AS Key. This will be available in the TG UI in future. Enter the provided details and click Save. Not that this screenshot is just an example - each partner will need a different set of credentials.
  5. Click Add a Route. Source port can be left as *. The strategy is not important, unless you have multiple destinations. Add a single destination in the form:


    Device URL
    Global (old)



  6. Save your Application Server setup with the button in the top right.

3. Create an Application Server Routing Profile

  1. In the left hand menu, click AS routing profiles
  2. Click Create.
  3. Give it a name, such as "TG Oyster". Click Create.
  4. Under Destinations, click Add. Choose Local Application Server as the type. Select the destination you created above.

4. Add your device

  1. In the left hand menu, go to Devices.
  2. To add a new device, click Create.
  3. Fill in the fields in the New Device dialog. Here are some helpful notes:
    1. The Administrative Data section is entirely user selectable. It will not prevent the device from working. Choose a useful name.
    2. Only OTAA is supported. ABP is not supported at this time.
    3. The various keys are available on a sticker that ships with the devices. They can also be found (and copy/pasted) from the config app - this is recommended to avoid typos. The App Key and App EUI may be reconfigured in the config app too. Ultimately, whatever is on the device when deploying should be entered into this dialog.
    4. Dashes are not required in the keys, and case is not important. AC-DE-48-23-45-67-AB-CD is equivalent to acde48234567abcd.
    5. Device profile - LoRaWAN 1.0 class A generally works well.
    6. Your network provider should supply the connectivity plan.
    7. Leave the DevAddr as Allocated by network server, unless you are an advanced user.
    8. Be sure to choose the AS routing profile you setup above.
    9. Editing a device after creation is limited. It does not appear to be possible to change the Dev EUI, App EUI, or AppKey without recreating the device. It is possible to change which Network Routing Profile is assigned to a device. Click the edit icon on the right of the device. In the left hand menu, under the selected device, there should be a network option. Within that page, it is possible to edit "Network Routing".

5. Create your device in Telematics Guru

  1. Login to TG. Go the Manage Assets page. 
  2. Add a new Asset. 
  3. Choose "Oyster LoRaWAN" as the asset type. 
  4. Enter the DevEUI as the serial number.
  5. Click Save.

6. Power up your device

  1. Your device should be ready to power up and join the network.
  2. Try to do this in a location that you know has good network coverage, and in an area with good GPS signal.
  3. Once joined, your should see some statistics for the device, including the last uplink time.
  4. Once the device has obtained a GPS fix, it should transmit an uplink, and it should appear on the live view in TG.

Notes and pitfalls:

  • If you see that the device is transmitting in DeviceManager (Actility), but nothing is appearing on TG, be sure to check with your LoRaWAN network about opening port 8083 for outgoing HTTP traffic.
  • This article covers the standard ThingPark DeviceManager. Some networks have rolled their own simplified interface, with Actility in the background. The setup should be similar, but the UI may look different.