ChirpStack Application Server to send data to an Azure Service Bus Queue config

Hello,

I have followed the Quickstart Azure integration. In the chirpstack-network-server.toml configuration example, it suggests the following settings:

  [network_server.gateway.backend]
  type="azure_iot_hub"

         [network_server.gateway.backend.azure_iot_hub]
         events_connection_string="[Gateway Events Connection String]"
         commands_connection_string="[Gateway Commands Connection String]"

However when I look at my unedited chirpstack-network-server.toml the same setting is currently set as follows:

  [network_server.gateway.backend]
  # Backend
  type="mqtt"

  
    # MQTT gateway backend settings.
    #
    # This is the backend communicating with the LoRa gateways over a MQTT broker.
    [network_server.gateway.backend.mqtt]
    # MQTT topic templates for the different MQTT topics.
    #
    # The meaning of these topics are documented at:
    # https://www.chirpstack.io/gateway-bridge/
    #
    # The default values match the default expected configuration of the
    # ChirpStack Gateway Bridge MQTT backend. Therefore only change these values when
    # absolutely needed.

Now this may be a silly ask but I am confused here, do I actually replace type="mqtt" with type="azure_iot_hub" or must the Azure related settings be additional to the pre-existing settings? I am quite new to this and currently trying to deploy this as a PoC.

Thank you.

Please see: https://www.chirpstack.io/network-server/install/config/

  # Backend defines the gateway backend settings.
  #
  # The gateway backend handles the communication with the gateway(s) part of
  # the LoRaWAN network.
  [network_server.gateway.backend]
    # Backend
    #
    # This defines the backend to use for the communication with the gateways.
    # Use the section name of one of the following gateway backends.
    # Valid options are:
    #  * mqtt
    #  * amqp
    #  * gcp_pub_sub
    #  * azure_iot_hub
    type="mqtt"

...
1 Like