[release] ChirpStack Gateway OS v3.3

v3.3.0-test.1

This is a rewrite of the ChirpStack Gateway OS, you must re-flash your SD Card to update! Currently this version only targets the Raspberry Pi 3.

Features

  • Yocto has been updated to version 3.0.
  • Software updates are now handled by SWUpdate.
  • The Semtech UDP Packet Forwarder has been replaced by ChirpStack Concentratord.

Updates

Fixes

  • Redis database does not start on boot after power failure that corrupts append only file. (#32)

ChirpStack Gateway OS v3.3.0-test.2

Updates

Supported hardware

  • Raspberry Pi 1 B+ support has been added (for IMST Lite Gateway)
  • IMST Lite Gateway has been added to gateway configuration script.

ChirpStack Gateway OS v3.3.0-test.3

Updates

ChirpStack Gateway OS v3.3.0-test.4

When updating from a previous v3.3.0 version, it is recommended to re-run the gateway-config utility to update the concentrator configuration.

Updates

1 Like

Hi @brocaar,

I tried Chirpstack Gateway OS for Raspberry Pi 3. I tried both (base and full) on both shields RisingHF RHF0M301 and RAK 831, with same issue. It seems ConcentratorD is having some problem to run.

tail -f /var/log/messages shows lots of lines like:

Mar 26 01:06:47 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:06:47Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:06:50 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:06:50Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:06:54 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:06:54Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:06:57 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:06:57Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:07:01 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:07:01Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:07:04 raspberrypi3 user.err monit[445]: 'chirpstack-concentratord' failed to start (exit status 1) -- '/etc/init.d/chirpstack-concentratord start': Configuration file  does not exist
Mar 26 01:07:04 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:07:04Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:07:08 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:07:08Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:07:11 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:07:11Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:07:11 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:07:11Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
Mar 26 01:07:14 raspberrypi3 user.err monit[445]: 'chirpstack-concentratord' process is not running
Mar 26 01:07:14 raspberrypi3 user.info monit[445]: 'chirpstack-concentratord' trying to restart
Mar 26 01:07:14 raspberrypi3 user.info monit[445]: 'chirpstack-concentratord' start: '/etc/init.d/chirpstack-concentratord start'
Mar 26 01:07:15 raspberrypi3 user.err chirpstack-gateway-bridge[459]: time="2020-03-26T01:07:15Z" level=error msg="backend/concentratord: event socket dial error" error="dial event api url error: zmq4: could not dial to \"ipc:///tmp/concentratord_event\": dial unix /tmp/co
M

I did in every case:

Afer that, /etc/chirpstack-concentratord/sx1301/global.toml is filled with default values. I change them (model=“generic_us915”, and gateway_id= random number)

/etc/chirpstack-concentratord/sx1301/band.toml is empty

/etc/chirpstack-concentratord/sx1301/channels.toml is empty. I populated with

[gateway.concentrator]
# US915 sub Band 2

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

[gateway.concentrator.lora_std]
frequency=904600000
bandwidth=500000
spreading_factor=8

I have to admit that this is my first time with chirpstack-concentratord. I would really appreciate any clue regarding this.

With best regards

Sebastian

ChirpStack Gateway OS v3.3.0-test.5

Updates

Features

Wifi Access Point mode

On initial installation on a Raspberry Pi 3, the Raspberry Pi will start Wifi in Access Point mode, so that it is possible to connect directly to the Raspberry Pi over WIFI for configuration of the concentrator shield and to re-configure the WIFI.

Improvements

  • RAK2245 configuration has been improved (using defined Concentratord model name).
  • RAK832 configuration has been improved.
  • RAK2245 / RAK831 AS923 channel-plan has been added. (#43)

Bugfixes

  • Fix passing incorrect model flags in gateway-config for some gateways.

The above release might fix your issue. Could you re-try with that version?

Hi @brocaar,
Thank you for your reply.
Yes! The new version works with RAK831. I haven’t tried with RisingHF, thought.
WiFi in access point is very clever. Specially when you don’t have access to DHCP Server.
Thank you again!

1 Like

Great and thanks for testing! The WiFi in access point mode is needed to provide support for the Raspberry Pi Zero Wireless (coming soon), which does not have an ethernet port. Glad you like it!

Thank you for your support!

I forgot to mention that WiFi in access point is good for RAK831 as well. The HAT adapter takes over serial pins, making impossible to access serial console.

ChirpStack Gateway OS v3.3.0-test.6

Features

  • Support has been added for the Raspberry Pi 4.
  • Support has been added for the Raspberry Pi Zero W.
  • Support has been added for the RAK2246 and RAK2246G shields.
  • Class-B beacon configuration has been added to the band configuration.

Updates

Improvements

  • gateway-config shows ChirpStack Gateway OS version.
  • gateway-config shows Gateway ID.
  • Change ISM band names to their common name. (#47)
  • sx1301-reset script has been modified to leave the reset pin as output.

ChirpStack Gateway OS v3.3.0-test.7

Updates

Features

  • Add gateway-config wizard for MQTT configuration.
  • Update to Yocto Dunfell + build Go apps from source. (#55)

Bugfixes

  • Fix AU915 selection bugs for RAK concentrators. (#56)

ChirpStack Gateway OS v3.3.0-test.8

Bugfixes

  • Fix ChirpStack Application Server Makefile execution to include web-interface statics in binary.

ChirpStack Gateway OS v3.3.0-test.9

Updates

Improvements

  • gateway-config has been updated for the Pi Supply LoRa Gateway HAT.
  • New gateway-config option has been added to reload the Gateway ID.

ChirpStack Gateway OS v3.3.0

This marks the first non-testing release of the ChirpStack Gateway OS!

Updates

ChirpStack Gateway OS v3.3.1

Updates

ChirpStack Gateway OS v3.3.2

Updates

Hello everyone, I have installed the ChirpStack Gateway OS v3.3.0-test.2 configuration on my imst lite gateway.
I would like to connect to my remote hirpStack Network Server.
in practice the gateway should only do packet forward to the remote server and remote server applicatio.

I usually configure global_conf and that’s it.
in this case I am afraid I have not understood how it works. it seems that the gateway also acts as a lora bridge?
Could you help me
thank you so much

ChirpStack Gateway OS v3.3.3

Features

Updates

Bugfixes

  • Fix bootfiles path in rpi-config. (#63)
  • Remove libubootenv. (#64)
  • Update u-boot CONFIG_SYS_BOOTM_LEN to 16M.
2 Likes