There have been a lot of questions related to the Gateway Profiles. Although I tried my best to document it, this feature does not seem to be well communicated and therefore understood. Many questions are related to people not actually using the Gateway Profiles, but pointing to it when things do not work as expected.
To summarize: The purpose is to re-configure gateways (e.g. update the Packet Forwarder configuration and restart it in case of change). It does not affect the LoRa Server behavior / device configuration at all. The only things it does is send configuration messages to the LoRa Gateway Bridge. When the LoRa Gateway Bridge is not configured to handle these configuration messages, the Gateway Profile does not add any value.
My question is: Are there any users that use the Gateway Profiles to re-configure their Packet Forwarder configuration? If this is not the case, then I propose we remove the Gateway Profile as this removes some unneeded complexity from the LoRa Gateway Bridge, LoRa Server and LoRa App Server.
Personally I would favor this, as maybe the management of LoRa gateways should not be the task of the LoRa Gateway Bridge. Its primary task is to work with different backends (e.g. Semtech UDP packet-forwarder and the Basic Station) and “bridge” this to LoRa Server message sent over (currently) MQTT.
It also simplifies the Basic Station configuration as the channel-plan configuration would move to the LoRa Gateway Bridge
lora-gateway-bridge.toml file. This would make it possible to use the Basic Station without LoRa Server (and a Gateway Profile) as dependency.
Please share your feedback!