[release] ChirpStack v4.12

Announcements
1

v4.12.0

Features

FUOTA Support

This release brings FUOTA support to ChirpStack, deprecating the need to use the ChirpStack FUOTA Server. Currently it supports both the v1 and v2 versions of TS003, TS004 and TS005
specifications.

Note:

This has been tested against the LoRa Basics Modem stack. While testing, a small implementation difference has been found between the LoRa Basics Modem and the TS005 (v2) specification (#106). At this moment, the ChirpStack implementation has been aligned with the
LoRa Basics Modem.

Improvements

  • Add sorting to device and gateway tables. (#579)
  • Add Yandex ID OAuth provider support. (#622)
  • Generalize auto-conversion of SEC1 EC Keys to PKCS#8. (#618)
  • Replace static UUIDs by gen_random_uuid() in PostgreSQL migration. (#634)
  • Show origin in case of bind parse error. (#632)
  • Refactor device-profile fields in database to reduce amount of used columns.
  • Add filtering to device table.
  • Update internal dependencies.
  • Add JavaScript example for default ADR algorithm.
  • Add option to configure join-server authorization header.
5 Likes
2

I performed a rolling upgrade of our redundant (test) setup from version 4.11.1 to this release. After the first instance is restarted, I see errors in the second instance, making it fail to process uplinks:

ERROR up{deduplication_id=10e9419e-29ed-4879-a1f2-23677289e93b}: chirpstack::uplink::data: Handle uplink error error=column device_profile.class_b_timeout does not exist

These errors are resolved when the second instance is also restarted, but this kind of defeats the purpose of having a redudant setup :woozy_face:

3

Version v4.12.0 contains database schema changes. It is therefore not possible to run an older version and newer version on either the old or new database schema.

4

v4.12.1

Improvements

  • Update internal dependencies.

Bugfixes

  • ui: Fix JSON enqueue error. (#658)
  • ui: Fix error after deleting tenant. (#635)
  • ui: Fix potential code-editor rendering issues (by replacing codemirror by ace).
5

Hello!

I’ve been trying to use the v3-to-v4 migration tool and in the documentation it mentions it needs 4.11 but I cant find the packages nor downgrade the version in my Raspberry Pi 3B+. It only finds and updates for this latest 4.12 version.