First make sure you have v0.26.3 installed and running (including LoRa App Server v21.1).
Then ugrade to v1.0.0.
See Downloads
for pre-compiled binaries or instructions how to setup the Debian / Ubuntu
repository for v1.x.
Changes
Code to remain backwards compatible with environment-variable based
configuration has been removed.
Code to migrate node- to device-sessions has been removed.
Code to migrate channel-configuration to gateway-profiles has been removed.
Old unused tables (kept for upgrade migration code) have been removed from db.
LoRa App Server v1.0.0
This marks the first stable release!
Upgrade notes
First make sure you have v0.21.1 installed and running (together with LoRa Server v0.26.3).
As some configuration defaults have been changed (in the MQTT topic node
has been replaced by device), make sure the old defaults are in you config
file. To re-generate a configuration file while keeping your modifications, run:
As some configuration defaults have been changed (in the MQTT topic node
has been replaced by device)
Therefore I recommend to re-generate the configuration file before upgrading so that the old defaults will be written to the configuration file. Then when installing v1.0.0 the MQTT topics stay the same.
On installing the .deb package, the installation script did prompt that self-signed certificates have been generated, but they were not set automatically in the generated lora-app-server.toml configuration file (clean install). This has been updated (@SJ_Park this is probably related to your issue)
LoRa App Server v1.0.1
Improvements
tls_cert and tls_key are set automatically (again) when installing from .deb file.
Hello, I don’t know if it’s the right post but I noticed something with this version.
When I generated the configuration file for lora-app-server keeping my old configuration: lora-app-server configfile --config lora-app-server-old.toml > lora-app-server-new.toml, in MQTT integration section I kept the old formalism:
Maybe just I need to replace node by device, however the behavior is quite strange because the lora-app-server works with …/node/… as path formalism
I’m using loraserver v1.0 and lora-app-server v1.0.1
I assume that my influxdb integration is ok with this configuration, I have got logs from CLI after show measurements:
Here a part of the payload with the object form (cayenne LPP codec) from my websocket integration:
This loads lora-app-server-old.toml first, sets these variables and then generates a new configuration file. You want to use this when you want to keep the old topic naming (your config is then out-of-sync with the default values, but that is fine as you can change them at any time).
lora-app-server configfile > lora-app-server.toml
This overwrites the lora-app-server.toml file with a new config file, using the defaults provided by LoRa App Server. As for consistency .../node/... was replaces by .../device/... in the latest version, you will see this changes when creating a new config file.
My server is still LoRa Server 0.22.0 & LoRa App Server 0.14.x, can I still do upgrade to the new versions or must a reload the new version from scratch?