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


The SensorData demo application can receive data from Actility, setup as follows. 


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 https://yournetwork.thingpark.com/deviceManager

  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. Click Add a Route. Source port can be left as *. The strategy is not important, unless you have multiple destinations. Add a single destination:
    https://oem-connector-functions.azurewebsites.net/api/ActilityIngest


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 "SensorData Demo". Click Create.
  4. Under Destinations, click Add. Choose Local Application Server as the type. Select the destination you created above. If your destination doesn't appear, check the content type is JSON, from step 2.3


 

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. View device data on the demo application



Open the Demo Application website http://sensordemo.digitalmatter.com/. From here, enter the DevEUI in the device serial section. Select the desired parameter, and data range, then click 'Submit'. Any data that has been received will show up on the graph, and a list of all the data (with time stamps) below.