Device Configuration
Configuration Overview
The miro Edge gateway configuration is done through a web interface. After successful login, the main configuration page of the gateway will be shown.
The LoRaWAN® and mioty settings are in the LPWAN menu.
To change LoRaWAN® specific settings and configuration navigate to the LoRaWAN section.
LoRaWAN® Settings
Register the gateway on your LoRa Network Server (LNS) first, and follow the documentation of the LNS for the detailed on-boarding procedure. Then enter the server address and the credentials provided by the LNS on the gateway.
Navigate to LPWAN->LoRaWAN. The region is given by the LoRaWAN card and shown on the page.
Select the packet forwarder in forwarder type and configure it as described below:
| Forwarder type | Connection to the network server | Recommendation |
|---|---|---|
| LoRa Basics™ Station | WebSocket over TLS; token or client certificate | Recommended |
| ChirpStack MQTT Forwarder | MQTT over TLS; user name and password or client certificate | Recommended for ChirpStack |
| Semtech UDP packet forwarder | UDP, no authentication or encryption | Only where the network server requires it |
The LoRaWAN settings for SubG and 2.4 GHz are slightly different
miro Edge for SubG LoRaWAN®
The SubG (868 MHz or 915 MHz) LoRaWAN® configuration page allows to change all LoRaWAN® specific settings
| Option | Description |
|---|---|
| Antenna used | Select either external (if connected) or internal LoRaWAN antenna. |
| Forwarder type | Select either optimized LORIOT packet forwarder or legacy Semtech packet forwarder of other LNS |
| Semtech packet forwarder server address | Set server address for legacy packet forwarder (e.g. router.eu.thethings.network for TTN EU) |
| Semtech packet forwarder port | Set server port for legacy packet forwarder |
| Loriot packet forwarder server address | Set server address for Loriot packet forwarder (e.g. eu1.loriot.io for EU instance) |
miro Edge for 2.4 GHz LoRaWAN®
The 2.4 GHz LoRaWAN configuration page allows changing all LoRaWAN® specific settings.
NOTE: Up to date, the global LoRaWAN region 2.4 GHz is not yet standardized. Please confirm your LNS is supporting LoRaWAN 2.4 GHz. Example LNS providing stable support are Loriot, TTN, or TTI.
| Option | Description |
|---|---|
| Semtech packet forwarder server address | Set server address for legacy packet forwarder (e.g. router.eu.thethings.network for TTN EU) |
| Semtech packet forwarder port | Set server port for legacy packet forwarder |
LoRa Basics™ Station
Select LoRa Basics(TM) Station as forwarder type, then configure the connection under LPWAN->LoRaWAN Basicstation: the LNS server URI, the authentication mode, the server's CA certificate and, depending on the mode, the station certificate and key or a token. CUPS is optional.
Private keys and tokens are not shown after saving; leave the field empty to keep the current one.
Status->Basicstion Log shows the log of LoRa Basics™ Station.
ChirpStack MQTT Forwarder
| Option | Description |
|---|---|
| Gateway EUI | EUI of the gateway as registered in ChirpStack |
| MQTT server | Address of the MQTT broker of ChirpStack |
| Topic prefix | MQTT topic prefix of the ChirpStack region (e.g. eu868) |
| JSON payloads | Use JSON instead of Protobuf payloads |
| Username / Password | Credentials for the MQTT broker, if required |
| MQTT connection | Status of the connection to the broker |
For a connection with client certificate, upload the CA certificate, the client certificate and the key on the same page.
Semtech UDP packet forwarder
| Option | Description |
|---|---|
| Semtech packet forwarder: Server address | Server address of the network server (e.g. eu1.cloud.thethings.network) |
| Semtech packet forwarder: Port | Server port (usually 1700) |
Warning
The Semtech UDP packet forwarder does not protect the connection to the network server. LoRaWAN payloads stay encrypted end to end, but use it only in a network that is separated from untrusted networks (e.g. a VPN or a private APN). Prefer LoRa Basics™ Station or the ChirpStack MQTT Forwarder.
mioty® Settings
On gateways with a mioty card, navigate to LPWAN->mioty. The settings are stored on the mioty card.
| Option | Description |
|---|---|
| Base Station ID | EUI of the base station; the button next to it derives it from the MAC address |
| BSSC address | Address of the mioty service center (e.g. eu3.loriot.io) |
| BSSC port | Port of the mioty service center |
| TLS CA certificate | CA certificate of the service center |
| TLS certificate | Certificate of the base station |
| TLS key | Private key of the base station; not shown after saving |
A factory reset also resets the configuration of the mioty card.
Interfaces
In the "interfaces" menu, you can change your configuration for the local network as well as for the mobile network.
The gateway has up to three preconfigured interfaces:
- ETHFIX: static, non-changable link local IPv4 address (169.254.100.100). Do not delete or modify!
- LAN: User configurable IPv4 address
- UMTS0: 3G/LTE network (might only be present in LTE gateways)
Firmware 2.7
Ethernet (LAN) and LTE (UMTS0) are both connections of the gateway to the internet. Firmware 2.7 does not route traffic between them: devices on the LAN cannot use the LTE connection of the gateway.
Ethernet interface
To change the IP address of the ethernet network, settings of LAN network have to be changed. Do not change the configuration of ETHFIX.
You can change your configuration for the local network: automatic (DHCP) or manual (static IP) by clicking on Edit button for LAN network configuration.
DHCP
You can configure your gateway as a DHCP client to automatically obtain IP configuration from a DHCP server.
- Set Protocol to "DHCP client"
- Click "Switch protocol"
- Click "Save" button to save your configuration.
- Back on the "Interfaces" page, click "Save & Apply" to finalize interface configuration
Static IP
You can configure your gateway with a static IP address.
- Set Protocol to "static address"
- Do not change "Device". This needs to be set to "br-lan"
- Set IPv4 address (e.g. 192.168.20.101)
- Set IPv4 netmask according to your local network setup (e.g. 255.255.255.0)
- Set IPv4 gateway address according to your local network setup. This is the address of the device used to connect the miro Edge gateway to the internet
- Set IPv4 broadcast, according to your local network setup (e.g., blank if not needed)
In a static IP setup you also have to set DNS configuration, which is available in the "Advanced Settings" page.
- Make sure "Use default gateway" is checked
- Add your DNS to "Use custom DNS server". This depends entirely on your network configuration. Recommendation is to set your default gateway and goolge DNS server. This assumes DNS support by your default gateway.
- Click "Save" button to save your configuration.
- Back on the "Interfaces" page, click "Save & Apply" to finalize interface configuration
Mobile Network Configuration
For mobile internet connectivity, you might have to set your APN configuration. Clicking on Edit button for UMTS0 network configuration.
- Set APN according to your mobile network operator (e.g. shared.m2m.ch)
- Set other configuration options (e.g. PIN) if needed.
- Click "Save" button to save your configuration.
- Back on the "Interfaces" page, click "Save & Apply" to finalize interface configuration
Testing network configuration and Diagnostics
In Network select Diagnostics to access "Network Utilities". Use those tools to check and validate your network configuration.
Important
Diagnostics tools might not work while your gateway is directly connected to your PC using link local (169.254.100.100) address.