Do you mean running two (or more) LoRa App Server instances to make your deployment more scalable / highly available? Or do you want LoRa Server to forward part of the devices to LoRa App Server 1 and the other part of the devices to LoRa App Server 2?
@lucdioc Have you been successful? Because I need the same functionality.
However, I can’t test it because I don’t have a complete setup yet with devices that transmit.
Btw, on /internal/uplink/data/data.go in Lora Server repository under getApplicationServerClientForDataUp method there is a logic for getting an application server client from a pool of registered IP addresses before making the gRPC (uplink) call.
I wondering if this part can be those that enables one-to-many communication between Loraserver an Lora-App-Server.
Thanks in advance.
On the documentation of Lora Server, under Routing-profile section, says that one lora-server is able to connect to multiple lora-app-server istance. So at the end it is possible to connect multple lora-app-server to ona lora-server istance I guess.
@brocaar i have similar architecture as @NMont , i have deployed 2 App server (development and production) and 2 network server with same band complying both app server respectively as well 1 mqtt broker assisting both environment . But , i have situation where some of my client would like to use their gateway for their own RnD purpose and serving my product as well . Right now , im putting 1 gateway in both enviroment and let my client use account in dev enviroment for their rnd and their purchased product served in production appserver . Am i advisable to do so because sometimes my product sending JoinAccept and first uplink on the lorawan frames at both appserver but on the production appserver where my device is registered it doesn’t show the device have been activated .