[release] ChirpStack Gateway OS v4.0


Main changes

ChirpStack v4

This release replaces ChirpStack Network Server (v3) and ChirpStack Application Server (v3) with ChirpStack v4.0.0.

MQTT certificates

If using the full image, MQTT TLS certificates will be automatically generated on first boot and configured in ChirpStack. For consuming device events throug the MQTT integration, you can generate certificates in the web-interface under the application integrations.

Note: localhost connections (e.g. if using Node-RED) to the MQTT do not need TLS certificates for authentication and authorization.

gateway-config improvements

If using the full ChirpStack Gateway OS image, which includes the ChirpStack Network Server, the gateway-config script will automatically create the gateway in the ChirpStack database for you.

Region configuration

The full image contains update region configuration for the common regions. The desired region can be selected using the gateway-config configuration script.

New shields

Support for the following shields has been added:

  • RAK2247
  • RAK5147
  • Seeed WM1302

Yocto Kirkstone

ChirpStack Gateway OS has been updated to Yocto Kirkstone. This should fix boot problems on some Pi 4 revisions, as this release contains an updated bootloader.

Other updates

  • ChirpStack Concentratord to v4.0.0
  • ChirpStack Gateway Bridge to v4.0.0
  • Node-RED to v2.1.6
1 Like



  • ChirpStack to v4.0.3.
  • ChirpStack Concentratord to v4.0.1.
  • The Things Network lorawan-devices to latest version.

New shields

  • Waveshare SX1302 LoRaWAN Gateway HAT


  • Add missing /etc/fw_env.config file (see upgrade note below).
  • Fix missing Wiregard binaries. (#93)

Update note

If upgrading from v4.0.0 using the software-update utility, you must run the
following command first because of the missing /etc/fw_env.config file:

sudo echo "/boot/uboot.env 0x0000    0x4000" > /etc/fw_env.config



  • ChirpStack to v4.1.1.
  • ChirpStack Gateway Bridge to v4.0.3.
  • Node-RED to v3.0.2.


  • Fix NodeJS / Node-RED crashing with “Bus error” error message. (#95)