LoRaWAN Gateway Setup and Configuration

Gateway Setup Basics

Getting a LoRaWAN gateway online involves: physical installation, network server registration, frequency plan configuration, and coverage testing. Most problems come from wrong frequency settings or firewall blocking UDP packets.

Gateway Types

Indoor gateways: Kerlink Wirnet iStation, Multitech Conduit, SenseCAP M2 - suitable for building coverage or dense urban deployments. Typical range: 1-5km depending on obstructions.

Outdoor gateways: Kerlink Wirnet iFemtoCell-Evolution, Cisco IXM, SenseCAP M2 (outdoor variant) - weatherproof, higher-gain antennas. Range: 5-15km rural, 2-8km urban.

DIY gateways: Raspberry Pi + SX1301/SX1302 concentrator boards. Cheap for testing (70-120 EUR) but not production-grade reliability.

Network Server Options

ChirpStack (open source): Self-hosted on Linux/Docker. Full control, no per-device fees. Requires sysadmin skills for setup and maintenance. Integrates with InfluxDB/Grafana easily.

The Things Network (TTN): Free community network, good for prototyping. Fair Use Policy limits: 30 seconds airtime per device per day. Not for production deployments with high message frequency.

AWS IoT Core for LoRaWAN: Managed service, pay per message. Good if you're already in AWS ecosystem. More expensive than self-hosting for large deployments.

Commercial options: Actility, Everynet, Senet - managed networks with SLAs. Typical pricing: 1-5 EUR per device per year plus setup fees.

Configuration Steps

1. Physical installation: Mount gateway with antenna vertical (omnidirectional) or pointed at coverage area (directional). Height matters - every meter helps. Roof mounting beats window mounting every time.

2. Network connectivity: Ethernet preferred. LTE backup for remote sites. Gateway needs UDP port 1700 outbound (for Semtech packet forwarder) or MQTT ports (for BasicStation protocol).

3. Frequency plan: Must match your region - EU868, US915, AS923, etc. Wrong frequency plan means devices can't connect. Gateway can't receive what it's not listening for.

4. Network server registration: Generate Gateway EUI (usually derived from MAC address). Register in network server. Configure gateway to point to network server address.

5. Test with known device: Deploy test device transmitting every 30 seconds. Check network server shows uplinks. Verify RSSI and SNR values are reasonable (RSSI > -120 dBm, SNR > -10 dB for reliable communication).

Coverage Testing

Walk/drive test with handheld device showing packet reception. Mark boundaries where SF7 (shortest range, fastest data rate) stops working. That's your practical coverage area.

Multiple gateways see same packets - this is good (redundancy). Network server deduplicates. For critical deployments, plan 20-30% gateway overlap.

Common Problems

Gateway online but no uplinks:

• Wrong frequency plan (check EU868 vs US915)
• Firewall blocking UDP 1700 or MQTT ports
• Device and gateway on different network servers
• Gateway clock drift (needs NTP for Class B/C)

Weak signal (RSSI < -120 dBm):

• Antenna not properly connected (check N-type or SMA connector)
• Indoor gateway trying to cover outdoor area
• Gateway placed in basement or surrounded by metal
• Solution: Move gateway higher or add outdoor gateway

High packet loss:

• Interference from other networks (check with spectrum analyzer)
• Gateway CPU overloaded (check processor usage)
• Network server behind on processing (check queue depth)
• LoRaWAN channel congestion (too many devices on SF12)

What I Help With

Services:

• Gateway hardware selection for your coverage requirements
• Network server selection (self-hosted vs managed)
• Installation planning (antenna placement, mounting)
• Configuration and troubleshooting
• Coverage modeling and optimization

You own everything:

• Self-hosted network server setup (if you choose ChirpStack)
• Complete configuration documentation
• Coverage test results and maps
• No monthly fees for self-hosted deployments