Hello,
Is possible to control different network bands with the same physical server, under the same gateway-bridge and lora-appserver?
We would control gateways from different bands ( US 902-928 and EU 863-870) from the same server.
Thank you in advance!
I’m fairly certain that this is not possible since the settings for band selection is in the .toml file on the server.
You should be able to run multiple loraserver instances though, and manage those from the same lora-app-server service by providing the different network-server configurations at the UI.
This is the way to support multiple bands indeed 
in fact there is a trick, but you need to modify the source code
(1)disbale create gateway on stats feature
(2)add band info on mqtt receive lock
(3)filter packets by gatewayID, which means loraserver instance ignore gateways which not registered in it.
Hi. In the UI I’m getting error
Error context deadline exceeded (code: 2)
Must update from lora 0.23 to higher, but can’t do by apt-get for not losing info or/and configs.
Any update procedure / version sequence suggested?
Thank you!
Please see the change-logs for each service.
Hi, sorry for the inconvenience. SOLVED : What I’m losing? -> Corrupted lora-app-server networkserver table!!!, just cleaned and added network server again
I have installed 2 loraserver instances in the same server, in addition there’s a lora-app server instance.
Each loraserver has it’s own database in postgresql, Each loraserver is configured for a different band Europe and US. Both are v1.0.0
I got rid of the gateway management via single lora-app-server (and with remote gateway config),
When I try to add devices I get in trouble.
First I create the device-profile, in the correspondent network-server. it’s created ok with both options, but when I try to create a device (via api rest, or via lora-app-server web console) I get the same error:
{“error”:“rpc error: code = NotFound desc = object does not exist”,“code”:2}
only when creating a device in the second networkserver (US)
Thanks in advance.
==========Adding extra data===============
Log journalctl, as can see, the profile is created ok.
feb 05 13:52:25 osboxes lora-app-server[23707]: time="2019-02-05T13:52:25Z" level=info msg="device-profile created" device_profile_id=92828cca-a7b8-4a7e-950e-ee07c753927d
feb 05 13:52:25 osboxes lora-app-server[23707]: time="2019-02-05T13:52:25Z" level=info msg="finished unary call with code OK" grpc.code=OK grpc.method=Create grpc.service=api.DeviceProfileService grpc.start_time="2019-02-05T13:52:25Z" grpc.time_ms=7.045 peer.address="127.0.0.1:57374" span.kind=server system=grpc
feb 05 13:52:25 osboxes lora-app-server[23707]: time="2019-02-05T13:52:25Z" level=warning msg="Deprecated Authorization header : RFC1945 format expected : Authorization: <type> <credentials>"
feb 05 13:52:25 osboxes lora-app-server[23707]: time="2019-02-05T13:52:25Z" level=info msg="finished client unary call" error="rpc error: code = NotFound desc = object does not exist" grpc.code=NotFound grpc.method=CreateDevice grpc.service=ns.NetworkServer grpc.time_ms=1.239 span.kind=client system=grpc
feb 05 13:52:25 osboxes lora-app-server[23707]: time="2019-02-05T13:52:25Z" level=error msg="network-server create device api error" error="rpc error: code = NotFound desc = object does not exist"
feb 05 13:52:25 osboxes lora-app-server[23707]: time="2019-02-05T13:52:25Z" level=error msg="finished unary call with code Unknown" error="rpc error: code = Unknown desc = rpc error: code = NotFound desc = object does not exist" grpc.code=Unknown grpc.method=Create grpc.service=api.Device grpc.start_time="2019-02-05T13:52:25Z" grpc.time_ms=6.186 peer.address="127.0.0.1:57358" span.kind=server system=grpc
The same error occurs when I try to change the ipaddres or port from a networkserver in the lora-app-server web interface (the network-server server field)