Bot releases are hidden (Show)
Published by brocaar over 6 years ago
Improvements:
HandleUplinkData
API call to the application-server is now handled async.Bugfixes:
storage.ErrAlreadyExists
was not mapped to the correct gRPC API error.Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/
Published by brocaar over 6 years ago
Features:
(Gateway) channel-configuration has been refactored into gateway-profiles and
configuration updates are now sent over MQTT to the gateway.
Gateway
gRPC service (which was running by default on port 8002
).NetworkServer
gRPC service.NetworkServer
gRPC service.FSK support when permitted by the LoRaWAN ISM band.
Bugfixes:
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.
Pre-compiled binaries are available at: https://www.loraserver.io/loraserver/overview/downloads/
Published by brocaar over 6 years ago
Features:
RU_864_870
as configuration option (thanks @belovictor)Improvements:
GetVersion
API method returning the LoRa Server version + configured region.lorawan/band
package with support for max payload-size perBugfixes:
Published by brocaar over 6 years ago
Features:
Class-B support! See Device classes
for more information on Class-B.
network_server.network_settings.class_b
Extended support for extra channel configuration using the NewChannelReq mac-command.
This makes it possible to:
Implement RXParamSetup mac-command. After a configuration file change,
LoRa Server will push the RX2 frequency, RX2 data-rate and RX1 data-rate
offset for activated devices.
Implement RXTimingSetup mac-command. After a configuration file change,
LoRa Server will push the RX delay for activated devices.
Published by brocaar over 6 years ago
Bugfixes:
Published by brocaar over 6 years ago
Improvements:
MQTT topics are now configurable through the configuration file.
See Configuration.
Internal cleanup of mac-command handling.
EnqueueDownlinkMACCommand
has been renamed to CreateMACCommandQueueItem
.Bugfixes:
create_gateway_on_stats
config mapping. (thanks @mkiiskila, #295)Published by brocaar over 6 years ago
Features:
StreamFrameLogsForGateway
API method has been added to stream frames for a given gateway MAC.StreamFrameLogsForDevice
API method has been added to stream frames for a given DevEUI.Changes:
GetFrameLogsForDevEUI
API method has been removed. The frame_log
tableUpgrade notes:
When upgrading using the .deb
package / using apt
or apt-get
, your
configuration will be automatically migrated for you. In any other case,
please see configuration.
Published by brocaar over 6 years ago
Improvements:
256
as value when batteryinfo
debug
Internal changes:
vendor
foldermake requirements
.Published by brocaar almost 7 years ago
Features:
This removes the following CLI options:
--as-ca-cert
--as-tls-cert
--as-tls-key
See for more information:
Published by brocaar almost 7 years ago
Features:
Bugfixes:
nil
pointer check for Time
Published by brocaar almost 7 years ago
Features:
Changes:
Working towards a consistent and stable API, the following API changes have
been made:
Application-server API
HandleDataDownACK
renamed to HandleDownlinkACK
HandleDataUp
renamed to HandleUplinkData
HandleProprietaryUp
renamed to HandleProprietaryUplink
GetDataDown
has been removed (as LoRa Server is now responsible for theNetwork-server API
Added
CreateDeviceQueueItem
FlushDeviceQueueForDevEUI
GetDeviceQueueItemsForDevEUI
Removed
SendDownlinkData
Note: these changes require LoRa App Server 0.15.0 or higher.
Published by brocaar almost 7 years ago
Note: this release brings many changes! Make sure (as always) to make a
backup of your PostgreSQL and Redis database before upgrading.
Changes:
Data-model refactor to implement service-profile, device-profile and
routing-profile storage as defined in the
LoRaWAN backend interfaces.
LoRa Server now uses the LoRa App Server Join-Server API as specified by the
LoRaWAN backend interfaces specification (currently hard-configured endpoint).
Adaptive data-rate configuration is now globally configured by LoRa Server.
See configuration.
OTAA RX configuration (RX1 delay, RX1 data-rate offset and RX2 dat-rate) is
now globally configured by LoRa Server.
See configuration.
API changes:
EnqueueDataDownMACCommand
renamed to EnqueueDownlinkMACCommand
PushDataDown
renamed to SendDownlinkData
Note: this release brings many changes! Make sure (as always) to make a
backup of your PostgreSQL and Redis database before upgrading.
Note: When LoRa App Server is running on a different server than LoRa Server,
make sure to set the --js-server
/ JS_SERVER
(default localhost:8003
).
This release depends on the latest LoRa App Server release (0.14). Upgrade
LoRa Server first, then proceed with upgrading LoRa App Server. See also the
LoRa App Server changelog.
Published by brocaar about 7 years ago
Features:
Implement sending and receiving 'Proprietary' LoRaWAN message type.
LoRa Server now implements an API method for sending downlink LoRaWAN frames
using the 'Proprietary' message-type. 'Proprietary' uplink messages will be
de-duplicated by LoRa Server, before being forwarded to LoRa App Server.
ARM64 binaries are now provided.
Published by brocaar about 7 years ago
Features:
IN_865_867
ISM band.Bugfixes:
Remove gateway location and altitude 'nullable' option in the database.
This removes some complexity and fixes a nil pointer issue when compiled
using Go < 1.8 (#210).
Update AU_915_928
data-rates according to the LoRaWAN Regional Parameters
1.0.2 specification.
Better handling of ADR and TXPower nACK. In case of a nACK, LoRa Server will
set the max supported DR / TXPower to the requested value - 1.
The ADR engine sets the stored node TXPower to 0
when the node uses an
"unexpected" data-rate for uplink. This is to deal with nodes that are
regaining connectivity by lowering the data-rate and setting the TXPower
back to 0
.
Published by brocaar about 7 years ago
Features:
8002
) whichNote: Before upgrading, make sure to configure the --gw-server-jwt-secret
/ GW_SERVER_JWT_SECRET
configuration flag!
Published by brocaar over 7 years ago
Improvements:
lorawan/band
packageRemoved:
RU_864_869
band. This band is not officially defined by theNote: To deal with nodes implementing the Regional Parameters 1.0 and
nodes implementing 1.0.2, the ADR engine will now only increase the TX power
index of the node by one step. This is to avoid that the ADR engine would
switch a node to an unsupported TX power index.
Published by brocaar over 7 years ago
Improvements:
--gw-mqtt-ca-cert
/ GW_MQTT_CA_CERT
configuration flag was added toBugfixes:
Published by brocaar over 7 years ago
Changes:
NetworkServer.EnqueueDataDownMACCommand
has been refactored in order toNetworkController.HandleDataUpMACCommandRequest
API method.NetworkController.HandleDataUpMACCommandRequest
has been updated to handleNetworkController.HandleError
method has been removed.Note: In case you are using the gRPC API interface of LoRa Server,
this might be a breaking change because of the above changes to the APi methods.
For a code-example, please see the Network-controller
documentation.
Bugfixes: