[release] LoRa Server 0.23.3 & LoRa App Server 0.17.X

Announcements
1

These releases allow you to start using the device-status feature (this was already available in LoRa Server, but not yet exposed though LoRa App Server). Also they contain some improvements and bug fixes :slight_smile:

LoRa App Server

0.17.0

Features:

  • Device last seen timestamp is now stored and displayed in device list

  • In the service-profile, it is now possible to set the

    • Device-status request frequency
    • Report battery level
    • Report margin

    When the interval is set to > 0 and reporting of this status is enabled,
    then this information is displayed in the device list and exposed over MQTT
    and the configured integrations.

  • Extra logging has been added:

    • gRPC API calls (to the gRPC server and by the gRPC clients) are logged
      as info
    • Executed SQL queries are logged as debug

  • A warning is displayed in the web-interface when creating a service-profile
    when no network-server is connected.

  • A warning is displayed in the web-interface when creating a device-profile
    when the organization is not associated with a network-server.

Internal changes:

  • The project moved to using dep as vendoring
    tool. In case you run into compiling issues, remove the vendor folder
    (which is not part of the repository anymore) and run make requirements.

  • The front-end code has been updated to use React 16.2.0 and all dependencies
    have been updated.

Bugfixes:

  • --gw-ping-dr 0 is now handled correctly (#204)

LoRa Server

0.23.3

Improvements:

  • Device-status (battery and link margin) returns 256 as value when battery
    and / or margin status is (yet) not available.
  • Extra logging has been added:
    • gRPC API calls (to the gRPC server and by the gRPC clients) are logged
      as info
    • Executed SQL queries are logged as debug
  • LoRa Server will wait 2 seconds between scheduling Class-C downlink
    transmissions to the same device, to avoid that sequential Class-C downlink
    transmissions collide (in case of running a cluster of LoRa Server instances).

Internal changes:

  • The project moved to using dep as vendoring
    tool. In case you run into compiling issues, remove the vendor folder
    (which is not part of the repository anymore) and run make requirements.
1 Like
2

Hi.

Thanks for the change. I’m trying them right now.

I have a question, where can I find information about the new values? Battery status and Link. I read something the server asking the device.
Is this a 1.1.0 LoRa feature? or is it a 1.0.2? i have the specification for 1.0.2 but lack the last and if it is something the module should do I want to ask directly to the manufacturer.

Thanks!

Never mind, working like a charm

imagen
imagen.png1140×87 6.47 KB

3

I’ve released one bug fix release for LoRa App Server.

LoRa App Server

0.17.1

Bugfixes:

  • Fix missing / prefix in two UI links causing a redirect to the login page.
  • Fix typo in TLS certificate loading causing error failed to find certificate PEM data in certificate input (thanks @Francisco_Rivas)