Help testing ChirpStack v4 (test releases)!

After months of working on this, I’m excited to share with you the first test-releases of ChirpStack v4. The biggest feature is the merge of ChirpStack Application Server and ChirpStack Network Server component into a single component and support for multi-region without the need to setup a new instance for each region. This makes it a lot easier to setup ChirpStack. More background information can be found here: Changes coming to ChirpStack.

For people who want to help with testing, I’ve prepared various test-releases :slight_smile:


This is the easiest way to test ChirpStack v4 :slight_smile:

Please see the v4 branch of the ChirpStack Docker repository:

A docker-compose up should bring everything up, after which you can open the web-interface on port 8080 (e.g. http://localhost:8080) and login with the username / password: admin / admin.

Raspberry Pi / ChirpStack Gateway OS

Please use the 4.0.0-test.X Raspberry Pi images from Index of /downloads/chirpstack-gateway-os/raspberrypi/.

At this moment these are:

Debian / Ubuntu

You can use the following Debian repository:

sudo apt-key adv --keyserver --recv-keys 1CE2AFD36DBCCA00

sudo echo "deb testing main" | sudo tee /etc/apt/sources.list.d/chirpstack_4.list
sudo apt update

After installation, please see the configuration file in /etc/chirpstack/chirpstack.toml. You must create a new PostgreSQL database and install the pg_trgm extension. To start / stop / restart ChirpStack, use:

systemctl start chirpstack
systemctl stop chirpstack
systemctl restart chirpstack

Please note that you can use ChirpStack v4 in combination with the ChirpStack Gateway Bridge v3. However, you must enable the protobuf marshaler in the chirpstack-gateway-bridge.toml configuration. As well, you must configure the topic prefix with the region of your gateway. For example:


  # MQTT integration configuration.
  # Event topic template.
  event_topic_template="eu868/gateway/{{ .GatewayID }}/event/{{ .EventType }}"

  # State topic template.
  # States are sent by the gateway as retained MQTT messages (by default)
  # so that the last message will be stored by the MQTT broker. When set to
  # a blank string, this feature will be disabled. This feature is only
  # supported when using the generic authentication type.
  state_topic_template="eu868/gateway/{{ .GatewayID }}/state/{{ .StateType }}"

  # Command topic template.
  command_topic_template="eu868/gateway/{{ .GatewayID }}/command/#"


(Configuration - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server).

Please see chirpstack/chirpstack/configuration at master · chirpstack/chirpstack · GitHub for all the included regions. Also make sure that the region that you are planning to use is enabled here: chirpstack/chirpstack.toml at master · chirpstack/chirpstack · GitHub.

I will follow up with a documentation link + draft changelog soon.


Setting up an separate Debian VPS now for testing V4 :muscle:

1 Like

This is great news. Gonna test it out soonest

I would to test out V4!

However, I do need slightly more detailed instructions. what do I do with this file? chirpstack-gateway-os-full-raspberrypi3-20220425082218.rootfs.wic.gzI tried using Balena Etcher to burn it to an SD card, but that’s not working.

Please help. Step by step instructions would be best, but an outline of major steps would also be helpful.



In general, you can follow these instructions: Introduction - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server.