[release] ChirpStack Network Server v3.15

v3.15.0

Features

Gateway metrics

This implements the forwarding of the additional gateway metrics implemented by ChirpStack Gateway Bridge v3.13.0 to the ChirpStack Application Server.

Improvements

  • Add AS923_4 band (AS923 with -5.90 MHz frequency offset).
  • Docker images added for ARM v6, v7 and ARM64. (#546)

Bugfixes

  • Remove sending mac-commands in Class-C downlink. (#543)
  • Fix AS923 sub-bands (_2 and _3) in GetVersion API response.
2 Likes

@brocaar Was there an API change in .15? After updating, the fuota-server enqueue grpc calls now fail. The latest fuota-server release is Index of /downloads/chirpstack-fuota-server/ 3.0.0-test.4?

time="2021-09-13T20:39:48Z" level=error msg="finished client unary call" error="rpc error: code = Unimplemented desc = Not Found: HTTP status code 404; transport: received the unexpected content-type \"text/plain; charset=utf-8\"" grpc.code=Unimplemented grpc.method=Enqueue grpc.service=api.DeviceQueueService grpc.time_ms=6.637 span.kind=client system=grpc
time="2021-09-13T20:39:48Z" level=error msg="handle clocksync error" error="enqueue payload error: rpc error: code = Unimplemented desc = Not Found: HTTP status code 404; transport: received the unexpected content-type \"text/plain; charset=utf-8\""

Trying to figure out what may have changed…

Looking at your logs, I don’t think this is related.

v3.15.1

Bugfixes

  • Update PostgreSQL client library (fixes re-connect). (#547)
  • Allow receiving less tx acknowledgements than downlink items sent to the gateway. E.g. two items were sent to the gateway, responded by a single OK acknowledgement (indicating the first item was sent).

@brocaar I installed chirpstack v3.15 in raspberry, but when I use AS923_4, some wrong accurred as follow:
pi@gateway:~ $ chirpstack-network-server version
WARN[0000] No configuration file found, using defaults. See: Configuration - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server
3.15.1
pi@gateway:~ $ sudo /usr/bin/chirpstack-network-server
FATA[0000] setup band error: get band config error: lorawan/band: band AS923_4 is undefined

I used the default configure file with only band changed. please give some help, thank you in advance.


The ‘_’ should be changed to ‘-’.

Bugfixes

  • Add missing password to Redis Sentinel Client. (#550)
  • Fix disablin ADR (when ADR algorithm is set in device-profile). (#538)
  • Restore the AMQP queue if needed after connection failure. (#503)

v3.15.3

Bugfixes

  • Fix AS923_X to AS923-X in configfile template.
  • Update lorawan dependency to fix LR-FHSS “data-rate not found” error.
2 Likes

I’m looking at frame logging feature introduced in v3.14 - lowering the per_device_frame_log_max_history to 5 returns last 5 frames on LORAWAN FRAMES device tab as expected, but DEVICE DATA tab still shows last 10 messages. Bug or feature? :slight_smile:

EDIT: Nevermind, found per_device_event_log_max_history under app-server config, which I guess will do the trick.