Basic station issue

Hi Guys,

I am configuring my gateway as a Basic station using US915 and I am getting this:

2021-01-25 18:37:56.634 [AIO:XDEB] [3|WS] < {“msgtype”:“router_config”,“NetID”:null,“JoinEui”:null,“region”:“EU863”,“hwspec”:“sx1301/0”,“freq_range”:[863000000,870000000],“DRs”:[[12,125,0],[11,125,0],[10,125,0],[9,125,0],[8,125,0],[7,125,0],[7,250,0],[0,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0]],“sx1301_conf”:[]}
2021-01-25 18:37:56.635 [RAL:ERRO] Unsupported hwspec=sx1301/0
2021-01-25 18:37:56.635 [any:ERRO] Closing connection to muxs - error in s2e_onMsg
2021-01-25 18:37:56.639 [AIO:DEBU] [3] ws_close reason=1000
2021-01-25 18:37:56.639 [AIO:XDEB] [3] ws_closing_w state=5
2021-01-25 18:37:56.639 [AIO:DEBU] Echoing close - reason=1000
2021-01-25 18:37:56.659 [AIO:DEBU] [3|WS] Server sent close: reason=1000
2021-01-25 18:37:56.659 [AIO:DEBU] [3] WS connection shutdown…
2021-01-25 18:37:56.660 [TCE:VERB] Connection to MUXS closed in state -1
2021-01-25 18:37:56.660 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)
2021-01-25 18:38:06.664 [AIO:XDEB] [3] ws_connecting state=1
2021-01-25 18:38:06.664 [AIO:XDEB] [3] ws_connecting state=2
2021-01-25 18:38:06.665 [TCE:INFO] Connecting to INFOS: ws://127.0.0.1:3001
2021-01-25 18:38:06.684 [AIO:XDEB] [3] ws_connecting state=3
2021-01-25 18:38:06.684 [AIO:XDEB] [3|WS] > {“router”:“80:0:a000:946”}
2021-01-25 18:38:06.686 [AIO:XDEB] [3|WS] < {“router”:“0080:0000:a000:0946”,“muxs”:“0080:0000:a000:0946”,“uri”:“ws://127.0.0.1:3001/gateway/00800000a0000946”}
2021-01-25 18:38:06.687 [TCE:INFO] Infos: 0080:0000:a000:0946 0080:0000:a000:0946 ws://127.0.0.1:3001/gateway/00800000a0000946
2021-01-25 18:38:06.687 [AIO:DEBU] [3] ws_close reason=1000
2021-01-25 18:38:06.687 [AIO:XDEB] [3] ws_closing_w state=5
2021-01-25 18:38:06.687 [AIO:DEBU] Echoing close - reason=1000
2021-01-25 18:38:06.691 [AIO:ERRO] Recv failed: NET - Connection was reset by peer
2021-01-25 18:38:06.691 [AIO:DEBU] [3] WS connection shutdown…
2021-01-25 18:38:06.693 [AIO:XDEB] [3] ws_connecting state=1
2021-01-25 18:38:06.693 [AIO:XDEB] [3] ws_connecting state=2
2021-01-25 18:38:06.694 [TCE:VERB] Connecting to MUXS…
2021-01-25 18:38:06.702 [AIO:XDEB] [3] ws_connecting state=3
2021-01-25 18:38:06.702 [TCE:VERB] Connected to MUXS.
2021-01-25 18:38:06.702 [AIO:XDEB] [3|WS] > {“msgtype”:“version”,“station”:“2.0.5(mlinux/std)”,“firmware”:null,“package”:null,“model”:“mlinux”,“protocol”:2,“features”:“rmtsh prod”}
2021-01-25 18:38:06.723 [AIO:XDEB] [3|WS] < {“msgtype”:“router_config”,“NetID”:null,“JoinEui”:null,“region”:“EU863”,“hwspec”:“sx1301/0”,“freq_range”:[863000000,870000000],“DRs”:[[12,125,0],[11,125,0],[10,125,0],[9,125,0],[8,125,0],[7,125,0],[7,250,0],[0,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0],[-1,0,0]],“sx1301_conf”:[]}
2021-01-25 18:38:06.723 [RAL:ERRO] Unsupported hwspec=sx1301/0
2021-01-25 18:38:06.723 [any:ERRO] Closing connection to muxs - error in s2e_onMsg
2021-01-25 18:38:06.723 [AIO:DEBU] [3] ws_close reason=1000
2021-01-25 18:38:06.723 [AIO:XDEB] [3] ws_closing_w state=5
2021-01-25 18:38:06.723 [AIO:DEBU] Echoing close - reason=1000
2021-01-25 18:38:06.738 [AIO:DEBU] [3|WS] Server sent close: reason=1000
2021-01-25 18:38:06.738 [AIO:DEBU] [3] WS connection shutdown…
2021-01-25 18:38:06.739 [TCE:VERB] Connection to MUXS closed in state -1
2021-01-25 18:38:06.739 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)

  • URI: ws://127.0.0.1:3001

  • chirpstack-gateway-bridge:

# This configuration provides a Semtech UDP packet-forwarder backend and
# integrates with a MQTT broker. Many options and defaults have been omitted
# for simplicity.
#
# See https://www.chirpstack.io/gateway-bridge/install/config/ for a full
# configuration example and documentation.

[general]
# debug=5, info=4, warning=3, error=2, fatal=1, panic=0
log_level=5

# Log to syslog.
#
# When set to true, log messages are being written to syslog.
log_to_syslog=true

# Gateway backend configuration.
[backend]
# Backend type.
type=“basic_station”

# Semtech UDP packet-forwarder backend.
[backend.semtech_udp]

# ip:port to bind the UDP listener to
#
# Example: 0.0.0.0:1700 to listen on port 1700 for all network interfaces.
# This is the listener to which the packet-forwarder forwards its data
# so make sure the ‘serv_port_up’ and ‘serv_port_down’ from your
# packet-forwarder matches this port.
udp_bind = “0.0.0.0:1700”

# Basic Station backend.
[backend.basic_station]

# ip:port to bind the Websocket listener to.
bind=":3001"

# TLS certificate and key files.
#
# When set, the websocket listener will use TLS to secure the connections
# between the gateways and ChirpStack Gateway Bridge (optional).
#tls_cert="/var/config/chirpstack-gateway-bridge/server.crt"
#tls_key="/var/config/chirpstack-gateway-bridge/server.key"

# TLS CA certificate.
#
# When configured, ChirpStack Gateway Bridge will validate that the client
# certificate of the gateway has been signed by this CA certificate.
#ca_cert="/var/config/chirpstack-gateway-bridge/ca.crt"

# Integration configuration.
[integration]
# Payload marshaler.
#
# This defines how the MQTT payloads are encoded. Valid options are:
# protobuf: Protobuf encoding
# json: JSON encoding (easier for debugging, but less compact than ‘protobuf’)
marshaler=“json”

# MQTT integration configuration.
[integration.mqtt]
# Event topic template.
event_topic_template=“gateway/{{ .GatewayID }}/event/{{ .EventType }}”

# Command topic template.
command_topic_template=“gateway/{{ .GatewayID }}/command/#”

# MQTT authentication.
[integration.mqtt.auth]
# Type defines the MQTT authentication type to use.
#
# Set this to the name of one of the sections below.
type=“generic”

# Generic MQTT authentication.
[integration.mqtt.auth.generic]
# MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws)
server="tcp://192.168.2.12:1883"
#server="ws://127.0.0.1:1883"

# Connect with the given username (optional)
username=""

# Connect with the given password (optional)
password=""

# Region.
#
# Please refer to the LoRaWAN Regional Parameters specification
# for the complete list of common region names.
region=“US915”

# Minimal frequency (Hz).
frequency_min=902000000

# Maximum frequency (Hz).
frequency_max=928000000

  • Chirpstack-network-server

[network_server.band]
# LoRaWAN band to use.
#
# Valid values are:
# AS923
# AU915
# CN470
# CN779
# EU433
# EU868
# IN865
# KR920
# RU864
# US915
name=“US915”


# Max mac-command error count.
#
# When a mac-command is nACKed for more than the configured value, then the
# ChirpStack Network Server will stop sending this mac-command to the device.
# This setting prevents that the Network Server will keep sending mac-commands
# on every downlink in case of a malfunctioning device.
max_mac_command_error_count=3

# Enable only a given sub-set of channels
#
# Use this when ony a sub-set of the by default enabled channels are being
# used. For example when only using the first 8 channels of the US band.
# Note: when left blank, all channels will be enabled.
#
# For the US band, there are 64 125kHz channels (0-63) with 8 500kHz
# channels (65-71) with frequencies in the middle of each
# sub-band of 125kHz channels.
# Most US LoRa gateways recieve on only one sub-band which consists of
# 8 125kHz channels and 1 500 kHz channel
#
# Example: (sub-band 1)
enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7, 64]
# Exmaple: (sub-band 2)
#enabled_uplink_channels=[8, 9, 10, 11, 12, 13, 14, 15, 65]
#enabled_uplink_channels=[]

=======================

Not sure why I am getting: “region”:“EU863” from the chirpstack-gateway-bridge? or chirpstack-network-server instead of configured as: US915?

Thanks,

BT

is this running on a pi or something?

Hi ccall48,

No. It is not. It is running on Multitech Conduit. I shut down the Chirpstac Network Sever and I am still

getting this error. It seemed like it is coming from the ChirpStack-gateway-bridge.

Any ideas?

Thanks,

BT

Sorry don’t have any experience with multitech, however they seem very popular… a lot of people use them. So hopefully someone can chirp in an correct me if i’m wrong here…

I have my stuff running in cloud using docker… so it may not be relevant to your setup…

contents of my chirpstack-network-server.toml

[network_server.band]
name="AU915"

  [network_server.network_settings]
  enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]

Do you have this (but with US915) settings for your application server?

Yes. See section: * Chirpstack-network-server on my first post. Thanks.

BTW, Since you have your stuff up and running, could you show/guide how to create the server certificate and server key and CA cert for the ChirpStack-gateway-Bridge? Thanks.

Ok, it sounds like the channel plan settings needs to be configured in the mutlitech gw itself.

You will also most definitely need to restart the mutlitech after making changes if you are not already.

Do you have any links to multitech docs?

Hi Guys,

Updated log:

root@mtcdt:/var/run/lora/1# ./station
2021-01-26 02:56:25.731 [SYS:INFO] Logging : stderr (maxsize=100000, rotate=3)
2021-01-26 02:56:25.732 [SYS:INFO] Station Ver : 2.0.5(mlinux/std) 2020-10-19 19:44:13
2021-01-26 02:56:25.732 [SYS:INFO] Package Ver : (null)
2021-01-26 02:56:25.732 [SYS:INFO] proto EUI : 80:0:a000:946 (station.conf)
2021-01-26 02:56:25.733 [SYS:INFO] prefix EUI : ::0 (station.conf)
2021-01-26 02:56:25.733 [SYS:INFO] Station EUI : 80:0:a000:946
2021-01-26 02:56:25.733 [SYS:INFO] Station home: ./ (builtin)
2021-01-26 02:56:25.733 [SYS:INFO] Station temp: /var/tmp/ (builtin)
2021-01-26 02:56:25.733 [SYS:WARN] Station in NO-CUPS mode
2021-01-26 02:56:25.935 [TCE:INFO] Starting TC engine
2021-01-26 02:56:25.952 [any:INFO] ./tc.trust:
cert. version : 3
serial number : 71:8D:F4:FF:AD:E9:50:B3:F3:9D:34:6D:68:CB:E4:8B:F3:3E:4B:04
issuer name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
subject name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
issued on : 2021-01-26 01:06:22
expires on : 2021-02-25 01:06:22
signed using : ECDSA with SHA256
EC 2021-01-26 02:56:25.952 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
2021-01-26 02:56:25.992 [AIO:XDEB] [3] ws_connecting state=1
2021-01-26 02:56:26.003 [TCE:INFO] Connecting to INFOS: wss://localhost:3001
2021-01-26 02:56:30.233 [AIO:XDEB] [3] ws_connecting state=1
2021-01-26 02:56:35.116 [AIO:XDEB] [3] ws_connecting state=1
2021-01-26 02:56:35.119 [AIO:XDEB] [3] ws_connecting state=2
2021-01-26 02:56:35.125 [AIO:XDEB] [3] ws_connecting state=3
2021-01-26 02:56:35.126 [AIO:XDEB] [3|WS] > {“router”:“80:0:a000:946”}
2021-01-26 02:56:35.130 [AIO:XDEB] [3|WS] < {“router”:“0080:0000:a000:0946”,“muxs”:“0080:0000:a000:0946”,“uri”:“wss://localhost:3001/gateway/00800000a0000946”}
2021-01-26 02:56:35.131 [TCE:INFO] Infos: 0080:0000:a000:0946 0080:0000:a000:0946 wss://localhost:3001/gateway/00800000a0000946
2021-01-26 02:56:35.131 [AIO:DEBU] [3] ws_close reason=1000
2021-01-26 02:56:35.131 [AIO:XDEB] [3] ws_closing_w state=5
2021-01-26 02:56:35.131 [AIO:DEBU] Echoing close - reason=1000
2021-01-26 02:56:35.136 [AIO:ERRO] Recv failed: SSL - The peer notified us that the connection is going to be closed
2021-01-26 02:56:35.136 [AIO:DEBU] [3] WS connection shutdown…
2021-01-26 02:56:35.139 [any:INFO] ./tc.trust:
cert. version : 3
serial number : 71:8D:F4:FF:AD:E9:50:B3:F3:9D:34:6D:68:CB:E4:8B:F3:3E:4B:04
issuer name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
subject name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
issued on : 2021-01-26 01:06:22
expires on : 2021-02-25 01:06:22
signed using : ECDSA with SHA256
EC 2021-01-26 02:56:35.139 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
2021-01-26 02:56:35.143 [AIO:XDEB] [3] ws_connecting state=1
2021-01-26 02:56:35.154 [TCE:VERB] Connecting to MUXS…
2021-01-26 02:56:37.154 [TCE:ERRO] TC engine timed out
2021-01-26 02:56:37.155 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)
2021-01-26 02:56:47.190 [any:INFO] ./tc.trust:
cert. version : 3
serial number : 71:8D:F4:FF:AD:E9:50:B3:F3:9D:34:6D:68:CB:E4:8B:F3:3E:4B:04
issuer name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
subject name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
issued on : 2021-01-26 01:06:22
expires on : 2021-02-25 01:06:22
signed using : ECDSA with SHA256
EC 2021-01-26 02:56:47.191 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
2021-01-26 02:56:47.194 [AIO:XDEB] [3] ws_connecting state=1
2021-01-26 02:56:47.196 [TCE:INFO] Connecting to INFOS: wss://localhost:3001
2021-01-26 02:56:50.910 [AIO:XDEB] [3] ws_connecting state=1
2021-01-26 02:56:56.377 [AIO:XDEB] [3] ws_connecting state=1
2021-01-26 02:56:56.379 [AIO:XDEB] [3] ws_connecting state=2
2021-01-26 02:56:56.389 [AIO:XDEB] [3] ws_connecting state=3
2021-01-26 02:56:56.389 [AIO:XDEB] [3|WS] > {“router”:“80:0:a000:946”}
2021-01-26 02:56:56.392 [AIO:XDEB] [3|WS] < {“router”:“0080:0000:a000:0946”,“muxs”:“0080:0000:a000:0946”,“uri”:“wss://localhost:3001/gateway/00800000a0000946”}
2021-01-26 02:56:56.392 [TCE:INFO] Infos: 0080:0000:a000:0946 0080:0000:a000:0946 wss://localhost:3001/gateway/00800000a0000946
2021-01-26 02:56:56.393 [AIO:DEBU] [3] ws_close reason=1000
2021-01-26 02:56:56.401 [AIO:ERRO] Recv failed: SSL - The peer notified us that the connection is going to be closed
2021-01-26 02:56:56.401 [AIO:DEBU] [3] WS connection shutdown…
2021-01-26 02:56:56.404 [any:INFO] ./tc.trust:
cert. version : 3
serial number : 71:8D:F4:FF:AD:E9:50:B3:F3:9D:34:6D:68:CB:E4:8B:F3:3E:4B:04
issuer name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
subject name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
issued on : 2021-01-26 01:06:22
expires on : 2021-02-25 01:06:22
signed using : ECDSA with SHA256
EC 2021-01-26 02:56:56.404 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
2021-01-26 02:56:56.408 [AIO:XDEB] [3] ws_connecting state=1
2021-01-26 02:56:56.449 [TCE:VERB] Connecting to MUXS…
2021-01-26 02:56:58.450 [TCE:ERRO] TC engine timed out
2021-01-26 02:56:58.451 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)
2021-01-26 02:57:08.455 [any:INFO] ./tc.trust:
cert. version : 3
serial number : 71:8D:F4:FF:AD:E9:50:B3:F3:9D:34:6D:68:CB:E4:8B:F3:3E:4B:04
issuer name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
subject name : C=US, ST=Minnesota, L=Blaine, O=BT-Company, OU=BT-Company, CN=localhost, emailAddress=test@test.com
issued on : 2021-01-26 01:06:22
expires on : 2021-02-25 01:06:22

Any ideas?

Thanks,

BT

Hi Guys,

I tested with TTI and it is working. But switch back to use chirpstack-gateway-bridge and it did not work and I am getting the same error. It looks to me, there is an issue with chirpstack-gateway-bridge.

Any ideas on how to fix this?

root@mtcdt:/var/run/lora/1# ./station
2021-01-26 16:24:07.913 [SYS:INFO] Logging : stderr (maxsize=100000, rotate=3)
2021-01-26 16:24:07.913 [SYS:INFO] Station Ver : 2.0.5(mlinux/std) 2020-10-19 19:44:13
2021-01-26 16:24:07.913 [SYS:INFO] Package Ver : (null)
2021-01-26 16:24:07.914 [SYS:INFO] proto EUI : 80:0:a000:3359 (station.conf)
2021-01-26 16:24:07.914 [SYS:INFO] prefix EUI : ::0 (station.conf)
2021-01-26 16:24:07.914 [SYS:INFO] Station EUI : 80:0:a000:3359
2021-01-26 16:24:07.914 [SYS:INFO] Station home: ./ (builtin)
2021-01-26 16:24:07.914 [SYS:INFO] Station temp: /var/tmp/ (builtin)
2021-01-26 16:24:07.914 [SYS:WARN] Station in NO-CUPS mode
2021-01-26 16:24:08.117 [TCE:INFO] Starting TC engine
2021-01-26 16:24:08.140 [any:INFO] ./tc.trust:
cert. version : 3
serial number : 40:01:75:04:83:14:A4:C8:21:8C:84:A9:0C:16:CD:DF
issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
subject name : C=US, O=Let’s Encrypt, CN=R3
issued on : 2020-10-07 19:21:40
expires on : 2021-09-29 19:21:40
signed using : RSA with SHA-256
RSA key size : 2048 bits
basic constraints : CA=true, max_pathlen=0
key usage : Digital Signature, Key Cert Sign, CRL Sign
ex2021-01-26 16:24:08.141 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
2021-01-26 16:24:08.350 [TCE:INFO] Connecting to INFOS: wss://multitech.eu1.cloud.thethings.industries:8887
2021-01-26 16:24:09.411 [TCE:INFO] Infos: 80::a000:3359 muxs-::0 wss://multitech.eu1.cloud.thethings.industries:8887/traffic/eui-00800000A0003359
2021-01-26 16:24:09.411 [AIO:DEBU] [3] ws_close reason=1000
2021-01-26 16:24:09.412 [AIO:ERRO] Recv failed: SSL - The peer notified us that the connection is going to be closed
2021-01-26 16:24:09.412 [AIO:DEBU] [3] WS connection shutdown…
2021-01-26 16:24:09.415 [any:INFO] ./tc.trust:
cert. version : 3
serial number : 40:01:75:04:83:14:A4:C8:21:8C:84:A9:0C:16:CD:DF
issuer name : O=Digital Signature Trust Co., CN=DST Root CA X3
subject name : C=US, O=Let’s Encrypt, CN=R3
issued on : 2020-10-07 19:21:40
expires on : 2021-09-29 19:21:40
signed using : RSA with SHA-256
RSA key size : 2048 bits
basic constraints : CA=true, max_pathlen=0
key usage : Digital Signature, Key Cert Sign, CRL Sign
ex2021-01-26 16:24:09.415 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
2021-01-26 16:24:09.558 [TCE:VERB] Connecting to MUXS…
2021-01-26 16:24:10.633 [TCE:VERB] Connected to MUXS.
2021-01-26 16:24:10.770 [S2E:WARN] Feature not supported in production level code (router_config) - ignored: nocca
2021-01-26 16:24:10.771 [S2E:WARN] Feature not supported in production level code (router_config) - ignored: nodc
2021-01-26 16:24:10.771 [S2E:WARN] Feature not supported in production level code (router_config) - ignored: nodwell
2021-01-26 16:24:12.248 [RAL:WARN] Ignoring unsupported/unknown field: antenna_gain
2021-01-26 16:24:12.248 [RAL:INFO] Lora gateway library version: Version: 5.0.1-mts-5;
2021-01-26 16:24:12.301 [RAL:VERB] Connecting to device: /dev/spidev0.0
2021-01-26 16:24:12.301 [RAL:DEBU] SX130x txlut table (16 entries)
2021-01-26 16:24:12.301 [RAL:VERB] SX1301 txlut 0: dig_gain=0 pa_gain=0 dac_gain=3 mix_gain=11 rf_power=-6
2021-01-26 16:24:12.301 [RAL:VERB] SX1301 txlut 1: dig_gain=0 pa_gain=0 dac_gain=3 mix_gain=13 rf_power=-3
2021-01-26 16:24:12.301 [RAL:VERB] SX1301 txlut 2: dig_gain=0 pa_gain=1 dac_gain=3 mix_gain=9 rf_power=0
2021-01-26 16:24:12.301 [RAL:VERB] SX1301 txlut 3: dig_gain=0 pa_gain=1 dac_gain=3 mix_gain=10 rf_power=3
2021-01-26 16:24:12.301 [RAL:VERB] SX1301 txlut 4: dig_gain=0 pa_gain=1 dac_gain=3 mix_gain=12 rf_power=6
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 5: dig_gain=0 pa_gain=2 dac_gain=3 mix_gain=10 rf_power=10
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 6: dig_gain=0 pa_gain=2 dac_gain=3 mix_gain=11 rf_power=11
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 7: dig_gain=0 pa_gain=2 dac_gain=3 mix_gain=11 rf_power=12
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 8: dig_gain=2 pa_gain=2 dac_gain=3 mix_gain=12 rf_power=13
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 9: dig_gain=0 pa_gain=2 dac_gain=3 mix_gain=13 rf_power=14
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 10: dig_gain=0 pa_gain=2 dac_gain=3 mix_gain=15 rf_power=16
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 11: dig_gain=0 pa_gain=3 dac_gain=3 mix_gain=10 rf_power=20
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 12: dig_gain=0 pa_gain=3 dac_gain=3 mix_gain=12 rf_power=23
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 13: dig_gain=0 pa_gain=3 dac_gain=3 mix_gain=13 rf_power=25
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 14: dig_gain=0 pa_gain=3 dac_gain=3 mix_gain=15 rf_power=26
2021-01-26 16:24:12.302 [RAL:VERB] SX1301 txlut 15: dig_gain=0 pa_gain=3 dac_gain=3 mix_gain=15 rf_power=27
2021-01-26 16:24:12.303 [RAL:VERB] SX1301 rxrfchain 0: enable=1 freq=904.3MHz rssi_offset=-166.000000 type=2 tx_enable=1 tx_notch_freq=0
2021-01-26 16:24:12.303 [RAL:VERB] SX1301 rxrfchain 1: enable=1 freq=905.0MHz rssi_offset=-166.000000 type=2 tx_enable=0 tx_notch_freq=0
2021-01-26 16:24:12.303 [RAL:VERB] SX1301 ifchain 0: enable=1 rf_chain=0 freq=-400000 bandwidth=0 datarate=0 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 1: enable=1 rf_chain=0 freq=-200000 bandwidth=0 datarate=0 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 2: enable=1 rf_chain=0 freq=0 bandwidth=0 datarate=0 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 3: enable=1 rf_chain=0 freq=200000 bandwidth=0 datarate=0 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 4: enable=1 rf_chain=1 freq=-300000 bandwidth=0 datarate=0 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 5: enable=1 rf_chain=1 freq=-100000 bandwidth=0 datarate=0 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 6: enable=1 rf_chain=1 freq=100000 bandwidth=0 datarate=0 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 7: enable=1 rf_chain=1 freq=300000 bandwidth=0 datarate=0 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 8: enable=1 rf_chain=0 freq=300000 bandwidth=1 datarate=4 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX1301 ifchain 9: enable=0 rf_chain=0 freq=300000 bandwidth=3 datarate=50000 sync_word=0/0
2021-01-26 16:24:12.304 [RAL:VERB] SX130x LBT not enabled
2021-01-26 16:24:12.305 [RAL:VERB] Station device: /dev/spidev0.0 (PPS capture enabled)
INFO: FPGA supported features: [TX filter] [Spectral Scan] [LBT]
2021-01-26 16:24:15.747 [RAL:VERB] Concentrator started (3s441ms)
2021-01-26 16:24:15.747 [S2E:INFO] Configuring for region: US902 – 923.0MHz…928.0MHz
2021-01-26 16:24:15.747 [S2E:VERB] DR0 SF10/BW125
2021-01-26 16:24:15.747 [S2E:VERB] DR1 SF9/BW125
2021-01-26 16:24:15.748 [S2E:VERB] DR2 SF8/BW125
2021-01-26 16:24:15.748 [S2E:VERB] DR3 SF7/BW125
2021-01-26 16:24:15.748 [S2E:VERB] DR4 SF8/BW500
2021-01-26 16:24:15.748 [S2E:VERB] DR5 FSK
2021-01-26 16:24:15.748 [S2E:VERB] DR6 FSK
2021-01-26 16:24:15.748 [S2E:VERB] DR7 FSK
2021-01-26 16:24:15.748 [S2E:VERB] DR8 SF12/BW500
2021-01-26 16:24:15.748 [S2E:VERB] DR9 SF11/BW500
2021-01-26 16:24:15.748 [S2E:VERB] DR10 SF10/BW500
2021-01-26 16:24:15.748 [S2E:VERB] DR11 SF9/BW500
2021-01-26 16:24:15.748 [S2E:VERB] DR12 SF8/BW500
2021-01-26 16:24:15.748 [S2E:VERB] DR13 SF7/BW500
2021-01-26 16:24:15.748 [S2E:VERB] DR14 FSK
2021-01-26 16:24:15.749 [S2E:VERB] DR15 FSK
2021-01-26 16:24:15.749 [S2E:VERB] TX power: 30.0 dBm EIRP
2021-01-26 16:24:15.749 [S2E:VERB] JoinEui list: 0 entries
2021-01-26 16:24:15.749 [S2E:VERB] NetID filter: FFFFFFFF-FFFFFFFF-FFFFFFFF-FFFFFFFF
2021-01-26 16:24:15.749 [S2E:VERB] Dev/test settings: nocca=0 nodc=0 nodwell=0
at+2021-01-26 16:24:40.757 [S2E:VERB] RX 904.6MHz DR4 SF8/BW500 snr=10.0 rssi=-43 xtime=0x9E000001A3029E - jreq MHdr=00 JoinEui=aabb:ccdd:eeff:9988 DevEui=80:0:400:8b8 DevNonce=38 MIC=1280424024
2021-01-26 16:24:42.751 [S2E:DEBU] ::0 diid=44317 [ant#0] - next TX start ahead by 2s983ms
INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
2021-01-26 16:24:45.715 [S2E:VERB] ::0 diid=44317 [ant#0] - starting TX in 19ms819us
2021-01-26 16:24:45.741 [S2E:INFO] TX ::0 diid=44317 [ant#0] - on air: 923.9MHz 30.0dBm ant#0(0) DR13 SF7/BW500 frame=203F8B3A2E54AC3EDCB20287…B74DDF99
2021-01-26 16:24:45.753 [S2E:DEBU] Tx done diid=44317
2021-01-26 16:24:50.768 [S2E:DEBU] Dropped mirror frame freq=904.9MHz snr= -3.8 rssi=-94 (vs. freq=903.9MHz snr= 8.2 rssi=-42) - DR0 mic=22540519 (16 byes)
2021-01-26 16:24:50.769 [S2E:VERB] RX 903.9MHz DR0 SF10/BW125 snr=8.2 rssi=-42 xtime=0x9E0000023BFB74 - updf mhdr=80 DevAddr=26083BFB FCtrl=81 FCnt=0 FOpts=[0D] 01AFA6 mic=22540519 (16 bytes)
2021-01-26 16:24:51.497 [S2E:DEBU] ::0 diid=44356 [ant#0] - next TX start ahead by 4s262ms
2021-01-26 16:24:53.593 [SYN:INFO] First PPS pulse acquired
2021-01-26 16:24:53.593 [SYN:INFO] Obtained initial PPS offset (231229) - starting timesync with LNS
2021-01-26 16:24:53.671 [SYN:DEBU] Timesync #2 sent to server
2021-01-26 16:24:53.742 [SYN:DEBU] Timesync #3 sent to server
2021-01-26 16:24:53.814 [SYN:DEBU] Timesync #4 sent to server
2021-01-26 16:24:53.885 [SYN:DEBU] Timesync #5 sent to server
2021-01-26 16:24:53.956 [SYN:DEBU] Timesync #6 sent to server
2021-01-26 16:24:54.028 [SYN:DEBU] Timesync #7 sent to server
2021-01-26 16:24:54.099 [SYN:DEBU] Timesync #8 sent to server
2021-01-26 16:24:54.170 [SYN:DEBU] Timesync #9 sent to server
2021-01-26 16:24:54.242 [SYN:DEBU] Timesync #10 sent to server
2021-01-26 16:24:54.313 [SYN:DEBU] Timesync #11 sent to server
INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
2021-01-26 16:24:55.817 [S2E:VERB] ::0 diid=44356 [ant#0] - starting TX in 19ms765us
2021-01-26 16:24:55.847 [S2E:INFO] TX ::0 diid=44356 [ant#0] - on air: 923.3MHz 30.0dBm ant#0(0) DR10 SF10/BW500 frame=60FB3B0826AC00000DE4043B…C6C1E2B6
2021-01-26 16:24:55.930 [S2E:DEBU] Tx done diid=44356
2021-01-26 16:24:57.426 [SYN:INFO] MCU/SX130X drift stats: min: +0.0ppm q50: +2.9ppm q80: -5.2ppm max: -14.3ppm - threshold q90: +10.5ppm
2021-01-26 16:24:57.426 [SYN:INFO] Mean MCU drift vs SX130X#0: -1.8ppm
2021-01-26 16:24:59.316 [SYN:DEBU] Timesync #12 sent to server
2021-01-26 16:24:59.387 [SYN:DEBU] Timesync #13 sent to server
2021-01-26 16:24:59.458 [SYN:DEBU] Timesync #14 sent to server
2021-01-26 16:24:59.529 [SYN:DEBU] Timesync #15 sent to server
2021-01-26 16:24:59.600 [SYN:DEBU] Timesync #16 sent to server
2021-01-26 16:24:59.672 [SYN:DEBU] Timesync #17 sent to server
2021-01-26 16:24:59.743 [SYN:DEBU] Timesync #18 sent to server
2021-01-26 16:24:59.814 [SYN:DEBU] Timesync #19 sent to server
2021-01-26 16:24:59.885 [SYN:DEBU] Timesync #20 sent to server
2021-01-26 16:24:59.957 [SYN:DEBU] Timesync #21 sent to server

Never Mind Guys. Got it running…Thanks.

Cool :sunglasses:Any chance of documenting what you did in case someone else has a similar issue?

Looks like you were not connecting to the ChirpStack Gateway Bridge?

Hi brocaar,

Sorry for the delay. Yes. You are correct. I was not.

That log is a log that I am trying to verify if my gateway’s Basic Station is working or not by trying to connect to the TTI network and it did successfully connected to the TTI network.

Thanks,

BT

Hi Guys,

Here is the configuration that I was able to get Multitech Conduit Basic Station to work with ChirpStack LNS

Conduit setup:

  • LoRaWan -> Network Settings -> LoRa Mode -> Basic Station
  • Credential -> LNS
  • URI: ws://xxx.xxx.xxx.xxxx:3001 <–xxx.xxx.xxx.xxx (IP address of the PC that run chirpstack-gateway-bridge)
  • Station.conf (Note: Frequency Subband 2)

{
“SX1301_conf”: {
“chan_FSK”: {
“bandwidth”: 125000,
“datarate”: 50000,
“enable”: true,
“if”: 300000,
“radio”: 0
},
“chan_Lora_std”: {
“bandwidth”: 250000,
“enable”: true,
“if”: -200000,
“radio”: 0,
“spread_factor”: 7
},
“chan_multiSF_0”: {
“enable”: true,
“if”: -400000,
“radio”: 0
},
“chan_multiSF_1”: {
“enable”: true,
“if”: -200000,
“radio”: 0
},
“chan_multiSF_2”: {
“enable”: true,
“if”: 0,
“radio”: 0
},
“chan_multiSF_3”: {
“enable”: true,
“if”: -400000,
“radio”: 1
},
“chan_multiSF_4”: {
“enable”: true,
“if”: -200000,
“radio”: 1
},
“chan_multiSF_5”: {
“enable”: true,
“if”: 0,
“radio”: 1
},
“chan_multiSF_6”: {
“enable”: true,
“if”: 200000,
“radio”: 1
},
“chan_multiSF_7”: {
“enable”: true,
“if”: 400000,
“radio”: 1
},
“clksrc”: 0,
“device”: “/dev/spidev0.0”,
“lorawan_public”: true,
“pps”: true,
“radio_0”: {
“enable”: true,
“freq”: 904300000,
“rssi_offset”: -162,
“tx_enable”: true,
“type”: “SX1257”
},
“radio_1”: {
“enable”: true,
“freq”: 905000000,
“rssi_offset”: -162,
“tx_enable”: false,
“type”: “SX1257”
},
“tx_gain_lut”: [
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 0,
“rf_power”: -6
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 0,
“rf_power”: -3
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 9,
“pa_gain”: 1,
“rf_power”: 0
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 1,
“rf_power”: 3
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 12,
“pa_gain”: 1,
“rf_power”: 6
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 2,
“rf_power”: 10
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 2,
“rf_power”: 11
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 2,
“rf_power”: 12
},
{
“dac_gain”: 3,
“dig_gain”: 2,
“mix_gain”: 12,
“pa_gain”: 2,
“rf_power”: 13
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 2,
“rf_power”: 14
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 2,
“rf_power”: 16
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 3,
“rf_power”: 20
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 12,
“pa_gain”: 3,
“rf_power”: 23
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 3,
“rf_power”: 25
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 3,
“rf_power”: 26
},
{
“dac_gain”: 3,
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 3,
“rf_power”: 27
}
]
},
“station_conf”: {
“TC_TIMEOUT”: “2s”,
“euiprefix”: “::0”,
“log_file”: “stderr”,
“log_level”: “DEBUG”,
“log_rotate”: 3,
“log_size”: 100000,
“routerid”: “”
}
}

  • Click on the ‘Submit’ button and do a save and apply

chirpstack-gateway-bridge.toml

[general]
#debug=5, info=4, warning=3, error=2, fatal=1, panic=0
log_level=5

#Log to syslog.

#When set to true, log messages are being written to syslog.
log_to_syslog=false

#Filters.

#These can be used to filter LoRaWAN frames to reduce bandwith usage between
#the gateway and ChirpStack Gateway Bridge. Depending the used backend, filtering
#will be performed by the Packet Forwarder or ChirpStack Gateway Bridge.
[filters]

#NetIDs filters.

#The configured NetIDs will be used to filter uplink data frames.
#When left blank, no filtering will be performed on NetIDs.

#Example:
#net_ids=[
#“000000”,
#“000001”,
#]
net_ids=[
]

#JoinEUI filters.

#The configured JoinEUI ranges will be used to filter join-requests.
#When left blank, no filtering will be performed on JoinEUIs.

#Example:
#join_euis=[
#[“0000000000000000”, “00000000000000ff”],
#[“000000000000ff00”, “000000000000ffff”],
#]
join_euis=[
]

#Gateway backend configuration.
[backend]

#Backend type.

#Valid options are:
#* semtech_udp
#* concentratord
#* basic_station
type=“basic_station”

#Semtech UDP packet-forwarder backend.
[backend.semtech_udp]

#ip:port to bind the UDP listener to

#Example: 0.0.0.0:1700 to listen on port 1700 for all network interfaces.
#This is the listener to which the packet-forwarder forwards its data
#so make sure the ‘serv_port_up’ and ‘serv_port_down’ from your
#packet-forwarder matches this port.
#udp_bind = “0.0.0.0:1700”

#Skip the CRC status-check of received packets

#This is only has effect when the packet-forwarder is configured to forward
#LoRa frames with CRC errors.
skip_crc_check = false

#Fake RX timestamp.

#Fake the RX time when the gateway does not have GPS, in which case
#the time would otherwise be unset.
fake_rx_time=false

#ChirpStack Concentratord backend.
[backend.concentratord]

#Check for CRC OK.
crc_check=true

#Event API URL.
event_url=“ipc:///tmp/concentratord_event”

#Command API URL.
command_url=“ipc:///tmp/concentratord_command”

#Basic Station backend.
[backend.basic_station]

#ip:port to bind the Websocket listener to.
#bind=“192.168.2.12:3001”
bind=":3001"

#TLS certificate and key files.

#When set, the websocket listener will use TLS to secure the connections
#between the gateways and ChirpStack Gateway Bridge (optional).
#tls_cert=“I:\ChirpStack\chirpstack\chirpstack-gateway-bridge_3.10.0_windows_amd64\server.crt”
#tls_key=“I:\ChirpStack\chirpstack\chirpstack-gateway-bridge_3.10.0_windows_amd64\server.key”
tls_cert=""
tls_key="

#TLS CA certificate.

#When configured, ChirpStack Gateway Bridge will validate that the client
#certificate of the gateway has been signed by this CA certificate.
ca_cert=""

#Stats interval.

#This defines the interval in which the ChirpStack Gateway Bridge forwards
#the uplink / downlink statistics.
stats_interval=“30s”

#Ping interval.
ping_interval=“1m0s”

#Read timeout.

#This interval must be greater than the configured ping interval.
read_timeout=“1m5s”

#Write timeout.
write_timeout=“1s”

#Region.

#Please refer to the LoRaWAN Regional Parameters specification
#for the complete list of common region names.
region=“US915”

#Minimal frequency (Hz).
frequency_min=902000000

#Maximum frequency (Hz).
frequency_max=928000000

#Minimal frequency (Hz).
#frequency_min=863000000

#Maximum frequency (Hz).
#frequency_max=870000000

#Concentrator configuration.

#This section contains the configuration for the SX1301 concentrator chips.
#Example:
[[backend.basic_station.concentrators]]

##Multi-SF channel configuration.
[backend.basic_station.concentrators.multi_sf]

##Frequencies (Hz).
#frequencies=[
#868100000,
#868300000,
#868500000,
#867100000,
#867300000,
#867500000,
#867700000,
#867900000,
#]

frequencies=[
903900000,
904100000,
904300000,
904500000,
904700000,
904900000,
905100000,
905300000,
]

#Frequency (Hz).
#frequency=868300000
frequency=904600000

#Bandwidth (Hz).
#bandwidth=250000
bandwidth=500000

#Spreading factor.
#spreading_factor=10
spreading_factor=8

#LoRa STD channel.
#[backend.basic_station.concentrators.lora_std]

#Frequency (Hz).
#frequency=868300000

#Bandwidth (Hz).
#bandwidth=250000

#Spreading factor.
#spreading_factor=7

#FSK channel.
#[backend.basic_station.concentrators.fsk]

#Frequency (Hz).
#frequency=868800000

#Integration configuration.
[integration]
#Payload marshaler.

#This defines how the MQTT payloads are encoded. Valid options are:
#*protobuf: Protobuf encoding
#*json: JSON encoding (easier for debugging, but less compact than ‘protobuf’)
marshaler=“json”

#MQTT integration configuration.
[integration.mqtt]
#Event topic template.
event_topic_template=“gateway/{{ .GatewayID }}/event/{{ .EventType }}”

#Command topic template.
command_topic_template=“gateway/{{ .GatewayID }}/command/#”

#Keep alive will set the amount of time (in seconds) that the client should
#wait before sending a PING request to the broker. This will allow the client
#to know that a connection has not been lost with the server.
#Valid units are ‘ms’, ‘s’, ‘m’, ‘h’. Note that these values can be combined, e.g. ‘24h30m15s’.
keep_alive=“30s”

#Maximum interval that will be waited between reconnection attempts when connection is lost.
#Valid units are ‘ms’, ‘s’, ‘m’, ‘h’. Note that these values can be combined, e.g. ‘24h30m15s’.
max_reconnect_interval=“1m0s”

#Terminate on connect error.

#When set to true, instead of re-trying to connect, the ChirpStack Gateway Bridge
#process will be terminated on a connection error.
terminate_on_connect_error=false

#MQTT authentication.
[integration.mqtt.auth]
#Type defines the MQTT authentication type to use.

#Set this to the name of one of the sections below.
type=“generic”

#Generic MQTT authentication.
[integration.mqtt.auth.generic]
#MQTT servers.
#
#Configure one or multiple MQTT server to connect to. Each item must be in
#the following format: scheme://host:port where scheme is tcp, ssl or ws.
servers=[
“tcp://127.0.0.1:1883”,
]

#Connect with the given username (optional)
username=""

#Connect with the given password (optional)
password=""

#Quality of service level
#
#0: at most once
#1: at least once
#2: exactly once
#
#Note: an increase of this value will decrease the performance.
#For more information: https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels
qos=0

#Clean session
#
#Set the “clean session” flag in the connect message when this client
#connects to an MQTT broker. By setting this flag you are indicating
#that no messages saved by the broker for this client should be delivered.
clean_session=true

#Client ID
#
#Set the client id to be used by this client when connecting to the MQTT
#broker. A client id must be no longer than 23 characters. When left blank,
#a random id will be generated. This requires clean_session=true.
client_id=""

#CA certificate file (optional)
#
#Use this when setting up a secure connection (when server uses ssl://…)
#but the certificate used by the server is not trusted by any CA certificate
#on the server (e.g. when self generated).
ca_cert=""

#mqtt TLS certificate file (optional)
tls_cert=""

#mqtt TLS key file (optional)
tls_key=""

#Google Cloud Platform Cloud IoT Core authentication.
#
#Please note that when using this authentication type, the MQTT topics
#will be automatically set to match the MQTT topics as expected by
#Cloud IoT Core.
[integration.mqtt.auth.gcp_cloud_iot_core]
#MQTT server.
server=“ssl://mqtt.googleapis.com:8883”

#Google Cloud IoT Core Device id.
device_id=""

#Google Cloud project id.
project_id=""

#Google Cloud region.
cloud_region=""

#Google Cloud IoT registry id.
registry_id=""

#JWT token expiration time.
jwt_expiration=“24h0m0s”

#JWT token key-file.

#Example command to generate a key-pair:
#$ ssh-keygen -t rsa -b 4096 -f private-key.pem
#$ openssl rsa -in private-key.pem -pubout -outform PEM -out public-key.pem
#
#Then point the setting below to the private-key.pem and associate the
#public-key.pem with this device / gateway in Google Cloud IoT Core.
jwt_key_file=""

#Azure IoT Hub

#This setting will preset uplink and downlink topics that will only
#work with Azure IoT Hub service.
[integration.mqtt.auth.azure_iot_hub]

#Device connection string (symmetric key authentication).
#
#This connection string can be retrieved from the Azure IoT Hub device
#details when using the symmetric key authentication type.
device_connection_string=""

#Token expiration (symmetric key authentication).

#ChirpStack Gateway Bridge will generate a SAS token with the given expiration.
#After the token has expired, it will generate a new one and trigger a
#re-connect (only for symmetric key authentication).
sas_token_expiration=“24h0m0s”

#Device ID (X.509 authentication).
#
#This will be automatically set when a device connection string is given.
#It must be set for X.509 authentication.
device_id=""

#IoT Hub hostname (X.509 authentication).
#
#This will be automatically set when a device connection string is given.
#It must be set for X.509 authentication.
#Example: iot-hub-name.azure-devices.net
hostname=""

#Client certificates (X.509 authentication).
#
#Configure the tls_cert (certificate file) and tls_key (private-key file)
#when the device is configured with X.509 authentication.
tls_cert=""
tls_key=""

#Metrics configuration.
[metrics]

#Metrics stored in Prometheus.

#These metrics expose information about the state of the ChirpStack Gateway Bridge
#instance like number of messages processed, number of function calls, etc.
[metrics.prometheus]
#Expose Prometheus metrics endpoint.
endpoint_enabled=false

#The ip:port to bind the Prometheus metrics server to for serving the
#metrics endpoint.
bind=""

#Gateway meta-data.

#The meta-data will be added to every stats message sent by the ChirpStack Gateway
#Bridge.
[meta_data]

#Static.

#Static key (string) / value (string) meta-data.
[meta_data.static]
#Example:
#serial_number=“A1B21234”

#Dynamic meta-data.

#Dynamic meta-data is retrieved by executing external commands.
#This makes it possible to for example execute an external command to
#read the gateway temperature.
[meta_data.dynamic]

#Execution interval of the commands.
execution_interval=“1m0s”

#Max. execution duration.
max_execution_duration=“1s”

#Split delimiter.

#When the output of a command returns multiple lines, ChirpStack Gateway Bridge
#assumes multiple values are returned. In this case it will split by the given delimiter
#to obtain the key / value of each row. The key will be prefixed with the name of the
#configured command.
split_delimiter="="

#Commands to execute.

#The value of the stdout will be used as the key value (string).
#In case the command failed, it is ignored. In case the same key is defined
#both as static and dynamic, the dynamic value has priority (as long as the)
#command does not fail.
[meta_data.dynamic.commands]
#Example:
#temperature="/opt/gateway-temperature/gateway-temperature.sh"

#Executable commands.

#The configured commands can be triggered by sending a message to the
#ChirpStack Gateway Bridge.
[commands]
#Example:
#[commands.commands.reboot]
#max_execution_duration=“1s”
#command="/usr/bin/reboot"

chirpstack-network-server.toml


#Example: (sub-band 1)
#enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7, 64]
#Exmaple: (sub-band 2)
enabled_uplink_channels=[8, 9, 10, 11, 12, 13, 14, 15, 65]
#enabled_uplink_channels=[]

===================================

Thanks,

BT