This guide provides instructions on how to configure an 8-channel Dragino LoRaWAN gateway such as the LPS8 or DLOS8 to work with the Helium network.
Prior to configuring your Dragino to work with the Helium network, please confirm that it is connected to the Internet and updated to the latest firmware. Refer to the user guide provided on the Dragino download site for more detailed instructions.
- Connect to a Wi-Fi or Ethernet network with Internet access.
- Update to the latest firmware from
recommended by Dragino, leave "Preserve Settings" unchecked when upgrading
firmware to avoid issues caused by incompatibility of settings between
versions. This guide assumes the standard firmware version v5.4.1618196981 or
later. Earlier firmware versions may require ca-bundle to be installed prior
to gateway-rs (via SSH:
opkg install ca-bundle). Note, the OpenVPN firmware may be used however port numbers may differ from what's included here.
- Change the root password from the default of 'dragino', if desired.
Configure LoRa Frequency Plan
To be able to send and receive LoRa data, your gateway must be configured to the frequencies specified for your region. You may be able to use the predefined frequency in the Dragino or some cases may need to manually set them per the frequencies used by Helium in your region.
- Log into the Dragino gateway web interface. In the standard Dragino firmware
connect via your browser at
http://<ip_address>:8000once the Dragino is connected to your network.
- Navigate to Lora > Lora from the Menu.
- Under Radio Settings, select your region in the Frequency Plan drop down and, if applicable, the Frequency Sub Band. For example, in the US, select US915 for the frequency plan and 2 for the sub band.
- If desired, set Static GPS coordinates.
- Click Save & Apply.
For some regions, it my be necessary to manually populate Populate the Customized
Channel Settings based on the Helium frequencies for your region. Refer to the
Helium sample LoRa packet forwarder global.conf files for your region as a
guide to the values to use. You can check the values used by the pre-defined
frequency plans by viewing the global_conf.json file:
Example of customized channel settings using the US915 frequency plan for Helium
Configure LoRaWAN Settings
Next, you will configure the LoRa packet forwarder on the Dragino to forward packets to the Helium Gateway service which will be installed on the Dragino in the next step.
- From the Dragino web interface, navigate to LoRaWAN > LoRaWAN from the menu.
Custom / Private LoRaWANfrom the Service Provider.
- Set the Server Address to
127.0.0.1and both Uplink and Downlink ports to
1680. This will configure the forwarder to use the default port used by Helium Gateway.
- Click Save & Apply.
Install Helium Gateway (gateway-rs) on the Dragino
Finally, you will install the Helium Gateway service. This requires SSH access to the Dragino.
- Connect to the Dragino over SSH. By default, the standard Dragino firmware
uses port 2222 for SSH (the OpenVPN firmware uses port 22) and the root user
ssh root@<ip address> -p 2222
- Copy the Helium Gateway package to the Dragino. The latest
source code and pre-built
releases are available on
Option 1: Download from GitHub: On the Dragino run
wget -O helium-gateway-<version>-dragino.ipk https://github.com/helium/gateway-rs/releases/download/<version>/helium-gateway-<version>-dragino.ipk. Option 2: Copy from another computer: Run this command from on the computer within the directory containing the package
scp helium-gateway-<version>-dragino.ipk <dragino ip>:/tmp/.
- Install the Helium Gateway package
opkg install /tmp/helium-gateway-<version>-dragino.ipk.
- Backup your key file
/etc/helium_gateway/keypair.binand keep in a safe place. This will be needed to recover this gateway especially if it is onboarded to the blockchain.
Helium Gateway is now installed and should be running. Use the command
helium_gateway key info to view the public key address and animal name of your
Your Dragino gateway should now be setup and forwarding LoRaWAN data traffic to the Helium Network.
Through Helium Console
If you have a LoRaWAN device configured through the Helium Console, you should now see it uplinking traffic through the Dragino gateway. You can verify this by turning on your device within range of the Dragino and looking for traffic in Console associated to the Dragino gateway's animal name.
Note, during the alpha period, the helium gateway service by default routes data traffic to the Staging Router/Console.
Through the System Logs
Use the Dragino system log to verify that Helium Gateway has started. You can
view the log in the web interface or by using logread on the commandline
logread | grep helium_gateway). In the logs, you should see
messages indicating helium_gateway is starting. If you do not see these, try
restarting the service (
/etc/init.d/helium_gateway restart) or reboot the
Dragino as the messages may have rotated out of the log.
Example logs showing the Helium Gateway service starting
Thu Mar 25 19:43:06 2021 daemon.err helium_gateway: Mar 25 19:43:06.184 INFO starting server, key: <public key>, version: 1.0.0-alpha.4 Thu Mar 25 19:43:06 2021 daemon.err helium_gateway: Mar 25 19:43:06.289 INFO starting, module: gateway Thu Mar 25 19:43:06 2021 daemon.err helium_gateway: Mar 25 19:43:06.306 INFO starting, module: router
Additionally, the LoRa Packet Forwarder log can provide some clues as to whether
the LoRaWAN server configuration is correct. Search the system log for PULL_DATA
messages and confirm that they are acknowledged such as
REPORT~ # PULL_DATA sent: 1 (100.00% acknowledged). This indicates that the
packet forwarder is communicating with the Helium Gateway service running on the
Dragino and is getting replies from the service as expected. Note, this is not a
foolproof way to confirm it is configured correctly. By default, the LoRaWAN
Server settings are configured for the TTN EU server which will also provide
acknowledgment. However, the absence of acknowledgment could indicate the the
LoRaWAN settings are not correct per the above.
COMING SOON: Onboard as Data-Only Hotspot
As part of Milestone 1.5 of the Light Gateway project roadmap, you will be able to onboard data only hotspots such as the Dragino to appear on the coverage map, and then, in Milestone 2, earn HNT for data transfers (but not for Proof of Coverage). See Light Hotspots - BETA for more information. This process will require using the Helium command-line interface (CLI) Wallet to submit the onboarding and assert location transactions.