[release] ChirpStack v4.4 test releases



Relay support (TS011)

This adds support for the Relay specification (TS011). In the Device Profile it is possible to configure the Relay and Relay capable end-device parameters. Under the Application view it is possible to assign devices to a Relay (required for filtering and exchanging the device list with the Relay).

Note: Please note that this requires a Relay and Relay capable end-device.


Build changes

The build configuration has been updated to generate fully static binaries based on musl libc. This solves the issue where in some cases ChirpStack would not connect over TLS to a PostgreSQL database. (#156).

This also changes the Docker base image to alpine, reducing the Docker image size by ~ 50% compared to debian:buster-slim. Within the Dockerfile we now COPY the already compiled binaries, which also reduces the build time on release.

If you are compiling ChirpStack from source, please refer to the README.md in the source repository as some commands have changed.

IFTTT integration

Configuration has been added to configure the prefix of the event name and to send arbitrary JSON payloads instead of the 3 value payload.

Other improvements

  • Add lrwn_filters crate for filtering LoRaWAN PHYPayloads.
  • Dependencies have been updated.


  • Fix netid_type method panic in case of invalid DevAddr prefix type.
  • Fix missing device search filter (API).



Use the testing channel instead of stable:

sudo echo "deb https://artifacts.chirpstack.io/packages/4.x/deb testing main" | sudo tee /etc/apt/sources.list.d/chirpstack.list


Use the chirpstack/chirpstack:4.4.0-test.1 image and tag.


Do you have any advice for a TS011 device?
I may love to have the device to test the relay feature.

Thanks a lot.

Unfortunately, nothing public yet… But I think this will be a matter of time :slight_smile:

1 Like

Hello! Can application servers add nodes in batches?

Not in the interface. But you can easily do it with the API.