Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Digital Matter Site
  • Contact Us

Setting up a Yabby Edge LoRaWAN device via ChirpStack

Written by Matthew Clark-Massera

Updated at February 3rd, 2023

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Contact Support
  • Home
  • Devices
  • LoRaWAN®
  • Yabby Edge LoRaWAN®
  • Integration

Table of Contents

1. Setup your Yabby Edge LoRaWAN devices using the LoRaWAN Provisioning Tool 2. Setup the API Credentials on OEM 3. Add your integration in ChirpStack 4. Add application server security details on OEM 5. Create a Forwarder on OEM 6. Set the Location Engine Lookups and Forwarder

1. Setup your Yabby Edge LoRaWAN devices using the LoRaWAN Provisioning Tool

The LoRaWAN provisioning tool can be downloaded here.
Please see Yabby Edge LoRaWAN - Configuration and Usage.
Note: It is important to configure the Region and Scanning parameters.

2. Setup the API Credentials on OEM

Navigate to the 'Manage' dropdown on OEM and click on 'API Credentials'. Select 'New' and generate the API key. Once created the key can be copied. Both Key 1 and Key 2 will need to be generated to save the API credentials. Once both are generated, select 'OK' to save them.

3. Add your integration in ChirpStack

An HTTP integration will need to be set up to send device data to the location engine to resolve the location. You will need to send the data to our Location Engine in a ChirpStack format and also be able to receive downlinks that get sent back down to the device. This integration would be done on your side. 

ChirpStack Downlink format: https://www.chirpstack.io/application-server/api/http-examples/ 

ChirpStack Uplink format: https://www.chirpstack.io/application-server/integrations/events/#up 

The Base URL: https://oem-event-processors.azurewebsites.net/api/LoraChirpStack
Header will need to be input at Authorization
The value will be Bearer and then the API Key generated in Step 2 above. 

4. Add application server security details on OEM

  1. Navigate to 'Manage' dropdown on OEM and click on 'LoRa Network Credentials'
  2. Click 'New' to create a new entry
  3. Select the relevant Distributor/Vendor/Client
  4. Enter a name for the network credential entry
  5. Select 'ChirpStack' from the LoRa Network Code dropdown
  6. Enter the API token and API URL from ChirpStack

5. Create a Forwarder on OEM

This step is only relevant if you need to forward data to your own platform. Forwarders for Telematics Guru are already created.
A Forwarder is an HTTP connector which allows the Location Engine to forward the "solved" device data to an end platform. Browse to Forwarders on OEM and click 'New'.

6. Set the Location Engine Lookups and Forwarder

Browse to LoRa Devices on OEM and select your devices.

  1. Click on 'Device Operation' and 'Set Network Credentials'. Select the entry you created in Step 4.
  2. Click on 'Device Operation' and 'Set Location Engine Lookup Settings'. Select Default Profile. This profile will cover 99% of use cases. Test on this profile initially, if you have specific requirements, speak to your support team to have the profile adjusted if this is required.
  3. Click on 'Device Operation' and 'Select Forwarder'. Select the TG forwarder for your region or the entry you created in Step 5. 
chirpstack yabby edge

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Setting up a Yabby Edge LoRaWAN Device via LoRIot
  • Setting up a Yabby Edge LoRaWAN Device via TTN (v3) and TTI
  • Setting up a Yabby Edge LoRaWAN Device via Actility (ThingPark Wireless and ThingPark Enterprise)
  • Setting up a Yabby Edge LoRaWAN Device via Everynet

Subscribe to Partner News

Subscribe to our mailing list to receive Digital Matter news, product and tehnical updates, and more.

Subscribe

Copyright © Digital Matter . All Rights Reserved.

Privacy Contact Support

Knowledge Base Software powered by Helpjuice

Expand