Device variables and tags are user-defined key/value values that can be assigned to devices. Tags can be used to add additional meta-data to devices and variables can be used for configured integrations (e.g. ThingsBoard requires a per-device Access Token).
PostgreSQL integration
When configured in the lora-app-server.toml configuration file, this integration will write events into a PostgreSQL database. See the PostgreSQL Integration documentation for more information.
ThingsBoard integration
When configured as Application integration, this integration will write attributes and telemetry to the configured ThingsBoard instance. See the ThingsBoard Integration documentation for more information.
Improvements
Speedup login with default admin / admin credentials (for low CPU power devices). (#320)
Gateway ID, FPGA ID and AES-key widgets have been updated.
Always display Class-C timeout field in Device Profile.
Bugfixes
Fix Gen Application Key is no longer a mandatory field. (#322)
Before upgrading, you must enable the hstore extension for the LoRa App Server PostgreSQL database. Example commands assuming the database is named loraserver_as:
sudo -u postgres psql
Within the PostgreSQL prompt, enter the following queries:
-- change to loraserver_as database and enable extension
\c loraserver_as
create extension hstore;
-- exit the prompt
\q
I have a gateway-bridge running on a VPS that points inwards to loraserver and I see all gateway data coming in on the MQTT server. so the data is coming in.
Could you define “lost connection with all gateways”, since you also mention “I see all gateway data coming in on the MQTT server”, so your gateways are still connected
Did you only update LoRa App Server, or also updated LoRa Server? Did you confirm that LoRa App Server is still running without any errors (your logs are from the loraserver process, you might want to look at the lora-app-server process too)?
Some aditional information that might answer your questions:
Although I see gateway traffic on MQTT it does not appear in LoRaServer console (currently last seen for 3 hours) and there is no live data in console too.
I updated both loraserver and lora-app-server
I found that config files ware replaced by default after which I reconfigured mqtt credentials.
In logging I see that MQTT is connecetd in both loraserver and lora-app-server
Yes, to me too. However I have not changed anything from the previous installation.
Can you provide directions on how to install cetrificates in the config file?
I generated certificate and key-file but cannot get it installed in the config file.
It is in this section of lora-app-server.toml (note that historically TLS was required, but this is no longer true).
# Settings for the "external api"
#
# This is the API and web-interface exposed to the end-user.
[application_server.external_api]
# ip:port to bind the (user facing) http server to (web-interface and REST / gRPC api)
bind="0.0.0.0:8080"
# http server TLS certificate (optional)
tls_cert=""
# http server TLS key (optional)
tls_key=""
Yes there is. It is not yet out as we also have been testing some Raspberry Pi 3B+ issues (some would not boot without HDMI connected). I believe this has been fixed now and I already updated the recipes at my side to issue a new release Stay tuned!
I have a working 3.01 server running on a RPi. My Linux foo is not strong, so I am not clear on the steps to upgrading to 3.1 (beyond what was in the original post).
My attempts to upgrade from 2.8x to 3.0 were pitiful and I ended up just redoing from scratch.
I was using AWS RDS for PostgreSQL for the App Server. But Amazon does not allow us to install DB extensions to their PaaS and it is quite reasonable. So after installation of an update my App Server stopped to run and crashes on run with this error in log:
level=fatal msg="setup storage error: storage: applying PostgreSQL data migrations error: pq: type \"hstore\" does not exist handling 0041_device_variables.sql"
Any ideas how this issue can be solved? I would prefer to stick to AWS RDS since until this update Chirpstack was so natively integrated there.
