MQTT integration with application server

Liam_Philipp · February 20, 2025, 6:19pm

The “Full” Chirpstack Gateway OS is really meant to just be for basic testing or development purposes. The gateway OS really should just be for your gateway, and Chirpstack itself should be set up on a dedicated server, with this setup the Helium integration would work.

That being said the gateway OS is only a few lines of code away from being compatible, submitting a pull request to add the integration section to the UCI commands would be relatively easy.

Liam_Philipp · February 20, 2025, 7:49pm

I was curious what this would actually take, so I just went and did it myself. Here’s the pull request.

github.com/chirpstack/chirpstack-openwrt-feed

Chirpstack Gateway OS 'Full' - Adding UCI commands for configuring the MQTT integration

chirpstack:master ← LiamPhil:master

opened 11:42PM - 20 Feb 25 UTC

LiamPhil

+45 -5

Updates the chirpstack.config file to include UCI commands for the [integration.…mqtt] section of the chirpstack.toml, then update the chirpstack.init to use these UCI commands when generating the runtime chirpstack.toml. I left the tls_certificate options out as there is no easy way to upload them. The updates leave MQTT as the only enabled integration.

If the changes are implemented, you would only need to run the commands:

uci set chirpstack.integration_mqtt.server='tcp://external-broker.example.com:1883/'
uci commit chirpstack

Then your events will get forwarded to your remote broker.