ChirpStack Gateway Bridge

ChirpStack Gateway Bridge is a service that converts LoRaWAN Packet Forwarder messages into ChirpStack's common data format.

  • Home Automation
  • Other
  • Tools & Utilities
ChirpStack Gateway Bridge is a service that converts LoRaWAN Packet Forwarder messages into ChirpStack's common data format. It sits between LoRaWAN gateways and the ChirpStack server and requires ChirpStack plus an MQTT broker such as Mosquitto to run.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

12/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 2 of 4 factors.

Availability: platform listings confirmed today, links checked 53 days ago

No GitHub repository data collected yet.

Checked 45 days ago - source: GitHub (sponsors/chirpstack)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set your LoRa region before starting Before starting, set your LoRaWAN region (the radio band, like EU868 or US915) in the gateway-bridge docker-compose settings, including the MQTT topic templates that tell the server where to listen. If the region or topic names don't match your gateway's region, the gateway and server can't talk, so your LoRa devices won't show data. source
  • Start the services, then open the UI From the folder with docker-compose.yml, run docker compose up to start all services, then open http://localhost:8080. If you don't start the services, the web UI and gateway bridge aren't running, so you can't log in or connect a gateway. source
  • Import device profiles for hardware If you're adding LoRa hardware and have make (a command-line helper) installed, run make import-device-profiles after the stack is up to load ready-made device profiles/templates. Without it, you may not find a template for your device and may have to configure it manually. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why might a LoRa gateway not send data to ChirpStack in a Docker setup?

The LoRaWAN region in the gateway-bridge docker-compose settings must match the gateway's region. The MQTT topic templates must also match, otherwise the gateway and server cannot talk and LoRa devices will not show data.

Where does chirpstack-gateway-bridge look for its configuration when no config flag is set?

It uses a default search order. One of the paths it checks is chirpstack-gateway-bridge.toml in the current working directory.

How do I start the ChirpStack services with Docker Compose and open the UI?

Run docker compose up from the folder containing docker-compose.yml. Then open the local web UI on port 8080.

How can I load ready-made device profiles after starting the ChirpStack Docker stack?

If make is installed, run make import-device-profiles after the stack is up. Without it, you may not find a template for your device and may need to configure it manually.

Answers sourced from context7.com, github.com, www.chirpstack.io

Community

Collected 53 days ago - public community threads