Skip to content

First gateway and device

After installing the full ChirpStack stack, you should be able to navigate to the ChirpStack Application Server web-interface.

To access the ChirpStack Application Server web-interface, enter the IP address or hostname of you server, followed by port 8080 (this is a default configuration which can be modified through the chirpstack-application-server.toml configuration file). If you have installed ChirpStack on your local machine this is http://localhost:8080.


The default login credentials are:

  • Username: admin
  • Password: admin

Add a LoRa® gateway

There are two steps involved when adding a gateway. First of all, you need to configure your gateway so that it sends data to the ChirpStack Gateway Bridge component. In the packet-forwarder configuration, modify the following configuration keys:

  • server_address to the IP address / hostname of the ChirpStack Gateway Bridge
  • serv_port_up to 1700 (the default port that ChirpStack Gateway Bridge is using)
  • serv_port_down to 1700 (same)

After restarting the packet-forwarder process, you should see log-lines appearing in the ChirpStack Gateway Bridge logs.

The second step is to add the LoRa gateway to your ChirpStack Server network. For this, log in into the ChirpStack Application Server web-interface and add the gateway to your organization. In case your gateway does not have a GPS, you can set the location manually.

Setting up your first LoRaWAN® device

Add network-server

In order to connect your ChirpStack Application Server instance with the ChirpStack Network Server instance, click Network servers and then Add. As the ChirpStack Network Server is installed on the same host as the ChirpStack Application Server in this guide, use as network-server name (port 8000 is the default port used by ChirpStack Network Server, this can be modified through chirpstack-network-server.toml).

Note that the LoRa App Server can connect to multiple LoRa Server instances. For example each LoRa Server instance could support a different region.

Service Profile

The service-profile defines the features that can be used by an organization.

Click on Service-profiles and then Create to create a service-profile for the ChirpStack organization. This will also associate the organization with the network-server instance.

Device Profile

The device-profile defines the device properties of a device. For example it defines the activation type (OTAA vs ABP), the implemented LoRaWAN version etc...

Click on Device-profiles and then Create to create a device-profile for the ChirpStack organization.


Now that there is a ChirpStack Application Server / ChirpStack Network Server association, a service-profile for the organization and device-profile, it is time to create your first application.

Click on Applications, then click on Create.

Next, click on the created application to see the list of devices associated with this application. This will be an empty list until you complete the next step...


Click on the Devices tab (found under Application/YourApp if you aren't there already), then click on the Create button to create a new device.

After the creation of an Over the Air Activation (OTAA) device, you will be redirected to a page where you can enter the root key(s). After the creation of an Activation By Personalization (ABP) device, you will be redirected to a page where you can enter the session keys. The selected Device Profile that was created in the steps above determines whether the device uses OTAA or ABP.

Check that you are receiving data

It is possible to stream all LoRaWAN frames (raw and encrypted data) and device data from the web-interface. Click on the created device and click on the live data or LoRaWAN frames tab. Now it is time to turn on your device and start receiving data!

Besides seeing the data in the web-interface, you can also subscribe to the MQTT topic to receive data, for example using the mosquitto_sub utility:

mosquitto_sub -v -t "#" -h localhost -p 1883


  • -v - verbose output - includes the topic of the message
  • -t "#" - any message. "#" is a multi-level wildcard. Other possibilities include:
    • "gateway/#" - any gateway messages
    • "application/#" - any application messages
  • -u - The user to log into mosquitto with
  • -P - The password for the user
  • -h - The host to log in to
  • -p - The mosquitto port

Read more more about sending and receiving data in the ChirpStack Application Server documentation.

In case you don't see any data confirm (in the logs) that: