|
| 1 | +--- |
| 2 | +title: "ChirpStack Setup" |
| 3 | +aliases: |
| 4 | + - chapter/pybytes/networks/lora/chirpstack |
| 5 | +--- |
| 6 | + |
| 7 | +## Overview |
| 8 | + |
| 9 | +When a LoRa device is created or LoRa network is configured in **Pybytes → Settings -> LoRa** the user profile is automatically created at [ChirpStack](https://loraserver.pycom.io/). |
| 10 | + |
| 11 | +## User profile |
| 12 | + |
| 13 | +After creating a LoRa device or configure Pybytes to use ChirpStack, you should receive an email with ChirpStack username and password what you can use for accessing the data on <a href="https://loraserver.pycom.io/"> loraserver.pycom.io</a>. |
| 14 | + |
| 15 | +The basic configurations are made by Pybytes, but if you want to overwrite the LoRa settings, it is possible to use these credentials. |
| 16 | + |
| 17 | +### What is created by ChirpStack: |
| 18 | + |
| 19 | +**Network-server** - Pycom |
| 20 | + |
| 21 | +You can add your own server in the section Network-servers |
| 22 | + |
| 23 | +**User** - Value |
| 24 | + |
| 25 | +The User will be created based on the same credentials that are used in Pybytes and it can be managed in the section Org. Users. At the same place, the Admin status of the user can be changed. |
| 26 | + |
| 27 | +**Organization** - Value (by default) |
| 28 | + |
| 29 | +The Organization Value will be created based on the same credentials used by Pybytes and can be changed in the section Org. Settings. |
| 30 | + |
| 31 | +**Service Profile** - Value (by default) |
| 32 | + |
| 33 | +The Service Profile Name is connected to the Organization’s name. |
| 34 | + |
| 35 | +**Device Profiles** - OTAA or ABP |
| 36 | + |
| 37 | +There are two different devices profiles among which you should select the preferable. |
| 38 | + |
| 39 | +**Applications** - Value (by default) |
| 40 | + |
| 41 | +All devices created in Pybytes will be connected to this app. |
| 42 | + |
| 43 | +**Devices** All devices that will be created in Pybytes. |
| 44 | + |
| 45 | + |
| 46 | +## Gateway |
| 47 | + |
| 48 | +The user should set up their own Gateway in order to communicate with ChirpStack. |
| 49 | + |
| 50 | +### How to set up a gateway: |
| 51 | + |
| 52 | +1 - Login in ChirpStack (https://loraserver.pycom.io/) |
| 53 | + |
| 54 | +2 - Click on **Gateway** on the main sidebar |
| 55 | + |
| 56 | +3 - Click on **Create** button |
| 57 | + |
| 58 | +4 - Fill the form with the information below |
| 59 | + |
| 60 | +**Gateway name** |
| 61 | + |
| 62 | +The name may only contain words, numbers, and dashes. |
| 63 | + |
| 64 | +**Gateway description** |
| 65 | + |
| 66 | +The description of the gateway. |
| 67 | + |
| 68 | +**Gateway ID** |
| 69 | + |
| 70 | +The gateway ID. |
| 71 | + |
| 72 | +**Network-server** |
| 73 | + |
| 74 | +Select the network-server to which the gateway will connect. When no network-servers are available in the dropdown, make sure a service-profile exists for this organization. |
| 75 | + |
| 76 | +**Gateway-profile** |
| 77 | + |
| 78 | +An optional gateway-profile which can be assigned to a gateway. This configuration can be used to automatically re-configure the gateway when LoRa Gateway Bridge is configured so that it manages the packet-forwarder configuration. |
| 79 | + |
| 80 | +**Gateway discovery enabled** |
| 81 | + |
| 82 | +When enabled (and LoRa Server is configured with the gateway discover feature enabled), the gateway will send out periodical pings to test its coverage by other gateways in the same network. |
| 83 | + |
| 84 | +**Gateway altitude** (meters) |
| 85 | + |
| 86 | +When the gateway has an on-board GPS, this value will be set automatically when the network has received statistics from the gateway. |
| 87 | + |
| 88 | +**Gateway location** (set to current location) |
| 89 | + |
| 90 | +For more information check out [ChirpStack official guide](https://www.chirpstack.io/guides/first-gateway-device/#add-a-lora-sup-reg-sup-gateway). |
0 commit comments