How can I use the gateway's Web UI to manage the lorawan node and upload data to a remote mqtt broker at the same time?

Wei-Li_Wang · June 26, 2025, 8:58am

Hi every one.
I use raspberry pi and downloaded chirpstack gateway full image os.
I have a question. I want to keep the original management function on chirpstack web ui:url:8088, but I also want to forward the data to a remote server. Is it possible?

I tried to set ChirpStack MQTT Forwarder to the remote IP in the Web UI.
At this time, I can no longer receive any data from the gateway on the :8088 page.
I tried to use UCI command to add a mqtt forwarder so that chirpstack has two sets of mqtt forwarders,

uci add chirpstack-mqtt-forwarder mqtt
uci set chirpstack-mqtt-forwarder.@mqtt[1]=mqtt
...
...
...

but when I set it up like this, the mqtt forwarder will not run.

Can experts give me some advice?

Liam_Philipp · June 30, 2025, 3:43pm

The MQTT forwarder is Chirpstack’s backhaul, so where it gets it’s data from not where it forwards data out. Pointing that at an external server just means Chirpstack gets no data and your external broker receives encrypted data which it has no means of decrypting.

What you would want is to use the mqtt integration, but unfortunately this is not fully supported in the Gateway OS configuration. I have a pull request submitted to add this to the configuration but it hasn’t been accepted.

So as for now there is no real way to pull data out of your Chirstack gateway os full image.

github.com/chirpstack/chirpstack-openwrt-feed

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

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.

eerke2021 · July 1, 2025, 10:30pm

Could you not just use a local MQTT broker as usual on the Raspberry Pi, a remote MQTT broker elsewhere and then just connect the two MQTT brokers with a WireGuard/openCPN tunnel or something. I haven’t connected two brokers but considered it at one point and looked into it. It didn’t look hard. Got to be easier than adjusting Chirpstack to use a remote broker.