ChirpStack MQTT Forwarder and ChirpStack Concentrator with uci in ChirpStack Gateway OS

devleesch001 · November 18, 2024, 8:22pm

Hello,

I need to configure the ChirpStack MQTT Forwarder and ChirpStack Concentrator in an advanced way in ChirpStack Gateway OS.

I understand the uci configuration allows to generate the configuration files when the init.d chirpstack services in openWrt are restarted.

The uci configuration can be modified from the LuCI web interface or via the uci cli.

However the configuration files of the ChirpStack MQTT Forwarder and ChirpStack Concentrator applications do not seem to be fully implemented with the uci configuration system.

For example the commands and metadata of the ChirpStack MQTT Forwarder do not seem to be implemented.

[metadata]
[metadata.static]
serial_number="1234"
[metadata.commands]
datetime=["date", "-R"]

[commands]
reboot=["/usr/bin/reboot"]

And, the gateway_id configuration for the concentrator only works with the semtech sx1301 chips.

config sx1302
	option gateway_id '0000000000000000'

[gateway]
gateway_id="0000000000000000"

Is this planned, or can I contribute to implement it, at least for the uci cli.

I started working on the subject on my side.

Is there any uci documentation for chirpstack services or does everything go through the interface?

Thanks in advance if you have more info.

brocaar · November 19, 2024, 8:42am

Contributions are welcome

Is there any uci documentation for chirpstack services or does everything go through the interface?

There is no documentation, about this, but I’m using the OpenWrt utilities for this. For the MQTT Forwarder you can find the implementation here:

github.com

chirpstack/chirpstack-openwrt-feed/blob/master/chirpstack/chirpstack-mqtt-forwarder/files/chirpstack-mqtt-forwarder.sh

. /lib/functions.sh

configure() {
    local config_name="$1"

    mkdir -p /var/etc/$config_name
    echo "" > /var/etc/$config_name/chirpstack-mqtt-forwarder.toml

	cat >> /var/etc/$config_name/chirpstack-mqtt-forwarder.toml <<- EOF
		[logging]
			log_to_syslog=true
		
		[backend]
			enabled="concentratord"
	EOF

	config_load "$config_name"
	config_foreach conf_rule_concentratord "concentratord" "$config_name"
	config_foreach conf_rule_mqtt "mqtt" "$config_name"
	config_foreach conf_rule_filters "filters" "$config_name"

This file has been truncated. show original

For the Concentratord:

github.com

chirpstack/chirpstack-openwrt-feed/blob/master/chirpstack/chirpstack-concentratord/files/chirpstack-concentratord.sh

. /lib/functions.sh

configure() {
	local config_name="$1"
	mkdir -p /var/etc/$config_name
	config_load "$config_name"
	config_foreach conf_rule_global "global" "$config_name"
}

conf_rule_global() {
	local cfg="$1"
	local config_name="$2"
	local chipset

	config_get chipset $cfg chipset
	CHIPSET="$chipset"

	if [ "$chipset" = "sx1301" ]; then
		config_foreach conf_rule_sx1301 "sx1301" "$config_name"
	fi

This file has been truncated. show original

devleesch001 · November 19, 2024, 6:08pm

Hello,

Perfect, thanks for the answer.

I made two Pull Requests.

This one implements the custom gateway_id for sx1302 chipsets

And this one adds the management of commands, metadata.

github.com/chirpstack/chirpstack-openwrt-feed

Feat uci mqtt forwarder add commands and metadata

chirpstack:master ← devleesch001:feat-uci-mqtt-forwarder-add-commands-and-metadata

opened 09:43AM - 19 Nov 24 UTC

devleesch001

+111 -7

Implemente `Commands` and `Metadata` of `chirpstack-mqtt-forwarder` with UCI in …`chirpstack-mqtt-forwarder.sh` for openWrt init.d service. UCI config file ```uci config commands 'reboot' option command '["/usr/bin/reboot"]' config commands 'shutdown' option command '["/usr/bin/shutdown"]' config metadata 'datetime' option command '["date", "-R"]' config metadata 'serial_number' option static '1234' ``` generate ```yaml [metadata] [metadata.static] serial_number=1234 [metadata.commands] datetime=["date", "-R"] [commands] reboot=["/usr/bin/reboot"] shutdown=["/usr/bin/shutdown"] ```

All this from the uci cli only

devleesch001 · December 16, 2024, 10:05am

All merged thanks you

system · February 16, 2025, 8:23pm

This topic was automatically closed after 90 days. New replies are no longer allowed.