Hi:
If you want the payload be JSON, you should select “loraserver 2.x” in LoRa Network server field. Json-v2 is just a code we use internally, in fact it is the standard JSON proto.
Hi. Please describe what you want to achieve. The Gateway bridge of loraserver.io is used to catch the Semtech UDP protocol and translate it to MQTT(in general). If you want to use the Gateway Bridge in RAK Gateway you do not need loraserver.io gateway bridge. The main difference in LoRaServer is migration to Go lang and using the Google Protobuf, this also changes the topic templates.
The company I work for operates customized proprietary LoRa applications, not the standard TTN LoRaWAN application. So, I need to customize components like LoRa Gateway Bridge to integrate RAK gateway to the existing backend system.
My existing backend system operates on Brocaar LoRa Gateway Bridge 2.7.1, uses V2_JSON and old MQTT Topic templates. LoRa Gateway Bridge 3.x brings some new features I would love to use, for example, customized meta-data, fake RX time.
In my situation, I would like to see the RAK gateway could:
run Brocaar LoRa Gateway Bridge 3.x, which you already have
allow me to use the JSON payload type (V2_JSON no longer supported in 3.x, Protobuf is not debugging friendly)
allows me to edit LoRa Gateway Bridge config file to add customized metadata
new MQTT topic templates, which you already supported