Skip to main content

Installation

This section covers bootstrap and configuration of the Linux system and the full LoRaWAN + monitoring software stack — one shared procedure for both FIBER hardware variants:

  • FIBER — the industrial version, based on Compute Module 4.
  • FIBER Lite — a Raspberry Pi 5 based bench-test appliance.

The two variants only diverge at the hardware level (flashing, RTC, the LoRaWAN concentrator's USB vs. SPI connection) — the page itself has tabs at those few points. Everything else, including InfluxDB, Grafana, and the branded Dashboard, is identical and installed on both.

Which device is this for?

A FIBER you received is already set up — there is nothing on these pages for you to run. It ships as a finished appliance: the operating system, ChirpStack, the concentrator and the rest of the stack are all part of its image, and it updates as a whole rather than package by package. Go straight to Register a Gateway and a Device, and to FIBER Hardware Guides for the display and 1-Wire sensors.

These pages are the build procedure — how that image is put together, and how to bring up a FIBER Lite unit from a blank microSD card. Follow them for FIBER Lite, or when building a FIBER image from scratch.

info

See FIBER Lite in the sidebar for FIBER Lite's hardware differences (no display, no 1-Wire sensors), and FIBER Hardware Guides for what to do with the display/1-Wire hardware that only FIBER has.

In this guide, we use two terms:

  • HOST: The computer from which you will perform the setup.
  • TARGET: The actual FIBER device you are setting up.

Follow the pages below in order:

  1. Flash Raspberry Pi OS
  2. Update System
  3. Configure Hardware - I2C bus + RTC
  4. Install ChirpStack
  5. Install ChirpStack Concentratord
  6. Install ChirpStack MQTT Forwarder
  7. Register a Gateway and a Device
  8. Install Node-RED
  9. Install InfluxDB
  10. Install Grafana
  11. Dashboard
  12. Firewall
  13. Ports & Default Credentials

Data Flow

ChirpStack, Node-RED, InfluxDB, and Grafana all run on the device itself — no separate servers or cloud services required:

A landing page on port 80 links to every service and shows live system stats, so the device is usable without memorizing ports or IP-to-service mappings.