I do have a quiet large chirpstack deployment across mutliple buildings.
Some buildings have 2 LoRa Gateways installed for better coverage.
In total we have 9 Gateways installed at 8 buildings along a road.
Obviously there is an overlap in the coverage, so that sensors in each building are seen by more than 1 gateway on more than one location.
In General, uplinks are working fine, sensors send messages, they are picked up by several gateways and they route the message to the application server.
So far so good.
The problem I'm facing with this setup is confirmed messages. The sensors do send periodicly confirmed uplinks for which they expect ACK messages back from the gateway.
Since message is picked up by several gateways, chirpstack seems to select a
random gateway through which the ACK is being sent out.
How does it look in reality?
Sensor1 in building1 is sending an ConfirmedDataUp uplink.
This message is received by Gateway from Building 1,2,3 and even 4.
Gateway in building1 has received the message with the strongest signal and I would expect that the ACK message will be sent through the gateway in Building 1.
Instead, chirpstack decides to send out the ACK message through a gateway in Building 3, but that response is too week for the sensor, so it repeats itself again, and again. After 1 hour, it does not try any longer and restart.
Do I need to split up the sensors for each building into a seperate organization or seperate application? If I do so, do I still have coverage from the other buildings in case a gateway witihin a building goes down?
Many thanks for an advices here.
