Description:
I have configured a ChirpStack LoRaWAN setup using a Raspberry Pi and a Seeed WM1302 gateway module. Initially, the LoRaWAN packets were successfully received and verified in the ChirpStack Web UI.
To integrate with a Local PC running a Mosquitto MQTT broker, I modified the server address in the ChirpStack configuration files as follows:
Configuration Changes:
ChirpStack MQTT Integration Configuration:
$ sudo nano /etc/chirpstack/chirpstack
[integration.mqtt]
server = “tcp://192.168.0.101:1883”
marshaler = “json”
$ sudo systemctl restart chirpstack
ChirpStack Gateway Bridge Configuration:
$ sudo nano /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
[integration.mqtt]
[integration.mqtt.auth.generic]
server = “tcp://192.168.0.101:1883”
marshaler = “json”
$ sudo systemctl restart chirpstack-gateway-bridge
Issue:
After modifying the MQTT integration to use the Local PC’s Mosquitto broker, I can successfully receive LoRaWAN packets and verify them using Wireshark. However, in the ChirpStack Web UI, the gateway status appears as offline.
Query:
Does modifying the MQTT integration to connect to a Local PC cause the Web UI to show the gateway as offline?
Are any additional steps required to ensure that the gateway status remains online in the Web UI while using an external MQTT broker?
Any guidance or recommendations would be greatly appreciated.
Best regards,
Sandeep S