[release] LoRa App Server 0.20.0 / LoRa Server 0.26.0 / LoRa Gateway Bridge 2.4.0


#1

This release deprecates the LoRa Channel Manager component and implements the packet-forwarder configuration management (for channel configuration) in LoRa Gateway Bridge.

Changelogs

LoRa App Server 0.20.0

Features:

  • (Gateway) channel-configuration has been refactored into gateway-profiles.
    • This requires LoRa Server 0.26.0 or up.
    • This removes the channel-configuration related gateway API methods.
    • This adds gateway-profile API methods.

Bugfixes:

  • Fix leaking Redis connections on pubsub subscriber (#313.
  • Fix discovery interval validation (#226).

Upgrade notes:

In order to automatically migrate the existing channel-configuration into the
new gateway-profiles, first upgrade LoRa Server and restart it. After upgrading
LoRa App Server and restarting it, all channel-configurations will be migrated
and associated to the gateways. As always, it is advised to first make a backup
of your (PostgreSQL) database.

LoRa Server 0.26.0

Features:

  • (Gateway) channel-configuration has been refactored into gateway-profiles and
    configuration updates are now sent over MQTT to the gateway.

    • This requires LoRa Gateway Bridge 2.4.0 or up.
    • This requires LoRa App Server 0.20.0 or up.
    • This deprecates the LoRa Channel Manager service.
    • This removes the Gateway gRPC service (which was running by default on port 8002).
    • This removes the channel-configuration related gRPC methods from the NetworkServer gRPC service.
    • This adds gateway-profile related gRPC methods to the NetworkServer gRPC service.
  • FSK support when permitted by the LoRaWAN ISM band.

    • Note that the ADR engine will only use the data-rates of the pre-defined multi data-rate channels.

Bugfixes:

  • Fix leaking Redis connections on pubsub subscriber (#313.

Upgrade notes:

In order to automatically migrate the existing channel-configuration into the
new gateway-profiles, first upgrade LoRa Server and restart it. After upgrading
LoRa App Server and restarting it, all channel-configurations will be migrated
and associated to the gateways. As always, it is advised to first make a backup
of your (PostgreSQL) database.

LoRa Gateway Bridge 2.4.0

Features:

  • LoRa Gateway Bridge can now manage the packet-forwarder configuration (channels).
    See Send / receive data for more information.

Gateway-profile enabled channels / LoRa Server extra channels
Feedback rev 0.26.0 loraserver.toml
Problem after update version
#2

#3

Hello community:
I have updated the lora-app-server to 0.20.0 version.
But I found a problem when the lora-app-server starts the service

image

what could be happened with lora-app-server?

thank you very much
Best regard.


#4

I deleted the Postgres database and reinstall the service. the problem continues.


#5

From which version did you upgrade? Version 0.19.0 inserted a new dependency on postgres, the pg_trgm extension, which needs to be created in the DB prior to the migrations. Check the changelog, in particular upgrade notes for version 0.19.0, here for instructions.


#6

I don’t know if I did bad command or something else, however after installing loraserver, I wanted to set loraserver.toml but I didn’t find the part “network_server.gateway.api.jwt_secret”.

Maybe I missed something in previous release or maybe it’s a bug ?

I read in your Release post:

This removes the Gateway gRPC service (which was running by default on port 8002).
This removes the channel-configuration related gRPC methods from the NetworkServer gRPC service.
This adds gateway-profile related gRPC methods to the NetworkServer gRPC service.

Certainly you can delete this post…


#7

Thanks for mentioning, this should have been deleted from the docs as that setting does not exist anymore :slight_smile: This has been updated.