[release] ChirpStack Gateway OS v4.2 test releases

v4.2.0-test.1

Features

This is a very exciting release, as this release migrates the ChirpStack Gateway OS from Yocto to OpenWrt. Thanks to LuCI and the UCI configuration system it is now possible to configure the provided ChirpStack components as well thinks like network configuration through a web-interface instead of a CLI. This release also splits the packages from the ChirpStack Gateway OS configuration such that these can be integrated in other OpenWrt based projects. Main features that this release brings:

Web-interface

There is no need to configure the ChipStack Gateway OS using a terminal. Powered by LuCI), the ChirpStack Gateway OS now provides an easy-to-use web-interface to configure ChirpStack components and system configuration.

Custom packages

Through the web-interface (and cli) it is possible to install additional software using the OpenWrt package repositories. This has been requested several times, but until now would require to compile a custom ChirpStack Gateway OS image which would take several hours to complete.

Upgrade notes

Unfortunately it is not possible to migrate from ChirpStack Gateway OS v4.1.1 to ChirpStack Gateway OS v4.2.0. You need to re-flash your SD-Card with the ChirpStack Gateway OS v4.2.0 image.

2 Likes

Hello,

Still the same issue of not supporting the LoRa Go PORT.
The concentratord configuration is not done properly.
I described the issue on the yocto bases OS here: Problem with Sandbox LoRaGo PORT shield conf

On this new version it’s the same situation: I’ve looked into the conf file in /var/etc/chirpstack etc… and the pin is still set to 0 after having chosen the Lora Port Go in the SX1301 conf part of the concentratord web interface. Obviously the gateway id is not updated.

The problem is that even by changing the PIN to 25 in the .toml file and rebooting, it doesn’t work in this case (I guess it can’t work if the gateway-id is not configured properly).

Would be great if this issue could be solved.

Thanks a lot for the good work.

Let me test with my LoRa Go Port shield. In general, there shouldn’t be any need to configure the pin number, this is all embedded in the ChirpStack Concentratord:

This model configuration is automatically selected by:

Again, I’ll see if I can reproduce the issue.

Ok. I don’t know for the OpenWRT solution (well, it seemsn not), but for the Yocto solution, changing the PIN in the .toml had a deterministic impact.
I’ll also try again but I’m not optimistic.

Thanks a lot for taking the time to investigate.

I’ve tried playing with the parameters on the web interface but it doesn’t change thing: concentratord just doesn’t initialize properly.

In the web-interface I have selected SX1301 + Sandbox LoRaGO PORT shield with EU868 and it works as expected.

As an additional test from the CLI (over SSH):

/etc/init.d/chirpstack-concentratord stop

Then:

cd /var/etc/chirpstack-concentratord

concentratord.toml

[concentratord]

# Log level.
#
# Valid options are:
#   * TRACE
#   * DEBUG
#   * INFO
#   * WARN
#   * ERROR
#   * OFF
log_level="INFO"

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

# Statistics interval.
stats_interval="30s"

  # Configuration for the (ZeroMQ based) API.
  [concentratord.api]

  # Event PUB socket bind.
  event_bind="ipc:///tmp/concentratord_event"

  # Command REP socket bind.
  command_bind="ipc:///tmp/concentratord_command"


# LoRa gateway configuration.
[gateway]

# Antenna gain (dB).
antenna_gain=0

# Public LoRaWAN network.
lorawan_public=true

# Region.
#
# The region of the gateway. Options:
#  EU868, US915, CN779, EU433, AU915, CN470, AS923, AS923_2, AS923_3, AS923_4,
#  KR923, IN865, RU864
#
# Not not all the gateway models implement all regions.
region="EU868"

# Gateway vendor / model.
#
# This configures various vendor and model specific settings like the min / max
# frequency, TX gain table.
model="sandbox_lorago_port"

# Gateway vendor / model flags.
model_flags=[]

# Gateway ID.
gateway_id="b827ebfffe31f94b"

# Reset pin.
#
# Note: most model configurations come with a pre-defined reset_pin, in which
# case the setting below will be ignored.
reset_pin=0
  • Note the log_to_syslog=false change!

Then to start by hand:

chirpstack-concentratord-sx1301 -c concentratord.toml -c region.toml -c channels.toml
root@ChirpStack:/var/etc/chirpstack-concentratord# chirpstack-concentratord-sx1301 -c concentratord.toml -c region.toml -c channels.toml 
2023-08-02T13:08:59.035Z INFO  [libconcentratord::reset] Configuring reset pin, dev: /dev/gpiochip0, pin: 25
2023-08-02T13:08:59.036Z INFO  [chirpstack_concentratord_sx1301::cmd::root] Starting Concentratord SX1301 (version: 4.2.0, docs: https://www.chirpstack.io/concentratord/)
2023-08-02T13:08:59.036Z INFO  [libconcentratord::reset] Triggering sx1302 reset
2023-08-02T13:08:59.236Z INFO  [chirpstack_concentratord_sx1301::concentrator] Setting spi device path, spidev_path: /dev/spidev0.0
2023-08-02T13:08:59.236Z INFO  [chirpstack_concentratord_sx1301::concentrator] Setting board configuration, lorawan_public: true, clock_source: 1
2023-08-02T13:08:59.236Z INFO  [chirpstack_concentratord_sx1301::concentrator] Setting up concentrator radios
2023-08-02T13:08:59.236Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring radio, radio: 0, enabled: true, center_freq: 867500000, type: SX1257
2023-08-02T13:08:59.236Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring radio, radio: 1, enabled: true, center_freq: 868500000, type: SX1257
2023-08-02T13:08:59.236Z INFO  [chirpstack_concentratord_sx1301::concentrator] Setting up concentrator channels
2023-08-02T13:08:59.236Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 0, enabled: true, freq: 868100000, rf_chain: 1, if_freq: -400000
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 1, enabled: true, freq: 868300000, rf_chain: 1, if_freq: -200000
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 2, enabled: true, freq: 868500000, rf_chain: 1, if_freq: 0
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 3, enabled: true, freq: 867100000, rf_chain: 0, if_freq: -400000
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 4, enabled: true, freq: 867300000, rf_chain: 0, if_freq: -200000
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 5, enabled: true, freq: 867500000, rf_chain: 0, if_freq: 0
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 6, enabled: true, freq: 867700000, rf_chain: 0, if_freq: 200000
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 7, enabled: true, freq: 867900000, rf_chain: 0, if_freq: 400000
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring Std LoRa channel, enabled: true, freq: 868300000, rf_chain: 1, if_freq: -200000
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Configuring FSK channel, enabled: true, freq: 868800000, rf_chain: 1, if_freq: 300000
2023-08-02T13:08:59.237Z INFO  [chirpstack_concentratord_sx1301::concentrator] Starting the concentrator
2023-08-02T13:09:02.397Z INFO  [libconcentratord::events] Creating socket for publishing events, bind: ipc:///tmp/concentratord_event
2023-08-02T13:09:02.398Z INFO  [libconcentratord::commands] Creating socket for receiving commands, bind: ipc:///tmp/concentratord_command
2023-08-02T13:09:02.398Z INFO  [libconcentratord::jitqueue] Initializing JIT queue, capacity: 32
2023-08-02T13:09:14.303Z INFO  [chirpstack_concentratord_sx1301::handler::uplink] Frame received, uplink_id: 1876312863, count_us: 14548099, freq: 868100000, bw: 125000, mod: LoRa, dr: SF7

Here you go:

root@ChirpStack:/var/etc/chirpstack-concentratord# chirpstack-concentratord-sx1301 -c concentratord.toml

thread ‘main’ panicked at ‘Error parsing config file: Error { inner: Error { inner: TomlError { message: “missing field concentrator”, original: Some(“# Concentratord configuration.\n[concentratord]\n\n# Log level.\n#\n# Valid options are:\n# * TRACE\n# * DEBUG\n# * INFO\n# * WARN\n# * ERROR\n# * OFF\nlog_level="INFO"\n\n# Log to syslog.\n#\n# When set to true, log messages are being written to syslog instead of stdout.\nlog_to_syslog=false\n\n# Statistics interval.\nstats_interval="30s"\n\n # Configuration for the (ZeroMQ based) API.\n [concentratord.api]\n\n # Event PUB socket bind.\n event_bind="ipc:///tmp/concentratord_event"\n\n # Command REP socket bind.\n command_bind="ipc:///tmp/concentratord_command"\n\n\n# LoRa gateway configuration.\n[gateway]\n\n# Antenna gain (dB).\nantenna_gain=0\n\n# Public LoRaWAN network.\nlorawan_public=true\n\n# Region.\n#\n# The region of the gateway. Options:\n# EU868, US915, CN779, EU433, AU915, CN470, AS923, AS923_2, AS923_3, AS923_4,\n# KR923, IN865, RU864\n#\n# Not not all the gateway models implement all regions.\nregion="EU868"\n\n# Gateway vendor / model.\n#\n# This configures various vendor and model specific settings like the min / max\n# frequency, TX gain table.\nmodel="sandbox_lorago_port"\n\n# Gateway vendor / model flags.\nmodel_flags=[]\n\n# Gateway ID.\ngateway_id="0101010101010101"\n\n# Reset pin.\n#\n# Note: most model configurations come with a pre-defined reset_pin, in which\n# case the setting below will be ignored.\nreset_pin=0\n”), keys: [“gateway”], span: Some(589…1314) } } }’, chirpstack-concentratord-sx1301/src/config/mod.rs:178:62
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

Any clue to what’s going on? I didn’t do anything stange…

I might have a clue though: can you check the download links there ? It seems to me they are all the same, at least for base which I’m using (for the record I have a Raspi 3B v1.2).

Thanks again for taking the time!

So I reflashed the gateway from the beginning and it didn’t work. I reapplied your recommended actions and here is what I got:

root@ChirpStack:/var/etc/chirpstack-concentratord# chirpstack-concentratord-sx13
01 -c concentratord.toml -c region.toml -c channels.toml
2023-08-02T19:52:55.720Z INFO [libconcentratord::reset] Configuring reset pin, dev: /dev/gpiochip0, pin: 25
2023-08-02T19:52:55.720Z INFO [chirpstack_concentratord_sx1301::cmd::root] Starting Concentratord SX1301 (version: 4.2.0, docs: Introduction - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server)
2023-08-02T19:52:55.720Z INFO [libconcentratord::reset] Triggering sx1302 reset
2023-08-02T19:52:55.920Z INFO [chirpstack_concentratord_sx1301::concentrator] Setting spi device path, spidev_path: /dev/spidev0.0
2023-08-02T19:52:55.920Z INFO [chirpstack_concentratord_sx1301::concentrator] Setting board configuration, lorawan_public: true, clock_source: 1
2023-08-02T19:52:55.920Z INFO [chirpstack_concentratord_sx1301::concentrator] Setting up concentrator radios
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring radio, radio: 0, enabled: true, center_freq: 867500000, type: SX1257
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring radio, radio: 1, enabled: true, center_freq: 868500000, type: SX1257
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Setting up concentrator channels
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 0, enabled: true, freq: 868100000, rf_chain: 1, if_freq: -400000
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 1, enabled: true, freq: 868300000, rf_chain: 1, if_freq: -200000
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 2, enabled: true, freq: 868500000, rf_chain: 1, if_freq: 0
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 3, enabled: true, freq: 867100000, rf_chain: 0, if_freq: -400000
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 4, enabled: true, freq: 867300000, rf_chain: 0, if_freq: -200000
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 5, enabled: true, freq: 867500000, rf_chain: 0, if_freq: 0
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 6, enabled: true, freq: 867700000, rf_chain: 0, if_freq: 200000
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring multi-SF LoRa channel, channel: 7, enabled: true, freq: 867900000, rf_chain: 0, if_freq: 400000
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring Std LoRa channel, enabled: true, freq: 868300000, rf_chain: 1, if_freq: -200000
2023-08-02T19:52:55.921Z INFO [chirpstack_concentratord_sx1301::concentrator] Configuring FSK channel, enabled: true, freq: 868800000, rf_chain: 1, if_freq: 300000
2023-08-02T19:52:55.922Z INFO [chirpstack_concentratord_sx1301::concentrator] Starting the concentrator
2023-08-02T19:52:59.079Z INFO [libconcentratord::events] Creating socket for publishing events, bind: ipc:///tmp/concentratord_event
2023-08-02T19:52:59.080Z INFO [libconcentratord::commands] Creating socket for receiving commands, bind: ipc:///tmp/concentratord_command
2023-08-02T19:52:59.081Z INFO [libconcentratord::jitqueue] Initializing JIT queue, capacity: 32

It still doesn’t work as seen from the webinterface. Do you know what that all means?

Ok, here is some update:

seems like I’m getting some frames:

2023-08-02T19:52:59.081Z INFO  [libconcentratord::jitqueue] Initializing JIT queue, capacity: 32
2023-08-02T19:53:29.082Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:53:59.082Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:54:27.300Z INFO  [chirpstack_concentratord_sx1301::handler::uplink] Frame received, uplink_id: 2910301797, count_us: 90828140, freq: 867900000, bw: 125000, mod: LoRa, dr: SF12
2023-08-02T19:54:29.083Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 1, rx_received_ok: 1, tx_received: 0, tx_emitted: 0
2023-08-02T19:54:59.083Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:55:29.083Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:55:59.084Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:56:29.084Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 1, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:56:59.085Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 1, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:57:29.085Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:57:59.085Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:58:29.086Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:58:55.537Z INFO  [chirpstack_concentratord_sx1301::handler::uplink] Frame received, uplink_id: 161467088, count_us: 359088659, freq: 867100000, bw: 125000, mod: LoRa, dr: SF7
2023-08-02T19:58:59.086Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 2, rx_received_ok: 1, tx_received: 0, tx_emitted: 0
2023-08-02T19:59:29.086Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T19:59:59.087Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 0, rx_received_ok: 0, tx_received: 0, tx_emitted: 0
2023-08-02T20:00:29.087Z INFO  [libconcentratord::events] Publishing stats event, rx_received: 2, rx_received_ok: 0, tx_received: 0, tx_emitted: 0

Also the following logs from the web interface seems to show that the upstream is also working:

Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Starting ChirpStack MQTT Forwarder (version: 4.1.0, docs: https://www.chirpstack.io/)
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Setting up ChirpStack Concentratord backend
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Setting up ChirpStack Concentratord backend
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Connecting to Concentratord event API, event_url: ipc:///tmp/concentratord_event
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Connecting to Concentratord command API, command_url: ipc:///tmp/concentratord_command
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Reading gateway id
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Received gateway id, gateway_id: 0101010101010101
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Received Gateway ID from backend, gateway_id: 0101010101010101
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Connecting to MQTT broker, server: tcp://192.168.33.20:1883, clean_session: false, client_id: 0101010101010101, qos: 0
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Connected to MQTT broker
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Starting MQTT consumer loop
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Subscribing to command topic, topic: eu868/gateway/0101010101010101/command/+
Wed Aug  2 19:59:23 2023 user.info chirpstack-mqtt-forwarder[2842]: Sending conn state, topic: eu868/gateway/0101010101010101/state/conn
Wed Aug  2 19:59:29 2023 user.info chirpstack-mqtt-forwarder[2842]: Received gateway stats
Wed Aug  2 19:59:29 2023 user.info chirpstack-mqtt-forwarder[2842]: Sending gateway stats event, topic: eu868/gateway/0101010101010101/event/stats

However, it clearly seems like the gateway ID doesn’t get received properly. What do you think is going on?

You probably already found out, but you are missing the -c channels.toml, which is causing the panic.

However, it clearly seems like the gateway ID doesn’t get received properly. What do you think is going on?

Could you explain? If you have configured 0101010101010101 in the web-interface as gateway ID, then this is expected. In case you are still running the chirpstack-concentratord-sx1301 by hand, then you might need to restart the MQTT Forwarder in order to update the gateway id, /etc/init.d/chirpstack-mqtt-forwarder.

Under normal circumstances, a web-interface change will cause the services to restart automatically to apply the changes :slight_smile:

Hello,

What I mean is that while I never entered any gateway ID in the web-interface, the only thing I ever see there is this 0101010101010101.
Now after configuring the MQTT forwarder and concentratord properly, attached is the pic I get from the web interface. Note the “could not read” gateway ID.

Furthermore, please note that in order to be sure that the hardware was not broken, I installed the old, yocto based version and it is working. I never managed to have concentratord properly detect my gateway ID on the openWRT version however.

Do you have an idea how I could investigate why the gateway ID is not detected?

Note that the Concentratord must be running to be able to read the Gateway ID. Once it is running. Based on “seems like I’m getting some frames” I believe you managed to start it, you should be able to run the following CLI command gateway-id.

If that outputs the gateway id, it should be a matter of refreshing the web-interface page to see the same there (it executes gateway-id to retrieve it).

Yes. That’s exactly the issue.

So here is some news:

  • the preceding message was because I had manually stopped concentratord as per your previous instructions and forgot to restart it
  • I have tried entering the right gateway-id manually and it’s now working

Now what is going on is the following:

  • the first time you start the web interface, the proper shield is not setup (it’s not lorago)
  • so by default the 0101010101010101 is generated for the gateway-id
  • the webinterface has no plafe to say “detect the right gateway-id”
  • so once you setup the proper shield, the interface and concentratord restart with the wrong gateway-id ( 0101010101010101)
  • when you go to the command line and type gateway-id, it indeed gives you 0101010101010101

So, in summary, I think the only issue is that when you change the shield to the right one, there is no “rediscovery” of the proper gateway-id or there isn’t at least a button close to the gateway-id number that says “auto-detect” or something like that.

Thanks

I gave this a shot and things generally seem to be working. However, I’m seeing a large number of files created in the root of the filesystem that appear to have GPS coordinates in them their names. The files themselves are empty.

EG:

-rw-r--r--    1 root     root             0 Aug  8 06:57 f�,064741.00,A,xxxx.72380,N,xxxxx.42562,W,0.052,,080823,,,D*71

There appears to be about 200 after running for ~24 hours.

This is with a RAK2287 with gnss.

Thanks.

@dustin thanks for your feedback. I’m aware there are issues, I’m working on a second test version right now :slight_smile: The issue is that Linux is currently booted with the console attached to the UART port of the Raspberry Pi. Console output is feed into the GNSS module and GNSS output is feed into the Linux console which is creating these files and causing other issues.

I have worked on a way to patch the OpenWrt source, without actually forking the repository. This is the fix that will be included in the next test version:

1 Like

v4.2.0-test.2

Features

This is a very exciting release, as this release migrates the ChirpStack Gateway OS from Yocto to OpenWrt. Thanks to LuCI and the UCI configuration system it is now possible to configure the provided ChirpStack components as well thinks like network configuration through a web-interface instead of a CLI. This release also splits the packages from the ChirpStack Gateway OS configuration such that these can be integrated in other OpenWrt based projects. Main features that this release brings:

Web-interface

There is no need to configure the ChipStack Gateway OS using a terminal. Powered by LuCI), the ChirpStack Gateway OS now provides an easy-to-use web-interface to configure ChirpStack components and system configuration.

Custom packages

Through the web-interface (and cli) it is possible to install additional software using the OpenWrt package repositories. This has been requested several times, but until now would require to compile a custom ChirpStack Gateway OS image which would take several hours to complete.

Updates

  • Update ChirpStack to v4.4.3.
  • Update ChirpStack Concentratord to v4.2.2.
  • Update ChirpStack UDP (in development) Forwarder to v4.1.2.
  • Update ChirpStack MQTT Forwarder to v4.1.0.
  • Update Node-RED to v3.0.2.

Upgrade notes

Unfortunately it is not possible to migrate from ChirpStack Gateway OS v4.1.1 to ChirpStack Gateway OS v4.2.0. You need to re-flash your SD-Card with the ChirpStack Gateway OS v4.2.0 image.

Hola Brocaar,

estuve probando la version 4.2.0 test2, pero no levanta el servicio de server chirpstack.

regrese a la version 4.2.0 test1 y levanta el servicio. hay algun cambio o configuracion extra para levantar los servicios server chirpstack y node red?

saludos.

Hello @brocaar . I don’t know what you have done and it doesn’t seem to appear in the change log but with this new version it’s working smoothly and the gateway-ID is properly detected! Thanks a lot !

Great, my Seed WM1302 with PiHat
Becomes online Status und Working