Hi,
I am trying to use the active LoraWAN gateway registered in https://www.thethingsnetwork.org/(TTN networks) but Iam not able to register the existing gateway through Lora APP server api.I have info of the gateway like EUI and name of the gateway.
Subscribing to already existing gateway is better than building a new one or do you have any suggestion in building a new LoraWAN gateway.
After running all of them,then I start the lora-app-server UI and try to create the server-profile ,but I am not able to choose network-server(I am connected to university Wifi).
My aim is to forward the packets to ttn gateway from my sensor node and then get the data from the gateway into the loraserver.Please let me know if I am wrong.
The issue is I am not able to create server-profile in app-server.
Check your LoRa Server logs + version. You did not apply the latest data-migrations, either because of an old LoRa Server version, --db-autmigrate is missing or because of an error. See also:
Hi ,
I have registered remote gateway and able to configure Lorawan .Please let me know to send/receive the data from application setup and the sensor node.
I’m having trouble when adding a new network server using the lora-app-server (version 0.17.1).
I’m using a Raspbian image generated with loraserver-pi-gen with the recommended changes to operate in the US915 frequency range.
I successfuly open the web interface at https://192.168.0.174:8080 in my local network, I use the admin credentials, and click the Network servers menu at the top bar. I enter some description and fill the Network-server server field with either localhost:8000 or 127.0.0.1:8000. Whenever I hit or the Submit button, I get the Error context deadline exceeded (code: 2) message, as shown next:
I know everything else is working because I’ve been able to use my gateway with the TTN application server. My end device is able to transmit and receive packets.
Has anyone face the same problem? I don’t seem to find enough information.
Also, when I kill the lora-app-server process that initiates when the Raspberry Pi 3 boots, I’m not able to relaunch it from the user pi. I try to log in with user appserver, the previous owner of the lora-app-server process, but I don’t know the password.
Moreover, no logs can be found in the respective /var/log directories. What could be a possible reason for the logs not being generated?
When I try to launch loraserver, it returns FATA[0000] NetID parse error: lorawan: exactly 3 bytes are expected, however, in /etc/default/loraserver, the second line is NET_ID=010203. Shouldn’t this be correct?
If I enter the net-idand the band manually, I get ERRO[0000] ping database error, will retry in 2s: pq: password authentication failed for user "pi". It’s the same problem I have to relaunch any of the other components since I can’t log as other users because I don’t know their passwords.
I’ve got the same errors running with loraserver and postgres users using sudo -u loraserver ./loraserver --net-id 123456 --band US_902_928.
I had to provide GW_SERVER_JWT_SECRET and then loraserver started successfuly.
Then, I went to the web interface and could add a network-server.
However, it does not show on the drop-down menu when I’m registering a gateway.
I’ll keep checking if I’m doing anything wrong.
Thanks a lot!
I will also check the feedback on configuration files.
UPDATE: My bad. I had to register a service profile first. Everything should work fine now.
Thanks again!